Bug 599494 – crash in Rhythmbox:

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 599494 - crash in Rhythmbox:


Summary:	crash in Rhythmbox:


Status:	RESOLVED DUPLICATE of bug 512570

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-10-24 16:31 UTC by heitkamp
Modified:	2009-10-27 04:21 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description heitkamp 2009-10-24 16:31:33 UTC

Version: 0.12.5

What were you doing when the application crashed?



Distribution: Debian  (lenny)
Gnome Release: 2.28.0 2009-10-23 (GNOME.Org)
BugBuddy Version: 2.29.1

System: Linux 2.6.31.5 #3 SMP PREEMPT Thu Oct 22 21:54:37 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10699001
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola
GTK+ Modules: gnomebreakpad, gail, atk-bridge

Memory status: size: 100909056 vsize: 100909056 resident: 22392832 share: 14966784 rss: 22392832 rss_rlim: 18446744073709551615
CPU usage: start_time: 1256401796 rtime: 40 utime: 35 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
0xffffe424 in __kernel_vsyscall ()

+ Trace 218538

Thread 1 (Thread 0xb5f08760 (LWP 17623))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /usr/local/gnome//lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/local/gnome//lib/libglib-2.0.so.0
#4 run_bug_buddy(char const*, int, char const*)
from /usr/local/gnome/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 check_if_gdb()
from /usr/local/gnome/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 bugbuddy_segv_handle(int)
from /usr/local/gnome/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 <signal handler called>
#8 rb_python_module_load_with_gil
from /usr/local/gnome//lib/librhythmbox-core.so.0
#9 g_type_module_use
from /usr/local/gnome//lib/libgobject-2.0.so.0
#10 load_plugin_module
from /usr/local/gnome//lib/librhythmbox-core.so.0
#11 rb_plugins_engine_activate_plugin_real
from /usr/local/gnome//lib/librhythmbox-core.so.0
#12 rb_plugins_engine_activate_plugin
from /usr/local/gnome//lib/librhythmbox-core.so.0
#13 rb_plugins_engine_load_cb
from /usr/local/gnome//lib/librhythmbox-core.so.0
#14 _uri_handle_recurse
from /usr/local/gnome//lib/librhythmbox-core.so.0
#15 _uri_handle_recurse
from /usr/local/gnome//lib/librhythmbox-core.so.0
#16 rb_uri_handle_recursively
from /usr/local/gnome//lib/librhythmbox-core.so.0
#17 rb_plugins_engine_load_dir
from /usr/local/gnome//lib/librhythmbox-core.so.0
#18 rb_plugins_engine_load_all
from /usr/local/gnome//lib/librhythmbox-core.so.0
#19 rb_plugins_engine_init
from /usr/local/gnome//lib/librhythmbox-core.so.0
#20 rb_shell_constructed
from /usr/local/gnome//lib/librhythmbox-core.so.0
#21 g_object_newv
from /usr/local/gnome//lib/libgobject-2.0.so.0
#22 g_object_new_valist
from /usr/local/gnome//lib/libgobject-2.0.so.0
#23 g_object_new
from /usr/local/gnome//lib/libgobject-2.0.so.0
#24 rb_shell_new
from /usr/local/gnome//lib/librhythmbox-core.so.0
#25 main

A debugging session is active.

	Inferior 1 [process 17623] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** rhythmbox **: atk_object_set_name: assertion `name != NULL' failed 
** rhythmbox **: atk_object_set_name: assertion `name != NULL' failed

Comment 1 Akhil Laddha 2009-10-27 04:21:06 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 bug 512570 ***