Bug 555918 – crash in Rhythmbox Music Player:

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 555918 - crash in Rhythmbox Music Player:


Summary:	crash in Rhythmbox Music Player:


Status:	RESOLVED DUPLICATE of bug 420467

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-10-11 15:42 UTC by Phil Bordelon
Modified:	2008-10-21 10:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description Phil Bordelon 2008-10-11 15:42:04 UTC

Version: 0.11.2

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.22.3 2008-08-11 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-gentoo-r8 #1 SMP Wed May 14 22:35:07 CDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: gnome

Memory status: size: 309944320 vsize: 309944320 resident: 127827968 share: 20271104 rss: 127827968 rss_rlim: 4294967295
CPU usage: start_time: 1223737831 rtime: 9873 utime: 9032 stime: 841 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 0xb66966d0 (LWP 15928)]
[New Thread 0xa76f2b90 (LWP 16420)]
[New Thread 0xa7ef3b90 (LWP 16419)]
[New Thread 0xa86f4b90 (LWP 16418)]
[New Thread 0xa8ef5b90 (LWP 16417)]
[New Thread 0xa96f6b90 (LWP 16416)]
[New Thread 0xaf0fcb90 (LWP 16415)]
[New Thread 0xb0553b90 (LWP 16414)]
[New Thread 0xabefbb90 (LWP 16413)]
[New Thread 0xaa6f8b90 (LWP 16412)]
[New Thread 0xac6fcb90 (LWP 16411)]
[New Thread 0xab6fab90 (LWP 16410)]
[New Thread 0xa9ef7b90 (LWP 16370)]
[New Thread 0xaaef9b90 (LWP 16369)]
[New Thread 0xacefdb90 (LWP 16368)]
[New Thread 0xad6feb90 (LWP 15953)]
[New Thread 0xadeffb90 (LWP 15952)]
[New Thread 0xb4a57b90 (LWP 15951)]
[New Thread 0xaf8fdb90 (LWP 15940)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 208049

Thread 1 (Thread 0xb66966d0 (LWP 15928))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at gspawn.c line 682
#4 run_bug_buddy
at gnome-breakpad.cc line 213
#5 check_if_gdb
at gnome-breakpad.cc line 283
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 226
#7 google_breakpad::ExceptionHandler::HandleException
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 197
#8 <signal handler called>
#9 gnome_vfs_uri_unref
at gnome-vfs-uri.c line 1026
#10 _gnome_vfs_job_destroy_notify_result
at gnome-vfs-job.c line 335
#11 dispatch_job_callback
at gnome-vfs-job.c line 535
#12 g_idle_dispatch
at gmain.c line 4090
#13 IA__g_main_context_dispatch
at gmain.c line 2012
#14 g_main_context_iterate
at gmain.c line 2645
#15 IA__g_main_loop_run
at gmain.c line 2853
#16 IA__gtk_main
at gtkmain.c line 1163
#17 main
at main.c line 306
#0 __kernel_vsyscall

Comment 1 Jonathan Matthew 2008-10-21 10:06:42 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 420467 ***