Bug 651834 - KDM 4.5.2 keyboard shortcuts not working (regression)
Summary: KDM 4.5.2 keyboard shortcuts not working (regression)
Keywords:
Status: CLOSED DUPLICATE of bug 631767
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-10 12:14 UTC by Andrei ILIE
Modified: 2010-11-12 10:01 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-11 16:25:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Andrei ILIE 2010-11-10 12:14:19 UTC 
The keyboard shortcuts (alt+r, alt+t, alt+c) don't work anymore
in the kdm's "restart/poweroff/cancel" dialog.

   This used to work without a glich for KDE 4.0-4 series, so it is an
(obvious) regression.
Comment 1 Rex Dieter 2010-11-10 16:00:05 UTC 
I can't reproduce this with stock f13.

Though, there is a known problem that exhibits these same symptoms when using qt-4.7.x.

rpm -q qt

please.
Comment 2 Rex Dieter 2010-11-10 16:13:32 UTC 
Oh goodie, seems kde-4.5.3 may fix this combination (when used with qt-4.7 too), mind testing that?  (it's currently in updates-testing repo).
Comment 3 Rex Dieter 2010-11-10 16:16:05 UTC 
oh, nevermind, shortcuts work all the way up to that last screen, then fail still.

We've got an open bug on that (seems that final dialog has problem getting focus, as even tabbing doesn't work to select the various buttons either), I'll see if I can find it.
Comment 4 Rex Dieter 2010-11-10 16:27:18 UTC 
See related/similar bug #643409 , does that fit what you're seeing here?
Comment 5 Andrei ILIE 2010-11-11 16:25:17 UTC 
yes - looks like someoane else spot that bug first

*** This bug has been marked as a duplicate of bug 643409 ***
Comment 6 Andrei ILIE 2010-11-12 10:01:21 UTC 

*** This bug has been marked as a duplicate of bug 631767 ***
Note You need to log in before you can comment on or make changes to this bug.