Bug 397960 – crash in Rhythmbox Music Player: Clicked on Properties af...

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 397960 - crash in Rhythmbox Music Player: Clicked on Properties af...


Summary:	crash in Rhythmbox Music Player: Clicked on Properties af...


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-01-18 11:22 UTC by dermann
Modified:	2007-01-18 21:39 UTC

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

Description dermann 2007-01-18 11:22:04 UTC

What were you doing when the application crashed?
Clicked on Properties after failing to open mp3 files. I was searching for a way to install the gstreamer plugin although in package manager it says it is already installed...


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

Memory status: size: 228003840 vsize: 228003840 resident: 35774464 share: 18268160 rss: 35774464 rss_rlim: -1
CPU usage: start_time: 1169118883 rtime: 709 utime: 662 stime: 47 cutime:4 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 47012271997920 (LWP 5689)]
[New Thread 1090525520 (LWP 5698)]
(no debugging symbols found)
0x00002ac1e0e8beef in waitpid () from /lib/libpthread.so.0

+ Trace 103213

Thread 1 (Thread 47012271997920 (LWP 5689))

#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 Jonathan Matthew 2007-01-18 21:39:40 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 356485 ***