Hide Forgot
Description of problem: On my system, I have a keyboard shortcut mapping key F3 to the "Play/Pause" multimedia action. As far as I can tell, the behavior of dbus is: when starting a multimedia application, it grabs the right to see the multimedia key; when I press a multimedia key like F3, dbus sends it to the most recently started multimedia application. I don't know if I've got that right. Today I ran into surprising and undesirable behavior of my multimedia keys. Here's the situation I experienced. I keep Exaile, an audio player, running almost constantly to provide background music. At one point, I paused Exaile and then watched a short movie with a video player like Totem. After watching the movie, I tried to unpause Exaile and go back to listening to music, onlyto discover that my F3 pause key no longer had any effect. When running dbus-monitor, I saw that the event generated was something like: signal sender=:1.5 -> dest=(null destination) serial=89 path=/org/gnome/SettingsDaemon/MediaKeys; interface=org.gnome.SettingsDaemon.MediaKeys; member=MediaPlayerKeyPressed string "totem" string "Play" However totem was not running (verified with "ps auxw | grep -i totem"). In any case, Exaile wasn't receiving the Play/pause event, and the event seemed to disappear into a black hole, to be ignored. This was not desirable. Possible explanatory factor: at several points when running totem, it crashed. It's entirely possible that the last time I ran totem, it crashed rather than exiting cleanly. Could this have caused Dbus to still think that it should direct multimedia key events to totem (because Dbus thought that totem is still running)? If so, should Dbus be improved somehow so it is more robust when applications don't exit cleanly? This seems like undesirable behavior. I've marked this as low priority because this is the first time I've had it happen, and if it only happens when an application crashes uncleanly, then hopefully it won't hit other users too frequently -- but it still sounds like a bug/design shortcoming that would be nice to fix, if there's a reasonable way to do so.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping