Version: (using KDE KDE 3.4.1) Installed from: Debian testing/unstable Packages OS: Linux First off, I'm using ubuntu not debian unstable but it was the closest listed. I have my account already created using kde 3.4 and khotkeys was fine. However since upgrading to 3.4.1 khotkeys is non fuctional and crashes if tried to launch: mcquaid@mcquaid:~$ khotkeys ERROR: Communication problem with khotkeys, it probably crashed. But, on a new users account khotkeys works without issue. So this seems to be a transition bug going from 3.4 to 3.4.1 I tried copying khotkeysrc and khotkeys_update from a working users account but it did not resolve the issue. Please tell me what other files khotkeys uses in a users ~.kde dir as I did not want to delete my ~.kde dir to start from scratch to solve the issue.
This happen to me too with KDE SVN 3.4.2. On laptop Centrino. I never used KHotKeys. I read an interesting article on a Magazine, but after configured KHotKeys it doesn't work so I tryed to see if khotkeys daemon was working... No, it wasn't. It crashes at KDE startup: %gdb khotkeys GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-slackware-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run Starting program: /opt/kde34/bin/khotkeys [Thread debugging using libthread_db enabled] [New Thread -1231493440 (LWP 5068)] ERROR: Communication problem with khotkeys, it probably crashed. Program exited with code 0377. (gdb)
It seems that running kcmshell khotkeys does work, and it also appears to be that it is avaliable under Control Center->Regional & Accessibility as well. I'm not sure if this was caused by running the previous command.
Probably this happens because khotkeys is already running as a kded module and the standalone instance refuses to start giving a spurious error. Try for instance: $ dcop kded khotkeys quit $ khotkeys $ killall khotkeys $ dcop kded kded loadModule khotkeys $ khotkeys ERROR: Communication problem with khotkeys, it probably crashed.
Correct, you're not supposed to run it manually, there's usually a kded module used instead. Can you still reproduce the actual problem?
This bug seems to be fixed with KDE 3.4.3.