Red Hat Bugzilla – Bug 475247
qt/kdelibs: some multimedia keys not supported
Last modified: 2009-11-25 10:14:53 EST
Description of problem:
I've got a Thinkpad T500 and installed Fedora 10 KDE Live i686 with all updates. The mute button seems to work (without grafical feedback) but volume and brightness control buttons do nothing. Not even the volume bar appears.
Before I've used Kubuntu 8.10 and both did fine.
Are you using tpb? If so, you should not be...its old and depreciated.
KDE should handle things natively.
Let me figure out which KDE component handles this and get your bug moved to get attention.
Wait, brightness should be handled automagically at the hal level, no?
hal-info is probably the way to go here (which contains the keycode to event mappings).
Created attachment 326159 [details]
I've used tpb just for testing because KDE shows me anything at all. KDE 3.5 had an extra section for thinkpads within the system settings but there seems to be nothing left.
The guidance power manager sets brightness according to AC or battery correctly, so something must work.
Attached lshal output (as root).
afaik, these keymapping->events happens at a level lower than kde.
For example, I can switch to a vt, and brightness keys work there too.
Hopefully, the hal-info folks can chime in with some helpful advice.
any news? this is really a show stopper. i've tested fedora 10 kde live i686 on my girlfriends thinkpad r60 and it isn't working either.
now i've tried fedora 10 gnome live i686 on thinkpad t500 and everything is doing fine. it seems to me to be a problem on the kde4-hal-interface.
KDE4 has never had keybindings for volume control (we're working upstream to correct that asap).
In the meantime, I still assert that brightness control is (should be!) DE-agnostic.
Is there a workaround available? What can I do to get things working? Is anyone interested in getting paid for fixing that?
(In reply to comment #9)
> In the meantime, I still assert that brightness control is (should be!)
Well, we have to use X in the session, and the user has preferences (for inctance the auto-dim threshold) that need getting from the session.
THB, you just need to listen for the X keys now, everything is going through evdev these days.
Thanks Richard, I think now it is a qt issue (from speaking with an upstream qt/kde developer)... it seems qt doesn't currently grok brightness key events.
I have a Dell Vostro 1400 and I have the same problem with fedora 10.
Until fedora 9 everything was fine.
Now I can't bind fn+brightness keys
I get an error saying QT doesn't recognize the key. But other fn+key combinations work fine.
since the update to kde 4.2 volume keys are fine, but kde doesn't show an OSD information if i press the mute button.
brightness keys still don't work.
I also have a Dell Vostro 1400 and can report the exact same behaviour. The multimedia keys are recognized just fine, but not the brightness keys.
In the KDE Global Keyboard Shortcuts config for guidance-power-manager (which controls brightness now it seems) if I try to set the right keys for Brightness Up and Down, I get the following error : "the key you just pressed isn't supported by qt"
The keycodes are:
Up : 233
Down : 232
I can confirm this with HP Pavilion dv5t:
keycode 233 (keysym 0x1008ff02, XF86MonBrightnessUp)
keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown)
BTW, there are two power managers which may change brightness and notebook behavior: Guidance Power Manager and Power Management - KDE Control Module. Is that normal?
Power Management - KDE Control Module is more flexible and it may be tuned to change brightness on its own, for example, when the battery is short of charge, or when the notebook is idle for some time. However, it does not have hot keys to change brightness on user request.
Guidance Power Manager has these hotkeys but it is much less flexible in regard of various power profiles.
I can also report a similar behaviour on a Thinkpad x300...
Fedora 10 with KDE 4.2.1 will not recognize the Fn+Fxx buttons, thought they appear correctly mapped with the expected XF86 codes... and xev shows the inputs captured as well.
When trying to assign the key *manually* in KDE - System Settings -> Global Keyboard Shortcuts, I get the error:
"The key you just pressed isn't supported by Qt"
These keys are working as expected on the same hardware with GNOME (either with Fedora 10 or Ubuntu 8.10)
# lshal|grep system.kernel
system.kernel.machine = 'x86_64' (string)
system.kernel.name = 'Linux' (string)
system.kernel.version = '22.214.171.124-170.2.35.fc10.x86_64' (string)
# lshal|grep system.hardware
system.hardware.product = '647815G' (string)
system.hardware.vendor = 'LENOVO' (string)
system.hardware.version = 'ThinkPad X300' (string)
# xmodmap -pk|grep XF86MonBrightness
232 0x1008ff03 (XF86MonBrightnessDown) (...)
233 0x1008ff02 (XF86MonBrightnessUp) (...)
*** Bug 486167 has been marked as a duplicate of this bug. ***
Upstream is aware of this issue, however we have no ETA on a fix. Watch this space for updates.
Who is upstream? Qt?
Yes its Qt/Trolltech
Going to close this as UPSTREAM. Since there is little the KDE-SIG can do about this and other multimedia/laptop button issues we have to wait for upstream to address this.
Just to make things clear... I don't like when submitted and confirmed bugs end like this. It just means that this system designed to fix bugs does'n work.
This bug still exists and, though not critically, reduces some functionality of a laptop. It is important because it relates to power managament which is important on laptops.
Now, you are closing this bug but we would like to know exactly, what have you done? Have you submitted a patch for Qt? Have you received any answer from them? Qt is open source now, so you could fix it yourself instead of closing it.
What's going on here? Why keep bugzilla running if it does not work even with this, I think, trivial bug?
at least i'd like to know the url of this bug in the qt bugtracker.
*** Bug 502702 has been marked as a duplicate of this bug. ***
First this bug is still present on F11. The workaround with keyboard and guidance-power-manager doesn't work anymore because there are no guidance-power-manager option in the keyboard shortcut.
Second this bug doesn't exist on kubuntu. There are others and multiple bug on this distribution so it's why I was trying to migrate to F11 but as usual KDE is a second zone citizen too bad.
Work around on t61p:
chmod a+rw /proc/acpi/ibm/cmos
(xbindkey '(XF86MonBrightnessUp) "echo 4 > /proc/acpi/ibm/cmos")
m:0x0 + c:233
(xbindkey '(XF86MonBrightnessDown) "echo 5 > /proc/acpi/ibm/cmos")
m:0x0 + c:232
run xbindkeys to activate the settings.
updating upstream bug #, as well as relevant trolltech report,
As well as launchpad tracker,
Mandriva, has some patches as well,
Sheesh, what a mess. :(
OK, re-opening here, and I'll see if I can make some sense from all the separate attempts to tackle this for us.
hooray for helio for getting things upstreamed,
OK, seems to work like a charm.
* Sat Aug 18 2009 Rex Dieter <email@example.com> 4.5.2-7
- kde-qt: 287-qmenu-respect-minwidth
- kde-qt: 0288-more-x-keycodes (#475247)
built for rawhide, will (likely) be included in next qt refresh for F-10/F-11 as well, provided there are no objections from our fellow qt maintainers.
Now, powerdevil (and friends) need some keyboard shortcuts, leaving that for upstream kde.
No objections here, bug fixing is a good thing!
qt-4.5.2-1.fc10.2 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update qt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-8398
qt-4.5.2-1.fc11.2 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update qt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-8406
Still the same behavior on Thinkpad T500 using Fedora 10 i686.
qt-4.5.2-2.fc11 has been submitted as an update for Fedora 11.
qt-4.5.2-2.fc10 has been submitted as an update for Fedora 10.
Julian, the keybindings may well still be lacking, but you should be able to at least assign the keys now, ie, you shouldn't get the "Qt doesn't recognize the key" type errors.
I can confirm the same old behavior on a dell vostro 1400 using fully updated F11 and KDE -- including the updates-testing packages.
what exactly is "old behavior"?
media keys not working by default?
media keys not assignable?
and, while we're at it, declare precisely what you're testing,
rpm -q qt kdelibs
Now, for *me* using qt-4.5.2-1.2 and newer, I can now at least assign brightness keys, whereas I previously saw "Qt doesn't recognize the key".
Old behavior as in I still get the "Qt does not recognize the key" error when attempting to set the brightness keys.
rpm -q qt kdelibs
The fix went in qt-4.5.2-1.2 and later (you're testing 4.5.2-1.1)
My mistake, I thought I had updated properly yesterday from the updates-testing repo. I can now assign the keys just fine in the KDE system settings. However, the keys do not appear to have any effect after they are assigned. And kde settings does remember the assignments. Possibly a bug for kde/guidance-power-manager?
Possibly, but that's a separate issue.
I'm able to set the keys for guidance-power-manager (which is removed on my system in favor of powerdevil). Maybe I missed it but i can't find the place to set brightness keys for powerdevil.
yeah, that's what I implied by comment #37 about keybindings missing. Powerdevil in particular has none currently.
*** Bug 518288 has been marked as a duplicate of this bug. ***
qt-4.5.2-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
qt-4.5.2-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 509295 has been marked as a duplicate of this bug. ***
*** Bug 509296 has been marked as a duplicate of this bug. ***
Still not working in qt-4.5.2-3
that bug isn't about multimedia keys, prob shouldn't be dup'd to this.
kdebase-workspace-4.3.3-7.fc10, kdelibs-4.3.3-4.fc10, kdebase-runtime-4.3.3-5.fc10, kdeaccessibility-4.3.3-1.fc10, kdeadmin-4.3.3-1.fc10, kdeartwork-4.3.3-1.fc10, kdebase-4.3.3-3.fc10, kdeedu-4.3.3-1.fc10, kdegames-4.3.3-2.fc10, kdegraphics-4.3.3-1.fc10, kdelibs-experimental-4.3.3-1.fc10, kdemultimedia-4.3.3-1.fc10, kdenetwork-4.3.3-4.fc10, kdepim-4.3.3-1.fc10, kdepim-runtime-4.3.3-1.fc10, kdepimlibs-4.3.3-1.fc10, kdeplasma-addons-4.3.3-1.fc10, kdesdk-4.3.3-1.fc10, kdetoys-4.3.3-1.fc10, kdeutils-4.3.3-1.fc10, konq-plugins-4.3.3-2.fc10, oxygen-icon-theme-4.3.3-1.fc10, qscintilla-2.4-7.fc10, webkitkde-0.0.2-0.1.20091109svn.fc10, kde-l10n-4.3.3-1.fc10, sip-4.9.3-1.fc10, PyKDE-3.16.6-1.fc10, PyQt4-4.6.2-1.fc10, qzion-0.4.0-5.fc10, qedje-0.4.0-4.fc10, PyQwt-5.2.0-2.fc10, PyQt-3.18.1-5.fc10, kdebindings-4.3.3-4.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
kdebase-workspace-4.3.3-7.fc11, kdelibs-4.3.3-4.fc11, kdebase-runtime-4.3.3-5.fc11, kdeaccessibility-4.3.3-1.fc11, kdeadmin-4.3.3-1.fc11, kdeartwork-4.3.3-1.fc11, kdebase-4.3.3-3.fc11, kdeedu-4.3.3-1.fc11, kdegames-4.3.3-2.fc11, kdegraphics-4.3.3-1.fc11, kdelibs-experimental-4.3.3-1.fc11, kdemultimedia-4.3.3-1.fc11, kdenetwork-4.3.3-4.fc11, kdepim-4.3.3-1.fc11, kdepim-runtime-4.3.3-1.fc11, kdepimlibs-4.3.3-1.fc11, kdeplasma-addons-4.3.3-1.fc11, kdesdk-4.3.3-1.fc11, kdetoys-4.3.3-1.fc11, kdeutils-4.3.3-1.fc11, konq-plugins-4.3.3-2.fc11, oxygen-icon-theme-4.3.3-1.fc11, qscintilla-2.4-7.fc11, webkitkde-0.0.2-0.1.20091109svn.fc11, sip-4.9.3-1.fc11, kde-l10n-4.3.3-1.fc11, PyKDE-3.16.6-1.fc11, PyQt4-4.6.2-1.fc11, qzion-0.4.0-5.fc11, qedje-0.4.0-4.fc11, PyQwt-5.2.0-2.fc11, PyQt-3.18.1-5.fc11, kdebindings-4.3.3-4.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
kdebase-workspace-4.3.3-7.fc12, kdelibs-4.3.3-4.fc12, kdebase-runtime-4.3.3-5.fc12, kde-l10n-4.3.3-1.fc12, kdeaccessibility-4.3.3-2.fc12, kdeadmin-4.3.3-1.fc12, kdeartwork-4.3.3-1.fc12, kdebase-4.3.3-3.fc12, kdeedu-4.3.3-2.fc12, kdegames-4.3.3-2.fc12, kdegraphics-4.3.3-1.fc12, kdelibs-experimental-4.3.3-1.fc12, kdemultimedia-4.3.3-2.fc12, kdenetwork-4.3.3-5.fc12, kdepim-4.3.3-1.fc12, kdepim-runtime-4.3.3-1.fc12, kdepimlibs-4.3.3-1.fc12, kdeplasma-addons-4.3.3-1.fc12, kdesdk-4.3.3-1.fc12, kdetoys-4.3.3-1.fc12, kdeutils-4.3.3-1.fc12, konq-plugins-4.3.3-2.fc12, oxygen-icon-theme-4.3.3-1.fc12, qscintilla-2.4-7.fc12, webkitkde-0.0.2-0.1.20091109svn.fc12, sip-4.9.3-1.fc12, qzion-0.4.0-5.fc12, qedje-0.4.0-4.fc12, PyQwt-5.2.0-3.fc12, PyQt-3.18.1-5.fc12, kdebindings-4.3.3-4.fc12, PyKDE-3.16.6-1.fc12, PyQt4-4.6.2-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.