Rhythmbox crashes after few seconds

Bug #1121094 reported by jonaternet
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This happens anytime I try to launch Rhythmbox.
I always get this error, (edit) and If I try to launch it from command line :

RhythmDB:ERROR:rhythmdb-tree.c:1517:remove_child: assertion failed: (g_hash_table_remove (parent->children, data))

When launching Rhythmbox with --debug, I get just before the crash :

couldn't access file:///media/gro/musique2/Underground_-_B.O/09 - Unknown Artist - Track 9.mp3: Error when getting information for file '/media/gro/musique2/Underground_-_B.O/09 - Unknown Artist - Track 9.mp3': No such file or directory
(12:37:06) [0x1deaed0] [song_update_availability] rhythmdb-song-entry-types.c:170: deleting entry file:///media/gro/musique2/Underground_-_B.O/09%20-%20Unknown%20Artist%20-%20Track%209.mp3; not seen for too long
(12:37:06) [0x1deaed0] [rhythmdb_entry_delete] rhythmdb.c:3707: deleting entry 0x7f15b8a30cf0
**
RhythmDB:ERROR:rhythmdb-tree.c:1517:remove_child: assertion failed: (g_hash_table_remove (parent->children, data))
found device path /dev/sdb1 for mount /media/gro
device /dev/sdb1 has no ID_MEDIA_PLAYER tag in udev
/media/gro is already a mount point
override file /media/gro/.is_audio_player not found on mount /media/gro
found device path /dev/sdb1 for mount /media/gro
device /dev/sdb1 has no ID_MEDIA_PLAYER tag in udev
/media/gro is already a mount point
override file /media/gro/.is_audio_player not found on mount /media/gro
jonath@jonath-MS-7369:~$ ls -la /media/gro/musique2/Underground_-_B.O/
ls: cannot access /media/gro/musique2/Underground_-_B.O/: No such file or directory

using Ubuntu 12.10
uname -a
Linux jonath-MS-7369 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
apt-cache policy rhythmbox
rhythmbox:
  Installed: 2.97-1ubuntu6
  Candidate: 2.97-1ubuntu6
  Version table:
 *** 2.97-1ubuntu6 0
        500 http://cz.archive.ubuntu.com/ubuntu/ quantal-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     2.97-1ubuntu5 0
        500 http://cz.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages

George Gill (ggilliii10)
summary: - Rhythmbox crashes after few seconds
+ Rhythmbox crashes after few seconds when launched from command line
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: Rhythmbox crashes after few seconds when launched from command line

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

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
Revision history for this message
jonaternet (jonaternet) wrote :

Hello, there is some misunderstanding here, I should have written :
This happens anytime I try to launch Rhythmbox.
I always get this error, *and* If I try to launch it from command line : <rest of bug description>

It is *not* only if I try to launch it from command line ! It is anytime I try to launch it.
I also want to add, this could be due to the fact that /media/gro is mounted at startup and is not on the same disk as root :

jonath@jonath-MS-7369:~$ grep gro /etc/fstab
/dev/sdb1 /media/gro ext4 rw,nosuid,nodev,uhelper=udisks2 0 0

So this could be linked with : "/media/gro is already a mount point" but I don't think it causes the bug (?)

Revision history for this message
jonaternet (jonaternet) wrote :

Workaround :
renaming the file ~/.local/share/rhythmbox/rhythmdb.xml and re-scan the music folder works.

jonaternet (jonaternet)
summary: - Rhythmbox crashes after few seconds when launched from command line
+ Rhythmbox crashes after few seconds
description: updated
Revision history for this message
joe57005 (joe57005) wrote :

I had the same problem and was able to fix it by removing the entry for the missing file from rhythmdb.xml

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
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.