Xbindkeys is the most important application on my system--everything I do involves keyboard shortcuts, and using xbindkeys to store the keybindings in a text file is vastly superior to most DE's clunky GUI approach.

Alas, I've looked into this question and could not find an xbindkeys equivalent for Wayland. Honestly, I think the shiny-new-toy makers working on Wayland don't give a hoot about graybeards whose workflow revolves around "obsolete" physical keyboards.

My prediction is that first Wayland will see widespread adoption, then people like us will develop an xbindkeys replacement.

@golinux: I read the link you posted and was shocked by the magnitude of the GTK3 problem. It makes me sad that this commercial mindset has a foothold in GNU/Linux. Seems that the systemd developers and the GNOME/GTK developers are birds of a feather.

MATE has been my DE of choice. Do you know whether the MATE version in ASCII is GTK3-based? If so, I can imagine the themes I've been using for last few years will become useless. I thought MATE would be a safe haven from the disease showcased in the link, but if they're using GTK then they're beholden to whatever the GTK developers do.

I just don't understand these Devuan graybeards. Why would anybody would want to setup shutdown jobs this way:

# This goes in /etc/init.d/hook-for-my-shutdown-jobs
[ "$1" = "stop" ] && /opt/scripts/my-shutdown-jobs

When one can can do it this way instead:

# This goes in /etc/systemd/system/hook-for-my-shutdown-jobs
[Unit]
Description=Run shutdown scripts

[Service]
Type=oneshot
RemainAfterExit=true
ExecStart=/bin/true
ExecStop=/opt/scripts/my-shutdown-jobs

[Install]
WantedBy=multi-user.target

Making even trivial tasks complex makes me feel smart.

The update-alternatives man page said this command would fix all breakages...

yes '' | sudo update-alternatives --force --all

...and, indeed, all the warnings went away after running the command Nevertheless, it would still be nice to understand what the warnings meant.

1. Download the latest Firefox*.AppImage (available here: https://bintray.com/probono/AppImages/F … .3.4#files)
2. Make it executable
3. Run it and enjoy

Congratulations!

I've used systemd-based distros since switching to GNU/Linux (Arch Linux and Debian 8). Before Devuan, I was only able to write an init service file after hours of research and many head-against-wall impacts.

Being a big fan of the UNIX philosophy and KISS principle, I ditched the other distros and switched to Devuan since it's been in beta. Not only have I never had any issues, Devuan Jessie actually boots faster on my machine than Debian Jessie (I love the irony in that).

Because my init system is no longer an alien, yesterday I wrote my first SysVinit service file after only a few minutes of research. I find SysVinit to be quite elegant and transparent, and am very happy that shell scripting skills do not suddenly become irrelevant when I venture into the bowels of my system. 

I'm really enjoying the combination of a) the greater control SysVinit allows me to exert over my machine and b) the power and convenience of Debian's package management tools and vast repository. Thank you, Devuan.

I hope that either a) the X11 protocol and its cornucopia of tools never die (as Bad Sector suggests) or b) if/when Wayland becomes default, it will offer tools that allow us to do at least as much as we can do with X11.

I rely heavily on desktop environment-agnostic and window manager-agnostic (i.e., highly portable) tools such as xdotool (for GUI automation) and xbindkeys (for keyboard shortcuts). I'd be a miserable GNU/Linux user without these tools or something very similar.

If you are using a screensaver other than xscreensaver, here is a screensaver-agnostic alternative:

#!/bin/bash

while true; do
	sleep 10
	cat /proc/asound/card*/pcm*/sub*/status | grep RUNNING && xdotool key Pause
done

The Pause key does not seem to do anything at all on my system, and I can use my system normally even if the key is being pressed in the background.

Thank you very much, smoki. I will check the encryption setting on the routers I control. Also, I added the nohwcrypt=1 parameter to ath9k as suggested. So far, so good ::fingers crossed::

@MiyoLinux: Thank you for sharing. It's very nice.

I've also noticed that trend, with things being more dumbed-down and less configurable in MATE as time passes. I also took a peek at the latest MATE versions, which have migrated to gtk3, and was upset that text previews in caja's icons no longer seem to work, for instance.

MATE is still my go-to DE for the time being, however, as I find it to be the most usable out of the box. XFCE is a close second but, after getting used to MATE, XFCE feels a bit rough (e.g., several custom patches required in xfdesktop and thunar in order to get basic features that caja provides by default).

Change for change's sake is bad enough. Change for change's sake plus lost functionality is even worse. But I'll stop my rambling before we get too off-topic.

@afuerst: I also use MATE and was missing the Suspend option in the shutdown dialog. I don't use Hibernate.

Also, if I press Alt + F4 and there are no windows left to close, I like the shutdown dialog to show up (I guess this is a leftover expectation from my Windows days). I was able to solve all problems by installing yad, xdotool, and wmctrl and "rolling my own" with these two scripts:

#!/bin/bash
# Put this script somewhere in your path. Name it altF4
activename_id="`xdotool getactivewindow getwindowname`_`xdotool getactivewindow`"
if [[ "$activename_id" = x-caja-desktop* || "$activename_id" = "_" ]]; then
	my-power-dialog
	while true; do # waiting for dialog to exist before activating it
		shutdowndialogid=$(wmctrl -lx | fgrep 'Power options' | awk '{print $1}')
		[ -n "$shutdowndialogid" ] && break
	done
	xdotool windowactivate $shutdowndialogid
else
	wmctrl -c :ACTIVE:
fi

#!/bin/bash
# Put this script somewhere in your PATH. Name it my-shutdown-dialog
yad --width 100 --height 50 --title "Power options" --on-top --center \
    --button=Shutdown:1 \
    --button=Restart:2 \
    --button=Suspend:3 \
    --button=Cancel:0 

case $? in
    1)	sudo shutdown -h now ;;
    2) 	sudo shutdown -r now ;;
    3) 	sudo pm-suspend ;;
    0)	exit 0 ;;
esac

Once the scripts are in one's PATH and executable, just map the Alt + F4 keyboard shortcut to the altF4 script. BTW, the yad package is not in Devuan stable's repo, but I use the one from Debian testing without any issues (https://packages.debian.org/search?keyw … ection=all).

Hope some of this is useful.

P.S. Instead of having the stock shutdown button on my MATE panel, I have a "Custom Application Launcher" that runs my-shutdown-dialog.