Description of problem: kdm shutdown menu lose keyboard control Version-Release number of selected component (if applicable): kdm-4.5.2-1.fc14.i686 How reproducible: every time Steps to Reproduce: 1. invoke kdm shutdown menu pressing ALT-M, then ALT-S 2. 3. Actual results: keyboard shortcuts does not work Expected results: Additional info:
To be clear, the first steps, ALT-M, ALT-S work, but the box that appears that includes options: "Turn off Computer" "Restart Computer" ... "Cancel" does not respond to keyboard, either ALT-... shortcuts, or tab (which is supposed to select the next button). Tested also on f13, works fine there, so is f14-specific... perhaps some sort of qt47'ism?
This upstream ml thread may be relevant, http://lists.kde.org/?t=128708520600001&r=1&w=2 talks about xorg-server >= 1.9.0 + qt47 = loss of focus sometimes, which seems to fit the symptoms here.
Forgot to mention - this is with a default theme, Goddard. Tested with Constantine too - the same.
Oops, sorry, Laughlin, not Goddard.
*** Bug 651834 has been marked as a duplicate of this bug. ***
This focus-related problem of newly opened dialog is system wide unfortunately (probably kdelibs related). I see this on root authentication dialog, when kPackageKit needs privilege escalation for example (KDE 4.4.5 and KDE 4.5.2).
the polkit-auth thing not getting focus is different (occurs with qt-4.6 too). BTW, you never confirmed my question, are you or are you not using qt-4.7.x on f13?
btw, this bug was also filed as #631767
(In reply to comment #7) > the polkit-auth thing not getting focus is different (occurs with qt-4.6 too). > > BTW, you never confirmed my question, are you or are you not using qt-4.7.x on > f13? don't now exactly (i'm at work now) I only have official f13 packages + official updates
(In reply to comment #9) > (In reply to comment #7) > > the polkit-auth thing not getting focus is different (occurs with qt-4.6 too). > > > > BTW, you never confirmed my question, are you or are you not using qt-4.7.x on > > f13? > > don't now exactly (i'm at work now) > I only have official f13 packages + official updates ...but I think your qt-4.7.x question was addressed to the reporter of this bug, Armands Liepins
I suggest closing this bug as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=631767
*** This bug has been marked as a duplicate of bug 631767 ***
Removing qt47 blocker, it's not a Qt 4.7 issue.
It *is* a qt-4.7 issue in my own testing. with qt-4.6: not reproducible with qt-4.7: is reproducible Does anyone experience otherwise?
I guess it could be simply f14-specific, let me retest installing qt-4.7 on a f13 to check again.