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 384716 - crash in Rhythmbox Music Player: Rhythmbox had been runni...
crash in Rhythmbox Music Player: Rhythmbox had been runni...
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-12-11 14:12 UTC by Carl-Erik Kopseng
Modified: 2006-12-12 15:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Carl-Erik Kopseng 2006-12-11 14:12:59 UTC 
What were you doing when the application crashed?
Rhythmbox had been running over ssh for a period of time (15 min-30min) from server to my laptop on a LAN. Then it suddenly stops. I start it over again, but all I get is this bug-buddy message.		


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

Memory status: size: 78643200 vsize: 0 resident: 78643200 share: 0 rss: 25583616 rss_rlim: 0
CPU usage: start_time: 1165846037 rtime: 0 utime: 169 stime: 0 cutime:154 cstime: 0 timeout: 15 it_real_value: 0 frequency: 9

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

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

+ Trace 93283

Thread 1 (Thread -1229011280 (LWP 9240))

  • #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_register_type
    from /usr/lib/rhythmbox/plugins/ipod/libipod.so
  • #5 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #8 rb_ipod_source_new
    from /usr/lib/rhythmbox/plugins/ipod/libipod.so
  • #9 register_rb_plugin
    from /usr/lib/rhythmbox/plugins/ipod/libipod.so
  • #10 rb_marshal_OBJECT__OBJECT
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 rb_removable_media_manager_queue_transfer
  • #16 rb_removable_media_manager_scan
  • #17 rb_shell_new
  • #18 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #21 rb_shell_new
  • #22 main
  • #0 __kernel_vsyscall 






Comment 1


Alex Lancaster





          2006-12-11 14:36:57 UTC
        



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. Thanks in advance!

This could be a duplicate of bug #358855 or bug #352972 but the stack traces don't match that well.






Comment 2


Carl-Erik Kopseng





          2006-12-12 15:47:38 UTC
        



> This could be a duplicate of bug #358855 or bug #352972 but the stack traces
> don't match that well.
It probably is just that bug. I sent in a trace with debug symbols later on. Seems as if it is a problem with irregular iTunesDB's made with Banshee/libipod-sharp.






Comment 3


Alex Lancaster





          2006-12-12 15:57:14 UTC
        



(In reply to comment #2)
> > This could be a duplicate of bug #358855 or bug #352972 but the stack traces
> > don't match that well.
> It probably is just that bug. I sent in a trace with debug symbols later on.
> Seems as if it is a problem with irregular iTunesDB's made with
> Banshee/libipod-sharp.

In that case, you should attach the stacktrace to the existing bug, not open a new one.  Or open a new one and close this one as a duplicate.  

Since this one is really a duplicate of bug #384717 and that bug is in, in turn, a duplicate of bug #358855.  I will close this bug as a duplicate of bug #358855.


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