Bug 365243 – crash in Rhythmbox Music Player: Nothing. It was just sit...

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 365243 - crash in Rhythmbox Music Player: Nothing. It was just sit...


Summary:	crash in Rhythmbox Music Player: Nothing. It was just sit...


Status:	RESOLVED DUPLICATE of bug 324487

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.9.5
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-26 11:15 UTC by Tomasz Sterna
Modified:	2006-10-26 13:50 UTC

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

Description Tomasz Sterna 2006-10-26 11:15:13 UTC

What were you doing when the application crashed?
Nothing. It was just sitting in background.


Distribution: Gentoo Base System version 1.12.5
Gnome Release: 2.16.1 2006-10-10 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 91496448 vsize: 0 resident: 91496448 share: 0 rss: 26533888 rss_rlim: 0
CPU usage: start_time: 1161860030 rtime: 0 utime: 265 stime: 0 cutime:245 cstime: 0 timeout: 20 it_real_value: 0 frequency: 2

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209005872 (LWP 3937)]
[New Thread -1244591216 (LWP 3949)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 78409

Thread 1 (Thread -1209005872 (LWP 3937))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 870
#3 <signal handler called>
#4 soup_connection_disconnect
at soup-connection.c line 699
#5 socket_disconnected
at soup-connection.c line 433
#6 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#7 IA__g_closure_invoke
at gclosure.c line 490
#8 signal_emit_unlocked_R
at gsignal.c line 2440
#9 IA__g_signal_emit_valist
at gsignal.c line 2199
#10 IA__g_signal_emit
at gsignal.c line 2243
#11 soup_socket_disconnect
at soup-socket.c line 974
#12 socket_read_watch
at soup-socket.c line 1068
#13 g_io_unix_dispatch
at giounix.c line 162
#14 IA__g_main_context_dispatch
at gmain.c line 2045
#15 g_main_context_iterate
at gmain.c line 2677
#16 IA__g_main_context_iteration
at gmain.c line 2736
#17 IA__gtk_main_iteration
at gtkmain.c line 1084
#18 rb_daap_source_disconnect
at rb-daap-source.c line 1023
#19 remove_source
at rb-daap-source.c line 410
#20 g_hash_node_destroy
at ghash.c line 768
#21 IA__g_hash_table_remove
at ghash.c line 433
#22 mdns_service_removed
at rb-daap-source.c line 403
#23 IA__g_cclosure_marshal_VOID__STRING
at gmarshal.c line 496
#24 IA__g_closure_invoke
at gclosure.c line 490
#25 signal_emit_unlocked_R
at gsignal.c line 2440
#26 IA__g_signal_emit_valist
at gsignal.c line 2199
#27 IA__g_signal_emit
at gsignal.c line 2243
#28 browse_cb
at rb-daap-mdns-browser-avahi.c line 253
#29 avahi_service_browser_event
at browser.c line 777
#30 filter_func
at client.c line 253
#31 dbus_connection_dispatch
at dbus-connection.c line 3646
#32 dispatch_timeout_callback
at ../avahi-common/dbus-watch-glue.c line 103
#33 dispatch_func
at glib-watch.c line 254
#34 IA__g_main_context_dispatch
at gmain.c line 2045
#35 g_main_context_iterate
at gmain.c line 2677
#36 IA__g_main_loop_run
at gmain.c line 2881
#37 IA__gtk_main
at gtkmain.c line 1001
#38 main
at main.c line 372
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-26 13:50:26 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 324487 ***