Version: 0.9.15 (using KDE 4.4.2) OS: Linux Global Shortcuts aren't remember between KNotes Sessions Set up global shortcuts for KNotes exit KNotes Restart KNotes All global shortcuts KNotes aren't remembered I also this on the KUubutu 10.10, and KNotes still has this problem Reproducible: Always Steps to Reproduce: Set up global shortcuts for KNotes exit KNotes Restart KNotes All KNotes global shortcuts KNotes aren't remembered Actual Results: All KNotes global shortcuts KNotes aren't remembered between KNotes sessions Expected Results: All KNotes global shortcuts KNotes are remembered OS: Linux (x86_64) release 2.6.32-23-generic Compiler: cc KUbuntu 10.04.1, 64 bit The default Configure Shortcuts box is too small it should be at least 654 pixels wide, and taller too If I edit the shortcuts by clicking defaults, for the ones that have global defaults, the first thing I get something like this: " The shortcut 'Alt+Shift+H' conflicts with the following key combination: Shortcut 'Alt+Shift+H' in Application KNotes for action Hide All Notes " After that, if I click the Reassign button It'll reassign the shortcut without having what it is displayed in the Global column If I give the shortcut a temporary different keyboard shortcut, I can click on default, and the shortcut will work, and show up in the Global column, without displaying the previous message In either of cases, if I exit KNotes, and restart it, then the global keyboard shortcuts I set up don't work The global shortcuts for Klipper seam to work for me, just not the global shortcuts for KNotes The shortcuts are enabled BEFORE I press OK Why isn't there an APPLY button? Looks like All changes take effect even if I hit the Cancel button
I tried KNotes in Gnome, and it looks like the global shortcuts are remembered if I start KNotes from Gnome instead of KDE.
@ Bryan: Isn't this a duplicate of https://bugs.kde.org/show_bug.cgi?id=239078 ?
Seams to be a duplicate, not sure why I posted it again, maybe it was something about it being the 'Global' shortcuts? *** This bug has been marked as a duplicate of bug 239078 ***