Bug 185453 - The key you just pressed isn't supported by Qt
Summary: The key you just pressed isn't supported by Qt
Status: RESOLVED DUPLICATE of bug 182672
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 4.2.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-24 17:58 UTC by Marc Benstein
Modified: 2009-03-14 16:54 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Benstein 2009-02-24 17:58:42 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

When trying to assign the WWW key to a keyboard shortcut the message: "The key you just pressed isn't supported by Qt" is displayed

I guess this is more of a Qt (both 4.4 and 4.5rc) problem, however it occurs in
the KDE control center.
When trying to assign a function to the multimedia keys of my keyboard, in one
case a requester occurs telling me that "this key isn't supported by Qt". All
other multimedia keys work as expected.

xev, however, definitely shows this key as supported:

KeyPress event, serial 34, synthetic NO, window 0x2a00001,
    root 0x1a6, subw 0x0, time 7298993, (112,10), root:(117,35),
    state 0x10, keycode 178 (keysym 0x1008ff2e, XF86WWW), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x2a00001,
    root 0x1a6, subw 0x0, time 7299054, (112,10), root:(117,35),
    state 0x10, keycode 178 (keysym 0x1008ff2e, XF86WWW), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

As XF86WWW seems like a rather standard multimedia key, this seems to be some
defective behaviour of Qt?!?


Reproducible: Always

Steps to Reproduce:
1. start KDE control center
2. assign input action to XF86wWW-key
Comment 1 Marc Benstein 2009-02-24 17:59:59 UTC
This was originally reported downstream here: https://bugzilla.novell.com/478492
Comment 2 Elián Hanisch 2009-03-04 17:23:35 UTC
I have the same bug, but for sleep key of my keyboard. Kubuntu 8.10 with kde 4.2

xev output
KeyPress event, serial 34, synthetic NO, window 0x6600001,
    root 0x1a6, subw 0x0, time 17453976, (-557,675), root:(534,700),
    state 0x10, keycode 150 (keysym 0x1008ff2f, XF86Sleep), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x6600001,
    root 0x1a6, subw 0x0, time 17454120, (-557,675), root:(534,700),
    state 0x10, keycode 150 (keysym 0x1008ff2f, XF86Sleep), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

I can't use XF86Sleep in any shortcut

I also tried to reproduce for XF86WWW, but my keyboard has in it's place XF86HomePage which works.
Comment 3 Ivan Mironov 2009-03-10 08:04:54 UTC
I have same problem for XF86WWW. KDE 4.2.1, Qt 4.5, Gentoo ~amd64.
Comment 4 unggnu 2009-03-12 12:06:51 UTC
I can confirm this problem. Brightness keys doesn't work while they have keycodes with Xev.

KeyRelease event, serial 35, synthetic NO, window 0x3000001,
    root 0xab, subw 0x0, time 999639, (-629,210), root:(458,235),
    state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 35, synthetic NO, window 0x3000001,
    root 0xab, subw 0x0, time 1000020, (-629,210), root:(458,235),
    state 0x0, keycode 233 (keysym 0x1008ff02, XF86MonBrightnessUp), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False
Comment 5 Lamarque V. Souza 2009-03-12 17:09:08 UTC
I think this is a duplicate of bug https://bugs.kde.org/show_bug.cgi?id=182672
Comment 6 unggnu 2009-03-12 20:09:54 UTC
Yeah, it is a duplicate. I don't know how to mark it as such.
Comment 7 Lamarque V. Souza 2009-03-12 20:19:10 UTC
Do not worry, some KDE developer will mark it as duplicate. Since it is likely a Qt's bug someone should inform Trolltech/Nokia about it.
Comment 8 Jonathan Marten 2009-03-14 16:54:36 UTC
As requested...

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