Bug 426092 – crash in Rhythmbox Music Player: looking at import error ...

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 426092 - crash in Rhythmbox Music Player: looking at import error ...


Summary:	crash in Rhythmbox Music Player: looking at import error ...


Status:	RESOLVED DUPLICATE of bug 356485

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-04-04 01:31 UTC by interface
Modified:	2007-04-06 07:13 UTC

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

Description interface 2007-04-04 01:31:28 UTC

What were you doing when the application crashed?
looking at import error log, clicked music / properties and crashed


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

Memory status: size: 204271616 vsize: 204271616 resident: 27262976 share: 15339520 rss: 27262976 rss_rlim: -1
CPU usage: start_time: 1175650067 rtime: 352 utime: 322 stime: 30 cutime:1 cstime: 0 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 46954625922016 (LWP 6875)]
[New Thread 1090525520 (LWP 6884)]
(no debugging symbols found)
0x00002ab474ef6eef in waitpid () from /lib/libpthread.so.0

+ Trace 124815

Thread 1 (Thread 46954625922016 (LWP 6875))

#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 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib64/libglib-2.0.so.0
#6 g_log
from /usr/lib64/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib64/libglib-2.0.so.0
#8 rb_source_set_pixbuf
#9 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#13 _gtk_action_emit_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#14 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#18 gtk_widget_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#19 gtk_menu_shell_activate_item
from /usr/lib64/libgtk-x11-2.0.so.0
#20 gtk_menu_shell_append
from /usr/lib64/libgtk-x11-2.0.so.0
#21 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib64/libgtk-x11-2.0.so.0
#22 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#23 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#26 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#27 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#28 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#29 _gdk_events_init
from /usr/lib64/libgdk-x11-2.0.so.0
#30 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#31 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#32 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#33 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#34 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 James "Doc" Livingston 2007-04-06 07:13:49 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 356485 ***