Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages Eike, I apologize for this, but I wanted to hand it off and see if you heard anything or witnessed anything like what many Ubuntu/GNOME users are reporting in Launchpad. The original report is located at https://bugs.edge.launchpad.net/ubuntu/+source/yakuake/+bug/248661. Any info would be great and if there is anything I can do to help please let me know. Thanks!
I can't say I'm familiar with this problem so far, but given the long track record of issues with the rewritten global shortcuts system in KDE 4 it doesn't surprise me, either. The first-run dialog does work fine in my KDE here, though; I may have to set up an Ubuntu virtual machine with Gnome to try it there. In general, it is noteworthy that global shortcuts involve a central authority a lot more in KDE 4 than they did in KDE 3 (the shortcut is now stored in a global config file, kglobalshortcutsrc, and the conflict checking is actually supposed to work, etc.). My gut feeling tells me that makes it more likely not to work well outside of KDE. Conflict-checking also only applies to KDE apps, I guess, so if something non-KDE inside the user's Gnome session is already using up the F12 key, things may not work. Another tip: Rather than use the D-Bus command to open Yakuake in the case of shortcut problems, simply rerunning Yakuake 2.9.1 and higher will toggle the window state as well (also allowing to conveniently open/close Yakuake from a panel button or similar).
Closing this due to lack of information.