GNOME Bugzilla – Bug 678032
The interface freezes at launch
Last modified: 2012-11-04 10:02:11 UTC
Hello, With the latest version of RB on Ubuntu Quantal 12.10 (2.97-0ubuntu2), the interface freezes at launch. I didn't have this bug with the previous version (2.97-0ubuntu1) but it's a bit strange because it seems the change between the two versions only concerns 'audiocd' plugin (and I have this bug with or without this plugin) The difference between the two versions: https://launchpadlibrarian.net/107058413/rhythmbox_2.97-0ubuntu1_2.97-0ubuntu2.diff.gz If I launch it with this command, I don't have any problem: $ rhythmbox --rhythmdb-file=test.db Maybe my (huge) database is corrupted but if I launch RB with the debug mode (-d), I don't have this bug (but it takes a few time before being ready to use, approximatively 2 minutes). I've also removed my 'rhythmdb.xml' file (26MB) and re-added all my music library: everything worked fine until I restart RB and now I still have the bug. Note that when I launch RB with the debug option, I can see this line a lot of time: [0x1470aa0] [rhythmdb_property_model_insert] rhythmdb-property-model.c:798: adding "(...)": refcount X And then I can see this line (it seems I see it for each song of my library): [0x1470aa0] [rhythmdb_process_one_event] rhythmdb.c:2497: Database is read-only, delaying event processing Thank you for developing RB!
3 new comments have been added to the Launchpad bug report: 1: nachokb (nachokb) wrote on 2012-10-25: -------------------------- it also happens with these two versions on Ubuntu Quantal (dist upgraded from Precise): * 2.98-0.1~webupd8~quantal2 from ppa:webupd8team/rhythmbox * Precise's 2.96-0ubuntu4.1 installed manually (gotten these debs from packages.ubuntu.com: rhythmbox_2.96-0ubuntu4.1_amd64 librhythmbox-core5_2.96-0ubuntu4.1_amd64 rhythmbox-data_2.96-0ubuntu4.1_all gir1.2-rb-3.0_2.96-0ubuntu4.1_amd64) 2.96 worked wonderfully on Precise before upgrading... perhaps the XML got corrupted somehow during the upgrade? (though it doesn't look like it was modified) I've got a ~100gb collection. Also, if I start it with rhythmbox --rhythmdb-file=~/test.db it works, until it scanned enough of my ~/Music to start hanging again... My conclusion: * it's definitely related to having a large collection * it didn't happen on Precise * it happens on Quantal with Precise's Rhythmbox so I guess the problem lies in some other dependency (say, libxml or something)... any ideas? 2: Matthieu Baerts (matttbe) wrote on 2012-10-25: -------------------------- Yes, I confirm that the problem is due to a large collection. But I don't know if it's due to libxml2 because I had this problem with the version 2.97-0ubuntu2 of RB and not with the previous one (2.97-0ubuntu1). They were compiled with the same version of libxml2 and I tested both versions of RB with the same version of libxml2. Build logs: - https://launchpadlibrarian.net/106847253/buildlog_ubuntu-quantal-amd64.rhythmbox_2.97-0ubuntu1_BUILDING.txt.gz - https://launchpadlibrarian.net/107103149/buildlog_ubuntu-quantal-amd64.rhythmbox_2.97-0ubuntu2_BUILDING.txt.gz 3: wasutton3 (will-sutton-family) wrote 3 hours ago: -------------------------- I have had a similar bug on ArchLinux. I did try removing the contents of /.local/share/rhythmbox (the same folder on ubuntu). And then reloading. It works once, but if i close rhythmbox and reopen, it fails.
Can you get a stack trace showing where it gets stuck? See http://live.gnome.org/GettingTraces for some information on how to do this - in short, run rhythmbox under gdb, and when it gets stuck, hit ctrl-c and then 'thread apply all bt'. If it doesn't get stuck when run in gdb (it sounds like there's a race condition somewhere, so this is possible), you can attach gdb once it's already stuck by running 'gdb rhythmbox `pidof rhythmbox`'.
Created attachment 227970 [details] A full backtrace of this crash Thank you for this answer! I just added a full backtrace of this crash. I hope it will be helpful ;)
fixed in commit a2ead52
I confirm that this commit fixes this bug! Thank you for your help :) I'll check to know if it's possible to backport this change to Ubuntu 12.10!