[regression] Gnome, mouse locate-pointer config stops multimedia keys from working after Intrepid upgrade

Bug #300954 reported by Voroshilov Vladimir
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I was using Ubuntu 8.10 (Intrepid) with GNOME on my Dell 500 Laptop for a some time all was fine.

After recent update via Update Manager, some multimedia keys (Mute, Play, Stop) stopped working.
Next and Prev buttons works only if Rhythmbox window is active.
VolumeUp and VolumeDown still works.

Unfortunately i can not localize which update caused regression.
It happend somewhen since Nov 14.

xev sucessfully catches buttons pressing:

KeyPress event, serial 33, synthetic NO, window 0x2800001,
    root 0x7a, subw 0x0, time 86399880, (-424,553), root:(248,604),
    state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x2800001,
    root 0x7a, subw 0x0, time 86400086, (-424,553), root:(248,604),
    state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x2800001,
    root 0x7a, subw 0x0, time 86400938, (-424,553), root:(248,604),
    state 0x0, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x2800001,
    root 0x7a, subw 0x0, time 86401142, (-424,553), root:(248,604),
    state 0x0, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x2800001,
    root 0x7a, subw 0x0, time 86401391, (-424,553), root:(248,604),
    state 0x0, keycode 174 (keysym 0x1008ff15, XF86AudioStop), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x2800001,
    root 0x7a, subw 0x0, time 86401595, (-424,553), root:(248,604),
    state 0x0, keycode 174 (keysym 0x1008ff15, XF86AudioStop), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

But nothing happend after key pressing.

P.S. I tried also assigning Mute key to "Open Home Folder" and it does not working too (home folder does not appear after pressing the key).

Revision history for this message
Voroshilov Vladimir (voroshil) wrote :
Revision history for this message
Martin Kossick (hacktick) wrote :

Hi,
thank you for reporting this.
Did Intrepid support these buttons out-of-the-box?
Are you using a dell-ppa?

greetings

Martin

Revision history for this message
Voroshilov Vladimir (voroshil) wrote :

Yes, it did.
Keys worked fine in Intrepid for several weeks after upgrade from Hardy to Intrepid.

No, I'm using official Ubuntu repository only.

Revision history for this message
linfidel (linfidel) wrote :

I am having a similar problem, which started right after upgrading to Intrepid from Hardy. I'm using Compiz, and used Compix Configuration Mgr to reassign some keys, some of which work and some don't now.

The keys I know that no longer work are mute (XF86AudioMute), home (XF86HomePage), E-mail (XF86Mail), Media (XF86AudioMedia), and media control keys like XF86AudioPlay, I believe. I don't actually use them very often.

The keys are recognized; if I try to assign them in either the CCM app, or the keyboard shortcuts, they get picked up. In fact, I can assign the home page key using the combination of Alt-Home.

It must be something in my home directory, as I can create a new login account, and they work there, except the Home key brings up Nautilus instead of my web browser.

Also, I went through and temporarily deleted the folders .gconf and .gconfd, and the keys (at least some of them) started working. But I've gone through the gnome configuration editor, trying everything I could, and didn't find anything that would have any effect.

I'm willing to try any other suggestions.

Revision history for this message
Voroshilov Vladimir (voroshil) wrote :

After removing ~/.gconf/desktop/gnome/peripherals/mouse/%gconf.xml and restarting Gnome, all multimedia keys
starts to work again.
I've attached contents of removed file.

Revision history for this message
linfidel (linfidel) wrote :

1. This bug (at least for me) was not a duplicate of 294400.
2. As unlikely as it sounded to me, especially after looking at the file, I tried the method of Voroshilov Vladimir, removed my %gconf.xml file, and it fixed my problem. The mute key works now, along with the the play controls. Previously, I could get some of the application keys to work by using the Compiz Config utility, but not by using the standard gnome keyboard settings. Now they work correctly, too.

Thank you, Voroshilov Vladimir, for your fix. I don't think I would have been able to isolate it to that file.

Revision history for this message
Kjetil Thuen (kjetil-thuen) wrote :

This is not a duplicate of 294400...

After reading Vladimirs suggestion, I have found that I can consistently stop my play, next, prev and mute buttons from working by enabeling the locate mouse pointer feature in the mouse preferences. When I disable the feature, the multimedia keys start working again.

This behaviour is consistent across several 8.10 installations, one of them just a couple of weeks old.

Revision history for this message
Chris Bainbridge (chris-bainbridge) wrote : Re: [regression] Gnome, old %gconf.xml in home dir stops multimedia keys from working after Intrepid upgrade

Changed bug to represent fact that this is a Gnome problem rather than the xorg bug #294400

Revision history for this message
J. Bruce Fields (bfields-fieldses) wrote :

"After reading Vladimirs suggestion, I have found that I can consistently stop my play, next, prev and mute buttons from working by enabeling the locate mouse pointer feature in the mouse preferences. When I disable the feature, the multimedia keys start working again."

Confirmed on my laptop (a Dell 1420n). The fast-forward/rewind/play/stop keys work if and only if the locate-mouse-pointer feature is turned off. I'm also using intrepid.

Revision history for this message
Steve Beattie (sbeattie) wrote :

The gnome-control-center package provides the gnome-mouse-settings binary that toggles this, though I'm not sure where the actual bug lies within the gnome stack. Confirming based on comments.

Revision history for this message
Rick Spencer (rick-rickspencer3) wrote :

Robert - this is an Intrepid bug. Please take a look.

Changed in gnome-control-center (Ubuntu):
assignee: canonical-desktop-team → robert-ancell
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Also confirming. When /apps/desktop/gnome/peripherals/mouse/locate_pointer is True the multimedia keys work if you hold them down for a short time, then they are detected on release. When it is False they behave as normal.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Further observations when locate_pointer is enabled:
- The multimedia keys don't work reliably when held down. They appear to work randomly <5% of the time they're pressed. It may be the key repeat that triggers this when holding them down.
- Volume up/down always work, volume mute behaves like the other multimedia keys
- When Rhythmbox was open I was mashing the media keys and then rhythmbox locked up for a few seconds. When it came back all/some of the keys pressed were activated and the new notification system flashed the operations in quick succession.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Uninstalled notify-osd and ran gnome-settings-daemon in the foreground:
gnome-settings-daemon --debug --no-daemon 2>&1 | tee /tmp/gsd.log

This shows the error messages about reaching the notification service don't occur reliably - rules out notify-osd as causing the problem..

Changed in gnome-control-center (Ubuntu):
assignee: robert-ancell → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.