Closing Rhythmbox doesn't close Rhythmbox and causes confusing key-binding behavior

Bug #1036489 reported by Jono Bacon
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This is a problem I am experiencing in Quantal right now. Here is how to trigger it:

 1. I load Pithos and start listening to music. My track change and start/pause key-bindings work great.
 2. I load Rhythmbox to listen to a song on my computer. I stop Pithos playing and start playing Rhythmbox.
 3. With two media players open my key-bindings only seem to apply to one player, so I close Rhythmbox (clicking the X in the window).
 4. The window is not actually closed and my key-bindings still affect Rhythmbox - this is confusing as I see no icon on my Launcher.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: unity 6.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
Date: Mon Aug 13 21:20:01 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jono Bacon (jonobacon) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
Revision history for this message
Ste (ilpillo) wrote :

I can confirm this bug in Ubuntu 12.04 (precise) 64 bit
I'm using gnome-shell 3.4.

when I close Rhythmbox clicking the X in the window the music doesn't stop!
Of course if I check the process list I see :
 ps xf | grep rhythmbox
14869 pts/0 S+ 0:00 \_ grep rhythmbox
14627 ? Sl 0:16 rhythmbox

affects: unity (Ubuntu) → rhythmbox (Ubuntu)
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in rhythmbox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Leonardo Jeanteur (speedphoenix) wrote :

This still affects me in Ubuntu 20.04.

Fully closing Rhythmbox does not free up the media keys, and if you reopen it later the media keys will not work (and won't work for other programs either)

Different ways to reproduce (note that the only way to have the media keys working again is to restart the machine)

1. Verify that the media keys work (restart the machine if not)
2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
3. reopen rhythmbox, the media keys do not work.

1. Verify that the media keys work (restart the machine if not)
2. End the 'rhythmbox' process
3. reopen rhythmbox, the media keys do not work.

1. Verify that the media keys work (restart the machine if not)
2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin
3. click the 'restart' next to "Restart the player for the changes to take effect"
4. once rhythmbox restarts, the media keys do not work anymore.

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.