Bug 407855 – crash in Rhythmbox Music Player: J'étais dans "applicatio...

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 407855 - crash in Rhythmbox Music Player: J'étais dans "applicatio...


Summary:	crash in Rhythmbox Music Player: J'étais dans "applicatio...


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:	2007-02-14 13:38 UTC by nevelo
Modified:	2007-02-14 13:54 UTC

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

Description nevelo 2007-02-14 13:38:49 UTC

What were you doing when the application crashed?
J'étais dans "application" pour voir comment s'écrivait Rhythmbox !


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

Memory status: size: 198377472 vsize: 198377472 resident: 26509312 share: 15843328 rss: 26509312 rss_rlim: -1
CPU usage: start_time: 1171460211 rtime: 278 utime: 252 stime: 26 cutime:6 cstime: 1 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47848142738400 (LWP 13396)]
[New Thread 1098918224 (LWP 13409)]
(no debugging symbols found)
0x00002b847eb00eef in waitpid () from /lib/libpthread.so.0

+ Trace 110670

Thread 1 (Thread 47848142738400 (LWP 13396))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_instance_get_private
from /usr/lib64/libgobject-2.0.so.0
#4 _gdk_gc_init
from /usr/lib64/libgdk-x11-2.0.so.0
#5 g_type_create_instance
from /usr/lib64/libgobject-2.0.so.0
#6 g_object_set
from /usr/lib64/libgobject-2.0.so.0
#7 g_object_newv
from /usr/lib64/libgobject-2.0.so.0
#8 g_object_new_valist
from /usr/lib64/libgobject-2.0.so.0
#9 g_object_new
from /usr/lib64/libgobject-2.0.so.0
#10 _gdk_x11_gc_new
from /usr/lib64/libgdk-x11-2.0.so.0
#11 gtk_style_attach
from /usr/lib64/libgtk-x11-2.0.so.0
#12 gtk_style_attach
from /usr/lib64/libgtk-x11-2.0.so.0
#13 gtk_cell_renderer_toggle_get_inconsistent
from /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so
#14 _gtk_tree_view_column_autosize
from /usr/lib64/libgtk-x11-2.0.so.0
#15 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib64/libgtk-x11-2.0.so.0
#16 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#20 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#21 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#22 gdk_window_is_viewable
from /usr/lib64/libgdk-x11-2.0.so.0
#23 gdk_window_process_all_updates
from /usr/lib64/libgdk-x11-2.0.so.0
#24 gtk_container_check_resize
from /usr/lib64/libgtk-x11-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#26 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#28 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#29 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Alex Lancaster 2007-02-14 13:54:41 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 ***