GNOME Bugzilla – Bug 524985
crash in rb_ipod_db_set_ipod_name
Last modified: 2008-08-11 20:10:08 UTC
Version: 0.11.5 What were you doing when the application crashed? Run rhythmbox Distribution: Debian 3.1 (sarge) Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 481062912 vsize: 481062912 resident: 45342720 share: 19804160 rss: 45342720 rss_rlim: 18446744073709551615 CPU usage: start_time: 1206806615 rtime: 97 utime: 84 stime: 13 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b4aed5e1cc0 (LWP 13998)] (no debugging symbols found) 0x0000003a57c0e5ef in waitpid () from /lib/libpthread.so.0
+ Trace 193625
Thread 1 (Thread 0x2b4aed5e1cc0 (LWP 13998))
----------- .xsession-errors --------------------- (rhythmbox:13998): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:13998): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:13998): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:13998): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:13998): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:13998): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:13998): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:13998): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Distribution: Debian 3.1 (sarge) Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 478498816 vsize: 478498816 resident: 45416448 share: 19820544 rss: 45416448 rss_rlim: 18446744073709551615 CPU usage: start_time: 1206912045 rtime: 104 utime: 86 stime: 18 cutime:4 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2b7ac29439e0 (LWP 23948)] 0x0000003a57c0e5ef in waitpid () from /lib/libpthread.so.0
+ Trace 193709
Thread 1 (Thread 0x2b7ac29439e0 (LWP 23948))
----------- .xsession-errors (92901 sec old) --------------------- (npviewer.bin:20412): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: niew\xb3a\xb6ciwa klasa ELF: ELFCLASS64 (npviewer.bin:20412): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: niew\xb3a\xb6ciwa klasa ELF: ELFCLASS64 (npviewer.bin:20412): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: niew\xb3a\xb6ciwa klasa ELF: ELFCLASS64 (npviewer.bin:20412): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: niew\xb3a\xb6ciwa klasa ELF: ELFCLASS64 (npviewer.bin:20412): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: niew\xb3a\xb6ciwa klasa ELF: ELFCLASS64 (npviewer.bin:20412): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: niew\xb3a\xb6ciwa klasa ELF: ELFCLASS64 (npviewer.bin:20412): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: niew\xb3a\xb6ciwa klasa ELF: ELFCLASS64 ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 527332 has been marked as a duplicate of this bug. ***
*** Bug 527417 has been marked as a duplicate of this bug. ***
*** Bug 526995 has been marked as a duplicate of this bug. ***
*** Bug 527661 has been marked as a duplicate of this bug. ***
*** Bug 527678 has been marked as a duplicate of this bug. ***
*** Bug 527963 has been marked as a duplicate of this bug. ***
*** Bug 528997 has been marked as a duplicate of this bug. ***
*** Bug 482571 has been marked as a duplicate of this bug. ***
we connect rb_ipod_source_name_changed_cb to RbIpodSource::notify::name in RbIpodSource::init but the callback uses RbIpodSource::priv::ipod_db which is only created at the end of RbIpodSource::constructor. I guess a notify::name signal is emitted after the signal is connected but befor the constructor runs to its end. We could move the signal connection after the creation of priv::ipod_db or silently return if priv::ipod_db is NULL.
I think it'd make sense to connect the notify::name signal handler in rb_ipod_load_songs after the g_object_set that sets the name.
*** Bug 529404 has been marked as a duplicate of this bug. ***
*** Bug 529366 has been marked as a duplicate of this bug. ***
*** Bug 530155 has been marked as a duplicate of this bug. ***
*** Bug 530625 has been marked as a duplicate of this bug. ***
*** Bug 530548 has been marked as a duplicate of this bug. ***
*** Bug 530547 has been marked as a duplicate of this bug. ***
*** Bug 532015 has been marked as a duplicate of this bug. ***
*** Bug 532191 has been marked as a duplicate of this bug. ***
*** Bug 532192 has been marked as a duplicate of this bug. ***
*** Bug 533574 has been marked as a duplicate of this bug. ***
Created attachment 111052 [details] [review] Proposed patch
looks fine to me.
*** Bug 532903 has been marked as a duplicate of this bug. ***
*** Bug 533021 has been marked as a duplicate of this bug. ***
*** Bug 533235 has been marked as a duplicate of this bug. ***
*** Bug 533294 has been marked as a duplicate of this bug. ***
*** Bug 533572 has been marked as a duplicate of this bug. ***
Confirming as per dupes and patch status. As a bonus note, some reports mentioned that if you initialized the db somewhere else, the crash didn't happen.
*** Bug 534030 has been marked as a duplicate of this bug. ***
ok, I committed the patch in rev 5705: 2008-05-20 Christophe Fergeaui <teuf@gnome.org> * plugins/ipod/rb-ipod-source.c: don't connect to notify::name too soon during RbIpodSource instanciation since RbIpodSource::priv::ipod_db must be set before the notify::name callback can be safely used, this fixes bug #524985. In impl_delete_thyself, don't try to use priv->ipod_db if it's NULL (which can happen with empty ipods)
*** Bug 534102 has been marked as a duplicate of this bug. ***
*** Bug 535028 has been marked as a duplicate of this bug. ***
*** Bug 534816 has been marked as a duplicate of this bug. ***
*** Bug 535317 has been marked as a duplicate of this bug. ***
*** Bug 535316 has been marked as a duplicate of this bug. ***
*** Bug 536333 has been marked as a duplicate of this bug. ***
*** Bug 536850 has been marked as a duplicate of this bug. ***
*** Bug 536945 has been marked as a duplicate of this bug. ***
*** Bug 517143 has been marked as a duplicate of this bug. ***
*** Bug 537881 has been marked as a duplicate of this bug. ***
*** Bug 538292 has been marked as a duplicate of this bug. ***
*** Bug 538092 has been marked as a duplicate of this bug. ***
*** Bug 537630 has been marked as a duplicate of this bug. ***
*** Bug 537620 has been marked as a duplicate of this bug. ***
*** Bug 538121 has been marked as a duplicate of this bug. ***
*** Bug 538291 has been marked as a duplicate of this bug. ***
*** Bug 538985 has been marked as a duplicate of this bug. ***
*** Bug 539215 has been marked as a duplicate of this bug. ***
*** Bug 539217 has been marked as a duplicate of this bug. ***
*** Bug 539611 has been marked as a duplicate of this bug. ***
*** Bug 540052 has been marked as a duplicate of this bug. ***
*** Bug 542406 has been marked as a duplicate of this bug. ***
*** Bug 542449 has been marked as a duplicate of this bug. ***
*** Bug 542457 has been marked as a duplicate of this bug. ***
*** Bug 542584 has been marked as a duplicate of this bug. ***
*** Bug 542620 has been marked as a duplicate of this bug. ***
*** Bug 542732 has been marked as a duplicate of this bug. ***
*** Bug 542901 has been marked as a duplicate of this bug. ***
*** Bug 543050 has been marked as a duplicate of this bug. ***
*** Bug 542238 has been marked as a duplicate of this bug. ***
*** Bug 541925 has been marked as a duplicate of this bug. ***
*** Bug 542807 has been marked as a duplicate of this bug. ***
*** Bug 543980 has been marked as a duplicate of this bug. ***
*** Bug 544163 has been marked as a duplicate of this bug. ***
*** Bug 544641 has been marked as a duplicate of this bug. ***
*** Bug 545577 has been marked as a duplicate of this bug. ***
*** Bug 547235 has been marked as a duplicate of this bug. ***