After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 591605 - Multimedia Keys Stop Working and CTRL key was no longer working
Multimedia Keys Stop Working and CTRL key was no longer working
Status: RESOLVED DUPLICATE of bug 125618
Product: gnome-settings-daemon
Classification: Core
Component: plugins
2.26.x
Other All
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2009-08-12 20:59 UTC by Guillaume
Modified: 2010-03-08 15:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Guillaume 2009-08-12 20:59:38 UTC
Please describe the problem:
1st, I am not certain that I filled the bug in the right section. It seems to my knowledge to be a gnome issue with keyboard and shortcut management.

Once the problem started, I was unable to use my keyboard multimedia keys anymore (or shortcut keys), and the CTRL button was working partially for what I wanted.

Steps to reproduce:
1. Go to  System => Preferences => Mouse
2. On the first tab, activate the functionnality for "Display the mouse when the CTRL key is hit"



Actual results:
It activates the functionnality, then the multimedia keys stop working.

Expected results:
I would expect them to continue working normally, and I would expect the CTRL key to behave normally except when hit then release without any other action, which should display where the mouse is.

Does this happen every time?
Both times, yes.

Other information:
It took me a long time to find the root cause of this. I was unable to remember what action causes that issue, and forums weren't of much help.
Comment 1 Jens Granseuer 2010-03-08 15:18:13 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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