Bug 447960 – 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 447960 - crash in Rhythmbox Music Player:


Summary:	crash in Rhythmbox Music Player:


Status:	RESOLVED DUPLICATE of bug 409540

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.10.0
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-15 17:57 UTC by ychikui@net.ie.niigata-u.ac.jp
Modified:	2007-06-15 22:20 UTC

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

Description ychikui@net.ie.niigata-u.ac.jp 2007-06-15 17:57:42 UTC

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: panther-gtk2
Icon Theme: ychikui_orig

Memory status: size: 641597440 vsize: 641597440 resident: 65331200 share: 39194624 rss: 65331200 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181929990 rtime: 514 utime: 483 stime: 31 cutime:7 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912512094320 (LWP 10065)]
[New Thread 1105209680 (LWP 10084)]
(no debugging symbols found)
0x000000332560d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 141261

Thread 1 (Thread 46912512094320 (LWP 10065))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /lib64/libglib-2.0.so.0
#6 g_log
from /lib64/libglib-2.0.so.0
#7 g_assert_warning
from /lib64/libglib-2.0.so.0
#8 rb_shell_preferences_new
#9 ??
#10 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#11 ??
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit
from /lib64/libgobject-2.0.so.0
#14 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#16 ??
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /lib64/libgobject-2.0.so.0
#19 gtk_widget_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#20 gtk_menu_shell_activate_item
from /usr/lib64/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#23 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#24 ??
from /lib64/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#26 g_signal_emit
from /lib64/libgobject-2.0.so.0
#27 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#28 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#31 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#32 ??
from /lib64/libglib-2.0.so.0
#33 g_main_loop_run
from /lib64/libglib-2.0.so.0
#34 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#35 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Jonathan Matthew 2007-06-15 22:20:07 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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