The problem with mutt is now solved. The problem with evolution isn't.

When displaying or composing emails the most recent version of mutt need to store temporary files in /var/tmp. It used to store them in /tmp, and that is what it still tells you if you look at the man page. On my PC, but not on my mail server the file permissions for /var/tmp were wrong (40755 not 41777). Correcting this solved the problem with mutt.

I still have no solution as to why my evolution mail user agent is unable to open my local mbox mail file (/var/mail/[myusername]), reporting a locking error instead.

As HOAS says UFW still accesses the nftables back-end (which uses the nftables kernel module) through an iptables translation layer.

If you want to run nftables commands natively you need to do as HOAS suggest. 

If you have Chimaera (or above) then use the nftables init script provided by orphan-sysvinit-scripts.

If you have Beowulf or earlier then there is no orphan-sysvinit-scripts. Having installed nftables and put the commands you want run in the config file you need to copy the example file /usr/share/doc/nftables/examples/sysvinit/nftables.init to /etc/init.d/nftables, change the Default-Start and Default-Stop lines (lines 6 and 7) and then make the init file executable by root.

Change the lines:

# Default-Start:
# Default-Stop:      0 1 2 3 4 5 6

to:

# Default-Start:     S	
# Default-Stop:      0 6

Then run

update-rc.d nftables defaults

as described by HOAS.

This will then read the config file and start nftables at boot.

You report that your problem is intermittent, which if true makes it hard to solve.

For myself I use the pm-utils package to suspend or hibernate and resume.

My wifi card uses the ath9k kernel module, however I found that it wasn't powering down when I suspended so I configured pm-utils to unload and reload the relevant module(s). This solved my problem.

One issues was that for my wifi card there are actually several interdependent modules, not just the primary one, and I needed to load/unload all of them. In my case these were ath9k ath9k_common ath9k_hw ath.

The instruction I had to use to specify which modules to load/unload were in the file /etc/pm/config.d/defaults, the relevant lines being:

# If you need to unload any modules to suspend/resume, add them here.
SUSPEND_MODULES="ath9k ath9k_common ath9k_hw ath"

you can check what is actually happening by viewing the log file /var/log/pm-suspend.log, where, on my system I find:

[on suspend]

Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
Unloading kernel module ath9k...Done.
Unloading kernel module ath9k_common...Done.
Unloading kernel module ath9k_hw...Done.
Unloading kernel module ath...Done.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.

[on resume]

Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend:
Reloaded unloaded modules.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.

Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend:
Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
/usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend: success.

The log also captures module interdependencies, and this is where you can find if you've loaded/unload all the relevant modules. in my case it shows (in additions to all the other modules/dependencies:

Linux grendel 4.19.0-18-amd64 #1 SMP Debian 4.19.208-1 (2021-09-29) x86_64 GNU/Linux
Module                  Size  Used by
ath9k                 139264  0
ath9k_common           20480  1 ath9k
ath9k_hw              483328  2 ath9k_common,ath9k
ath                    36864  3 ath9k_common,ath9k,ath9k_hw

Which is where I got my list of related wifi card modules from.

For me suspend/hibernate and resume works and the networking restarts.

In my Cinnamon (3.8.8) on Beowulf the window buttons settings are in Menu>System Settings (Control Centre)>Windows>Titlebar tab or alternatively Menu>Preferences>Windows>Titlebar tab.

Normally you decide which buttons (Max,Min,Close,Menu,Close,Sticky,Shade) go on the left or right but it would be possible to blank them all.

Have you had a look at
https://github.com/DNSCrypt/dnscrypt-pr … and-Ubuntu?

There's more information about installation and configuration in the wiki (see right panel on that page)

The versions in the devuan repositories are reasonably up to date (2.0.19 in Beowulf) but you can update to the latest version from Github as long you also get the latest configuration to use the additional features.

If you need more information I run dnscrypt-proxy myself (my version is 2.0.44).

Not quite sure why some of us are rushing to update firefox-Esr, and looking for round-about, and perhaps dangerous, ways to do so.
The whole point of firefox-esr is that it is stable.
Although firefox-esr 91.0 was released on 8 August Mozilla continue to provide 3 months of monthly point security updates of the previous Firefox-esr.
Debian/Devuan have always used this delayed release and only then made the new version avaialble as a security upgrade, which has then had three security patches under the belt.
Firefox-esr 91.3 is due for release 2 November, at the same time as Firefox 94.
I expect to receive it shortly thereafter in a normal unattended secruity update, replacing the last version of Firefox-esr 78 - 78.15.
This is what happened last year.

Your issue seems to relate to runing scripts that capture the lid open/closing event and running an appropriate command.

This has to happen before you call your suspend/hibernate/resume command and therefore related to acpi/acpid and acpi scripts not pm-utils and its scripts which obviously only run once suspend/resume have been called.

I don't have a laptop myself so I have no personal experience of how to do this.

However there is some discussion (and further links) here that might be able to help:

https://askubuntu.com/questions/517683/ … ect=1&lq=1

Ubuntu 14 was the last sysvinit version of Ubuntu before they went over to the systemd darkside.

Yes, if you are using sysvinit then I'd anticipate that you can use pm-utils to suspend and hibernate . Which is what I use.

Installing the pm-utils package installs both binaries and the scripts that are run when you put your machine to sleep/wake it up again.

As root/sudo you can run pm-suspend, pm-hibernate or pm-suspend-hybrid.

I've added the names of the first two of these to my sudoers file so that I can run them from a power menu button on my cinnamon desktop.

The pm-utils configuration scripts are in /etc/pm/ and /usr/lib/pm-utils.

In the former you will have the /etc/pm/config.d/defaults script that (inter-alia) sets the hibernate mode.

This is mine:

##########################################################
# DO NOT EDIT THE FILE in /usr/lib/pm-utils/             #
#                                                        #
# Edit this in /etc/pm/config.d/ instead!                #
##########################################################

# Default method to power down the system when hibernating.
# If commented out, the system will use the kernel default as a 
# default value.
#
# Check /sys/power/disk for valid values.  The default value
# will be surrounded by [square brackets].
HIBERNATE_MODE="platform"

# Whether we need to post the video card when resuming from
# hibernate. You should not normally need to set this.  
# In the future pm-utils will get this setting from HAL.
#
# Valid values are "no" and "yes"
# HIBERNATE_RESUME_POST_VIDEO="no"

# The default sleep/wake system to use.  Valid values are:
#   kernel    The built-in kernel suspend/resume support.
#             Use this if nothing else is supported on your system.
#   uswsusp   If your system has support for the userspace
#             suspend programs (s2ram/s2disk/s2both), then use this.
#   tuxonice  If your system has support for tuxonice, use this.
#
# The system defaults to "kernel" if this is commented out.
SLEEP_MODULE="kernel"

# These variables will be handled specially when we load files in 
# /etc/pm/config.d.
# Multiple declarations of these environment variables will result in 
# their contents being concatenated instead of being overwritten.

# If you need to unload any modules to suspend/resume, add them here.
SUSPEND_MODULES="ath9k ath9k_common ath9k_hw ath"

# If you want to keep hooks from running, add their names here.
# HOOK_BLACKLIST=""

# If you want to unconditionally add parameters to the commandline,
# add them here.
# ADD_PARAMETERS=""

# If you want to ignore commandline parameters, add them here.
# DROP_PARAMETERS=""

# If you need to synchronize the system clock across a suspend/resume or
# hibernate/thaw cycle, set this variable.
# NEED_CLOCK_SYNC="true"

My atheros network card refuses to go to sleep so I unload the relevant modules and reload then on waking, hence the SUSPEND_MODULES= line.

I aso have supplementary scripts:

etc/pm/sleep.d/10_unattended-upgrades-hibernate that stops hibernation until unattended upgrades has finished.

and

etc/pm/sleep.d/password-protect-waking that calls a locked screensaver on waking.

In the latter you will find the default scripts that are run when you put your computer to sleep and are then run in reverse when you wake it up. You can also add your own.

I  have an additional script  /usr/lib/pm-utils/sleep.d/95anacron that start and stops anacron when I sleep the computer. The purpose of this is to defer scripts run by anacron until the computer is awake (regular cron scripts simply don't run if the computer is asleep).

#!/bin/sh

# This script makes anacron jobs stop/start when a workstation
# enters/exits a suspended/hibernated state.
# 

case $1 in
    resume|thaw)
	/usr/sbin/invoke-rc.d anacron start >/dev/null   
	;;
    suspend|hibernate)
	/usr/sbin/invoke-rc.d anacron stop >/dev/null   
	;;
esac

and  /usr/lib/pm-utils/sleep.d/wpa-supplicant that notifies wpa-supplicant of pm actions.

#!/bin/sh

# /etc/pm/sleep.d/60_wpa_supplicant
# Action script to notify wpa_supplicant of pm-action events.

PATH=/sbin:/usr/sbin:/bin:/usr/bin

WPACLI=wpa_cli

case "$1" in
	suspend|hibernate)
		$WPACLI suspend
		;;
	resume|thaw)
		$WPACLI resume
		;;
esac

exit 0

Just to report that my system has reverted to normal behaviour, with automatic screen blanking and then suspend after a pre-determined delay.

I've not done anything I'm aware of to achieve this, it has just happened. Not sure exactly when either as I normally invoke suspend manually.

I can't find any relevant reverted package updates.

My suspicion is that it may be have been triggered by minor kernel updates: I upgraded to 4.19.0.16 on 16 March and 4.19.0.17 on 18 July.

I think you do still need the current kernel headers to recompile the kernel module for NVidia if you are using NVidia's own driver.

I have this working in Beowulf with lightdm and Cinnamon.

I have a GRUB_CMDLINE_LINUX="text" in /etc/default/grub.

I assume that you ran update-grub to change /boot/grub/grub.cfg?

This should have put a 'text' parameter in the linux /vmlinux.. line of your grub.cfg's menuentry.

This will start you in text mode, not sure if this will then permit you to successfully run startx - it is implemented as a simple trap in the lightdm init script (/etc/init.d/lightdm):

case "$1" in
  start)
        CONFIGURED_DAEMON=$(basename "$(cat $DEFAULT_DISPLAY_MANAGER_FILE 2> /dev/null)")
        if grep -wqs text /proc/cmdline; then
            log_warning_msg "Not starting Light Display Manager (lightdm); found 'text' in kernel commandline."
        elif [ -e "$DEFAULT_DISPLAY_MANAGER_FILE" ] && \
           [ "$HEED_DEFAULT_DISPLAY_MANAGER" = "true" ] && \
           [ "$CONFIGURED_DAEMON" != lightdm ] ; then
                log_action_msg "Not starting Light Display Manager; it is not the default display manager"
        else
                log_daemon_msg "Starting Light Display Manager" "lightdm"
                start-stop-daemon --start --quiet --pidfile /var/run/lightdm.pid --name lightdm --exec $DAEMON -b|| echo -n " already running"
                log_end_msg $?
        fi
  ;;

In my case this is on my mail server and I just run it headless and ssh -X into it from my desktop PC. Graphics mode (Cinnamon desktop) is installed as I used it when configuring the server and it's there if I were to need to work on the server with a keyboard and screen plugged in on my desk.