Bug 540647 – crash in Rhythmbox Music Player: plugged in mp3 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 540647 - crash in Rhythmbox Music Player: plugged in mp3 player


Summary:	crash in Rhythmbox Music Player: plugged in mp3 player


Status:	RESOLVED DUPLICATE of bug 510236

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-28 17:50 UTC by kgfowler
Modified:	2008-07-13 22:04 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description kgfowler 2008-06-28 17:50:24 UTC

Version: 0.11.5

What were you doing when the application crashed?
plugged in mp3 player 


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 110956544 vsize: 110956544 resident: 49803264 share: 18497536 rss: 49803264 rss_rlim: 4294967295
CPU usage: start_time: 1214675033 rtime: 4268 utime: 4110 stime: 158 cutime:2 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb661b740 (LWP 19968)]
[New Thread 0xb6372b90 (LWP 19974)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 201621

Thread 1 (Thread 0xb661b740 (LWP 19968))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 rhythmdb_entry_allocate
at rhythmdb.c line 1210
#7 rhythmdb_entry_new
at rhythmdb.c line 1319
#8 rhythmdb_add_import_error_entry
at rhythmdb.c line 1858
#9 rhythmdb_process_metadata_load_real
at rhythmdb.c line 1898
#10 rhythmdb_process_one_event
at rhythmdb.c line 2072
#11 rb_async_queue_watch_dispatch
at rb-async-queue-watch.c line 61
#12 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#13 ??
from /usr/lib/libglib-2.0.so.0
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
from /usr/lib/libglib-2.0.so.0
#20 ??
from /usr/lib/libglib-2.0.so.0
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
from /lib/i686/cmov/libc.so.6
#27 ??
from /lib/i686/cmov/libpthread.so.0
#28 ??
from /lib/i686/cmov/libpthread.so.0
#29 g_thread_self
from /usr/lib/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
at main.c line 327
#0 __kernel_vsyscall



----------- .xsession-errors (24872 sec old) ---------------------
(update-notifier:4501): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:4501): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:4501): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:4501): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:4501): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:4501): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:4501): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Susana 2008-07-13 22:04:53 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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