Sound global shortcuts don't work while evince is running

[Valentin Neacsu]

While running evince, the global shortcuts for sound control I have configured in System -> Preferences -> Keyboard Shortcuts (CTRL+ALT+ different keys) stop working until I close evince. I have tried this with both Rhythmbox and Banshee, both exibiting the same behavior. This does not happen with Adobe Reader 8 running.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Also, please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will greatly aid us in tracking down your problem and resolving this bug.

[Valentin Neacsu (valentin.neacsu)]

Yes, it is reproducible.

1. System -> Preferences -> Keyboard Shortcuts:
- Play (or play/pause) -> CTRL + ALT + Home
- Stop playback -> CTRL + ALT + End
- Previous track -> CTRL + ALT + Page Up
- Next track -> CTRL + ALT + Page Down

2. Start Rhythmbox and minimize it to the tray (no taskbar entry) because the global shortcuts only work with it minimized.
3. Test the global shortcuts to verify that they indeed work.
4. Run "evince".
5. Test global shortcuts again and notice they don't work any more.
6. Close "evince".
7. Test global shortcuts and notice they start working again.

[Dimitrios Symeonidis (azimout)]

The list of evince keyboard shortcuts can be seen here:
http://library.gnome.org/users/evince/stable/evince-shortcuts.html.en

The ones you mentioned in your last comment don't seem to be registered by evince, and they don't seem to provoke any event in evince on my machine.

Do they do so in yours?

[Valentin Neacsu (valentin.neacsu)]

Following the steps I described above I always get the same result. Evince doesn't react to they keys, but it does stop Rhythmbox/Banshee from registering them aswell.

[Dimitrios Symeonidis (azimout)]

I'm switching this back to new.

However, I tried assigning the ctrl+alt+home/end/pgup/pgdn keys to volume up/down and they continued working even with evince open... Strange...

[Valentin Neacsu (valentin.neacsu)]

I just did a fresh install of Intrepid x86, as the last one was an upgrade from Hardy x86. I thought this might have something to do with the upgrade process, but it seems it was not the case as the problem is still there, just as I described it above.

[Dimitrios Symeonidis (azimout)]

valentin, is it possible that your bug is a duplicate of this one?
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/263779
that one is marked "fix released" for intrepid...

[Valentin Neacsu (valentin.neacsu)]

Yes, it's the same bug, but contrary to that bug's status, it isn't fixed for Intrepid, at least in my case.

Marking as duplicate.

[Dimitrios Symeonidis (azimout)]

that bug is marked as fixed. if you still have this issue with the latest intrepid updates, then you have a very similar, but still different bug, so not a duplicate...

[Kilian Evang (kevang)]

Dimitrios, I don't think the automatic updates would fix the bug, see https://bugs.launchpad.net/ubuntu/+source/evince/+bug/263779/comments/17 . Marking as duplicate again.