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 379183 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
Status: RESOLVED DUPLICATE of bug 358855
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-25 16:20 UTC by ross.margulies
Modified: 2006-11-25 21:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description ross.margulies 2006-11-25 16:20:36 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 57352192 vsize: 0 resident: 57352192 share: 0 rss: 23146496 rss_rlim: 0
CPU usage: start_time: 1164471623 rtime: 0 utime: 90 stime: 0 cutime:84 cstime: 0 timeout: 6 it_real_value: 0 frequency: 2

Backtrace was generated from '/usr/bin/rhythmbox'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228880208 (LWP 9583)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 89301

Thread 1 (Thread -1228880208 (LWP 9583))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 rb_ipod_source_name_changed_cb
    at ../../sources/rb-ipod-source.c line 127
  • #5 g_cclosure_marshal_VOID__PARAM
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_object_class_override_property
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_enum_register_static
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #15 rb_ipod_source_new
    at ../../sources/rb-ipod-source.c line 213
  • #16 create_source_cb
    at rb-ipod-plugin.c line 204
  • #17 rb_marshal_OBJECT__OBJECT
    at rb-marshal.c line 229
  • #18 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #22 rb_removable_media_manager_mount_volume
    at rb-removable-media-manager.c line 457
  • #23 rb_removable_media_manager_scan
    at rb-removable-media-manager.c line 629
  • #24 rb_shell_constructor
    at rb-shell.c line 1381
  • #25 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #28 rb_shell_new
    at rb-shell.c line 968
  • #29 main
    at main.c line 304
  • #0 __kernel_vsyscall 






Comment 1


Jonathan Matthew





          2006-11-25 21:06:52 UTC
        



The crash occurs because the database file on your iPod is damaged and rhythmbox doesn't check for errors properly when reading it.  We get a lot of bug reports about this, but it's hard to fix without a copy of the damaged database file.  Could you please make the iPod_Control/iTunes/iTunesDB file (and the corresponding ArtworkDB if you have artwork on your ipod) available by attaching it to bug 358855?

It would be even more helpful if you could try rebuilding rhythmbox with the patch from bug 358855, which is my initial (untested) attempt at fixing the crash.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 358855 ***