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 454828 - Opening gparted causes Rhythmbox to stop playing
Opening gparted causes Rhythmbox to stop playing
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: Removable Media
0.10.0
Other All
: Normal minor
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-08 12:17 UTC by Phil Bull
Modified: 2018-05-24 12:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Log files (114.96 KB, application/x-compressed-tar)
2007-07-11 15:10 UTC, Phil Bull
Details

Description Phil Bull 2007-07-08 12:17:01 UTC
Please describe the problem:
If Rhythmbox is playing a song, opening gparted (System -> Administration -> GNOME Partition Editor) causes Rhythmbox to stop playing and change to the 'Not Playing' status. This occurs during the period when gparted is showing the 'Scanning all devices...' label. Rhythmbox remains 'Not Playing' until the user presses play again.

It seems that the bug only occurs when I have a USB (mass storage) MP3 player plugged-in which has music files on it. If it is not plugged in, the bug doesn't happen.

rhythmbox 0.10.0-0ubuntu2 (Ubuntu Feisty)
gparted 0.2.5-2ubuntu2 (Ubuntu Feisty)

Steps to reproduce:
1. Plug-in a USB Mass Storage device with songs on it
2. Play song(s) in Rhythmbox
3. Open gparted


Actual results:
Rhythmbox will stop playing, whether or not the song being played is on the removable volume

Expected results:
Rhythmbox should not stop playing if the song being played is NOT on the removable drive

Does this happen every time?
Yes

Other information:
Bug originally reported on the Ubuntu bugtracker:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/121853

Output of `rhythmbox -d 2> rb.log`:
http://launchpadlibrarian.net/8175835/rb.log.tar.gz
Comment 1 Jonathan Matthew 2007-07-11 11:29:33 UTC
The interesting bits are:

(11:16:05) [0x80f4028] [rhythmdb_volume_unmounted_cb] rhythmdb-monitor.c:423: volume file:///home unmounted

(11:16:06) [0x80f4028] [rhythmdb_volume_mounted_cb] rhythmdb-monitor.c:401: volume file:///home mounted

(11:16:07) [0x80f4028] [rb_removable_media_manager_mount_volume] rb-removable-media-manager.c:428: detecting new media - display name=/home

So, something gparted is doing is making rhythmbox think your /home filesystem is being unmounted and remounted.
Comment 2 Phil Bull 2007-07-11 12:32:47 UTC
Possibly, but I don't get the bug when only /home is mounted initially - it only happens when there is another music-containing volume mounted too.

If it was caused by /home mounting and unmounting, wouldn't I expect to get the same issue whether there was another device plugged in or not?

Thanks
Comment 3 Jonathan Matthew 2007-07-11 12:47:39 UTC
Output from 'rhythmbox -D rhythmdb-monitor' in both cases would be helpful.  There don't seem to be any mount/unmount events other than those for /home in the above output.
Comment 4 Phil Bull 2007-07-11 15:10:08 UTC
Created attachment 91627 [details]
Log files

Results of running the command below and then opening gparted.

phil@jaguar:~$ rhythmbox -D rhythmdb-monitor 2>rb.log

rb_no_usb_disk.log - results of running command with NO USB disk plugged in
rb_usb_disk_connected.log - results of running command with the USB disk plugged in

I plugged in a USB disk without audio files on it this time (only videos), and the same bug occurred.
Comment 5 GNOME Infrastructure Team 2018-05-24 12:41:05 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/398.