Bug 209890 - can't configure shortcuts - settings discard when i try to use it
Summary: can't configure shortcuts - settings discard when i try to use it
Status: RESOLVED DUPLICATE of bug 205070
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 0.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-08 17:57 UTC by Alex Savin
Modified: 2009-10-09 09:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Savin 2009-10-08 17:57:13 UTC 
Version:           3.9.95 (using KDE 4.3.1)
OS:                Linux
Installed from:    SuSE RPMs

can't configure shortcuts - settings discard when i try to use it:
open "configure shortcuts", reassign shortcuts,
try to use - shortcuts settings discard!

always reproducible

Qt: 4.5.2
KDE: 4.3.2 (KDE 4.3.2) "release 5"
KDevelop: 3.9.95 (using KDevPlatform 0.9.95)
Operating System: Linux 2.6.27.29-0.1-pae i686
Distribution: "openSUSE 11.1 (i586)"
Comment 1 Alex Savin 2009-10-08 18:39:14 UTC 
seem as duplicate "Problem 2"(reset shortcuts to defaults) at:
http://bugs.kde.org/show_bug.cgi?id=205070

add, to bug 205070:
this don't work for ANY shortcuts
Comment 2 Andreas Pakulat 2009-10-08 19:36:36 UTC 
if it doesn't work for any of the shortcuts there, thats a problem in kdelibs not kdevelop.
Comment 3 Alex Savin 2009-10-09 01:58:14 UTC 
I try again to reproduce this bug:
this is only kdevelop bug(test other kde4 app), and only for conflict shortcuts (F10, F11),
F10 - Dynamic Word Wrap
F11 - Show Line Numbers
when reassign this action, and use new shortcuts:
it work (only first pass), and then it discard shortcuts settings!!!

i wrote that can't change ANY shortcuts - this fixed after reboot (i'm sorry that not try it before)
Comment 4 Andreas Pakulat 2009-10-09 09:54:55 UTC 
so it really is a duplicate of 205070

*** This bug has been marked as a duplicate of bug 205070 ***