Hello Neon-Users,

after the upgrade to KDE Neon on 22.04 the automatic start of xbindkeys unfortunately doesn't work anymore, which worked without problems before the upgrade. I need xbindkeys to assign two additional mouse buttons.

My $HOME/.xbindkeysrc

Code: Select all

"kate"
  b:10

"audacious"
  b:8


Also creating an autostart entry in the system settings to start xbindkeys did not bring any success. A manual start of xbindkeys in the KDE konsole always works fine and after that the additional mouse buttons were configured correctly.

What do I have to do to start xbindkeys automatically again?

Regards
Bluelupo

Probably this thread might help:
viewtopic.php?f=309&t=176336&p=458570&hilit=autostart#p458570

claydoh wrote:Probably this thread might help:
viewtopic.php?f=309&t=176336&p=458570&hilit=autostart#p458570

Hi claydoh,
hmmm, I don't know how the thread you mentioned is going to help me right now. But anyway thanks for your answer.

Regards
Bluelupo

Switching from the new systemd startup scheme to the previous one seems to help people with autostart item issues. I missed mentioning that part

bluelupo wrote:

claydoh wrote:Probably this thread might help:
viewtopic.php?f=309&t=176336&p=458570&hilit=autostart#p458570

Hi claydoh,
hmmm, I don't know how the thread you mentioned is going to help me right now. But anyway thanks for your answer.

Regards
Bluelupo

Please note the following from that thread:

all child processes are killed
<snip>
if your script contains a command that spawns another process (such as sshfs), these processes will be killed when the main script exits

When you invoke xbindkey, it spawns another background process and exits. And this background process will be killed.

Alex

Hello all,

after I opened a bugreport (https://bugs.kde.org/show_bug.cgi?id=462099) at KDE about the above mentioned problem, the developer suggested I should execute the following command in the console:

Code: Select all

$ kwriteconfig5 --file startkderc --group General --key systemdBoot false


...after that the autostart of my shellscript at the start of the KDE desktop worked fine again.

Problem solved

Greetings
Bluelupo

The problem described by me with the not executed Autostart Shellscript is according to a developer in the bug report #462099 due to a bug in systemd version 249.11-0ubuntu3.6, which is contained in Neon currently in the repositories. In version 250 this bug is fixed.

Bugreport #462099: https://bugs.kde.org/show_bug.cgi?id=462099

To add some value for others who may find this: the `kwriteconfig5` command above doesn't have to be run as root. It creates the file `~/.config/startkderc` if it doesn't already exist. If for whatever reason the new configuration causes other problems you can remove the file if it was newly created or remove the `systemBoot=false` line if there are other configurations you want to keep in the file. You have to log back in for the changes to take effect.

Mehmet

p.s. bluelupo, thank you very much for this post.

I was on the KDE forums to look up something else, saw your post, and thought I'd read it. Only ten minutes previously, I'd notice my custom bindings on my mouse weren't working, but I wasn't planning to investigate it today. Once I read your post, I realised it may be related, ran the `kwriteconfrig5` command, rebooted, and everything works as before.

It's amazing finding a solution to a problem before you even start looking.

p.p.s. I apologise if thank you posts aren't allowed as they clutter the forum. Mods, feel free to delete and let me know for future.