SUMMARY *** A short self-made bashscript that starts xbindkeys unfortunately does not work anymore since the update to KDE Neon 22.04. Running the bashscript manually in the console after starting the desktop works without problems. My Script: #!/bin/bash nohup xbindkeys #EOF *** Distributor ID: Neon Description: KDE neon 5.26 Release: 22.04 Codename: jammy STEPS TO REPRODUCE 1. start from KDE, OBSERVED RESULT no process of xbindkeys running EXPECTED RESULT An xbindkeys should be visible in the process list SOFTWARE/OS VERSIONS Distribution: KDE neon 5.26 Kernel : 5.15.0-53-generic Plasma : 5.26.3 Qt : 5.15.7 KF : 5.100.0 Kwin : 5.18.7 ADDITIONAL INFORMATION The shell script for the autostart of xbindkeys was correctly included or created by me in the system settings under the item Start and Shutdown, subitem Autostart.
Created attachment 153927 [details] Screentshot Autostart script in the systemsettings
Can you attach the script file?
Created attachment 154160 [details] Autostart shellscript Here is my shellscript in the file attachment
The script appears to not be executable. Does it start working if you make it executable?
the shellccript is executable, I already paid attention to that. -rwx------ 1 michael michael 24 Feb 10 2015 /home/michael/userscripts/start_xbindkeys
Thanks. If you run `kwriteconfig5 --file startkderc --group General --key systemdBoot false` in a terminal window and reboot, does it start working again?
The command line command they mentioned solved the problem. The start_xbindkeys autostart script is now executed when the KDE desktop is started. Thus the additional key bindings for the mouse are initiated in the script start_xbindkeys . I still have one question, what exactly does the command do?
It turns off Systemd boot. Systemd boot is stricter about what's allowed to autostart, and it sounds like this thing is triggering its strictness. You can use that workaround for now, but for further debugging, please disable it by running `kwriteconfig5 --file startkderc --group General --key systemdBoot true`. David, any ideas?
Might be this bug, which is resolved upstream in systemd 250. Neon is on 249 :( https://bugs.kde.org/show_bug.cgi?id=433299
Can you check the logs of the generated autostart unit? to do so, cd $XDG_RUNTIME_DIR/systemd/generator.late You should find the unit generated for your script then find the logs by systemctl status --user "scriptname"
Hi thenujan, there is no autostart unit $ systemctl status --user start_xbindkeys.sh Unit start_xbindkeys.sh.service could not be found.
(In reply to bluelupo from comment #11) > Hi thenujan, > > there is no autostart unit > > $ systemctl status --user start_xbindkeys.sh > Unit start_xbindkeys.sh.service could not be found. You wouldn't have the autostart unit in the same name. you need to look for the generated unit inside the directory I mentioned ($XDG_RUNTIME_DIR/systemd/generator.late). It would start with "app-". It would contain the name start_xbindkeys the underscore might be replaced with something else
Output of the command.... $ systemctl status --user app-xbindkeys@autostart.service ○ app-xbindkeys@autostart.service - xbindkeys Loaded: loaded (/etc/xdg/autostart/xbindkeys.desktop; generated) Active: inactive (dead) since Tue 2022-12-13 06:57:21 CET; 2h 49min ago Docs: man:systemd-xdg-autostart-generator(8) Process: 3105 ExecStart=/usr/bin/xbindkeys_autostart (code=exited, status=0/SUCCESS) Main PID: 3105 (code=exited, status=0/SUCCESS) CPU: 31ms Dez 13 06:57:20 neonlight systemd[2614]: Starting xbindkeys... Dez 13 06:57:20 neonlight systemd[2614]: Started xbindkeys.
$ systemctl cat --user app-xbindkeys@autostart.service # /run/user/1000/systemd/generator.late/app-xbindkeys@autostart.service # Automatically generated by systemd-xdg-autostart-generator [Unit] Documentation=man:systemd-xdg-autostart-generator(8) SourcePath=/etc/xdg/autostart/xbindkeys.desktop PartOf=graphical-session.target Description=xbindkeys After=graphical-session.target [Service] Type=exec ExecStart=:/usr/bin/xbindkeys_autostart Restart=no TimeoutSec=5s Slice=app.slice
Looks like it worked. So despite that output, `xbindkeys` is not running? You can confirm with `ps -e | grep -i xbindkeys`?
Hello Nate, no xbindkeys does not run in the process list. $ ps -ef|grep -i xbindkeys michael 8196 8164 0 07:18 pts/1 00:00:00 grep --color=auto -i xbindkeys $ systemctl status --user app-xbindkeys@autostart.service ○ app-xbindkeys@autostart.service - xbindkeys Loaded: loaded (/etc/xdg/autostart/xbindkeys.desktop; generated) Active: inactive (dead) since Thu 2022-12-15 06:51:53 CET; 32min ago Docs: man:systemd-xdg-autostart-generator(8) Process: 3110 ExecStart=/usr/bin/xbindkeys_autostart (code=exited, status=0/SUCCESS) Main PID: 3110 (code=exited, status=0/SUCCESS) CPU: 28ms Dez 15 06:51:53 neonlight systemd[2514]: Starting xbindkeys... Dez 15 06:51:53 neonlight systemd[2514]: Started xbindkeys.
That's odd. It definitely looks like it's running. Maybe it runs and then immediately dies for some reason? This is getting beyond my debugging abilities.
We're missing `ExitType=cgroup` Newer systemd will fix it.
As a workaround, wrapping in a shell script would work as then the topmost process will stay alive
This bug was filed against Neon, which uses Ubuntu 22.04 as a base. It's not that old, so it's unfortunate that they don't ship the version of systemd with this bug fixed. What systemd version is the fix in?