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 365098 - crash in Rhythmbox Music Player: starting Rhythmbox
crash in Rhythmbox Music Player: starting Rhythmbox
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-10-25 20:00 UTC by Baptiste Mille-Mathias
Modified: 2006-11-25 20:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Baptiste Mille-Mathias 2006-10-25 20:00:57 UTC
What were you doing when the application crashed?
starting Rhythmbox



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

Memory status: size: 68284416 vsize: 0 resident: 68284416 share: 0 rss: 23621632 rss_rlim: 0
CPU usage: start_time: 1161806421 rtime: 0 utime: 165 stime: 0 cutime:143 cstime: 0 timeout: 22 it_real_value: 0 frequency: 9

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 -1209075520 (LWP 21709)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1209075520 (LWP 21709))

  • #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 IA__g_cclosure_marshal_VOID__PARAM
    at gmarshal.c line 531
  • #6 IA__g_closure_invoke
    at gclosure.c line 490
  • #7 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #8 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #9 IA__g_signal_emit
    at gsignal.c line 2243
  • #10 g_object_dispatch_properties_changed
    at gobject.c line 563
  • #11 g_object_notify_dispatcher
    at gobject.c line 245
  • #12 IA__g_object_newv
    at gobjectnotifyqueue.c line 123
  • #13 IA__g_object_new_valist
    at gobject.c line 1022
  • #14 IA__g_object_new
    at gobject.c line 795
  • #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 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #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 IA__g_object_newv
    at gobject.c line 937
  • #26 IA__g_object_new_valist
    at gobject.c line 1022
  • #27 IA__g_object_new
    at gobject.c line 795
  • #28 rb_shell_new
    at rb-shell.c line 968
  • #29 main
    at main.c line 304
  • #0 __kernel_vsyscall

Comment 1 Baptiste Mille-Mathias 2006-10-25 20:02:22 UTC
as You seen my iPod was plugged when I started
Comment 2 Alex Lancaster 2006-10-26 00:45:42 UTC
This is possibly a variant of bug #352972.  The solution there is to upgrade to libgpod 0.4.  Please close as a dupe if it turns out that upgrading to libgpod fixes it.
Comment 3 Jonathan Matthew 2006-11-21 23:20:46 UTC
Actually, this looks a lot like bug 358855.  Can you try the patch on that bug?
Comment 4 Jonathan Matthew 2006-11-25 20:55:46 UTC
Bug 379183 is clearly a duplicate of 358855 (it arrived after a string of 3 duplicates from the same submitter, but this time with debug info) and has an identical stack trace.

If you do manage to test the patch on bug 358855, please report results there.

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