Bug 373440 – crash in Rhythmbox Music Player: I had just clicked the P...

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 373440 - crash in Rhythmbox Music Player: I had just clicked the P...


Summary:	crash in Rhythmbox Music Player: I had just clicked the P...


Status:	RESOLVED DUPLICATE of bug 343443

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-10 16:10 UTC by joshfaulkner
Modified:	2006-11-10 20:58 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description joshfaulkner 2006-11-10 16:10:35 UTC

What were you doing when the application crashed?
I had just clicked the Play button.


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

Memory status: size: 86724608 vsize: 0 resident: 86724608 share: 0 rss: 23207936 rss_rlim: 0
CPU usage: start_time: 1163174960 rtime: 0 utime: 420 stime: 0 cutime:388 cstime: 0 timeout: 32 it_real_value: 0 frequency: 5

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 -1229138256 (LWP 8775)]
[New Thread -1270883424 (LWP 8786)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 85091

Thread 1 (Thread -1229138256 (LWP 8775))

#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 g_type_instance_get_private
from /usr/lib/libgobject-2.0.so.0
#5 _gdk_gc_init
from /usr/lib/libgdk-x11-2.0.so.0
#6 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#7 g_object_set
from /usr/lib/libgobject-2.0.so.0
#8 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#9 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_object_new
from /usr/lib/libgobject-2.0.so.0
#11 _gdk_x11_gc_new
from /usr/lib/libgdk-x11-2.0.so.0
#12 gdk_gc_new_with_values
from /usr/lib/libgdk-x11-2.0.so.0
#13 gdk_window_clear
from /usr/lib/libgdk-x11-2.0.so.0
#14 gdk_gc_new_with_values
from /usr/lib/libgdk-x11-2.0.so.0
#15 gdk_gc_new
from /usr/lib/libgdk-x11-2.0.so.0
#16 gtk_style_attach
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_style_attach
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so
#19 ??
#20 ??
#21 ??
#0 __kernel_vsyscall

Comment 1 Alex Lancaster 2006-11-10 20:58:33 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 343443 ***