Bug 414292 – crash in Rhythmbox Music Player: ein großes Verzeichnis m...

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 414292 - crash in Rhythmbox Music Player: ein großes Verzeichnis m...


Summary:	crash in Rhythmbox Music Player: ein großes Verzeichnis m...


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-03-03 16:33 UTC by d.f.krauss
Modified:	2007-03-04 02:38 UTC

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

Description d.f.krauss 2007-03-03 16:33:39 UTC

What were you doing when the application crashed?
ein großes Verzeichnis mit mehreren Hunder .mp3 geladen geladen


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

Memory status: size: 90767360 vsize: 0 resident: 90767360 share: 0 rss: 22114304 rss_rlim: 0
CPU usage: start_time: 1172939216 rtime: 0 utime: 3589 stime: 0 cutime:2685 cstime: 0 timeout: 904 it_real_value: 0 frequency: 14

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228716368 (LWP 17919)]
[New Thread -1262335072 (LWP 17930)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 115508

Thread 1 (Thread -1228716368 (LWP 17919))

#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 gtk_paint_flat_box
from /usr/lib/libgtk-x11-2.0.so.0
#19 _gtk_tree_view_column_autosize
from /usr/lib/libgtk-x11-2.0.so.0
#20 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#21 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#28 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#29 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#30 gtk_container_check_resize
from /usr/lib/libgtk-x11-2.0.so.0
#31 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#34 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#35 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#36 main
#0 __kernel_vsyscall

Comment 1 Alex Lancaster 2007-03-04 02:38:38 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 343443 ***