Bug 460392 – crash in Rhythmbox Music Player:

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 460392 - crash in Rhythmbox Music Player:


Summary:	crash in Rhythmbox Music Player:


Status:	RESOLVED DUPLICATE of bug 460051

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.10.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-25 21:59 UTC by jiij
Modified:	2007-07-29 01:46 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description jiij 2007-07-25 21:59:28 UTC

Version: 0.10.1

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: OSX

Memory status: size: 70389760 vsize: 70389760 resident: 30887936 share: 15958016 rss: 30887936 rss_rlim: 4294967295
CPU usage: start_time: 1185400895 rtime: 104 utime: 94 stime: 10 cutime:3 cstime: 0 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228794176 (LWP 10969)]
(no debugging symbols found)
0xb7f7a7f2 in ?? () from /lib/ld-linux.so.2

+ Trace 150560

Thread 1 (Thread -1228794176 (LWP 10969))

#0 ??
from /lib/ld-linux.so.2
#1 __waitpid_nocancel
from /lib/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
from /usr/lib/librhythmbox-core.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_override_class_closure
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_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#21 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#22 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#23 main
#0 ??
from /lib/ld-linux.so.2



----------- .xsession-errors ---------------------
(nautilus:3104): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: Element 'markup' was closed, but the currently open element is 'b'
(nautilus:3104): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: Element 'markup' was closed, but the currently open element is 'b'
gnome-mount 0.6
** Message: drive = 88762d0
** Message: volume = 0
** Message: drive = 890c230
** Message: volume = 0
** (update-notifier:3107): WARNING **: no cdrom: disk
** Message: drive = 890c230
** Message: volume = 88762d0
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-29 01:46:43 UTC

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 460051 ***