Bug 459375 – crash in Rhythmbox Music Player: closing it.

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 459375 - crash in Rhythmbox Music Player: closing it.


Summary:	crash in Rhythmbox Music Player: closing it.


Status:	RESOLVED DUPLICATE of bug 434003

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-23 00:51 UTC by ralphewj-nospam
Modified:	2007-07-24 12:17 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description ralphewj-nospam 2007-07-23 00:51:43 UTC

What were you doing when the application crashed?
closing it.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 106459136 vsize: 106459136 resident: 33300480 share: 21618688 rss: 33300480 rss_rlim: 4294967295
CPU usage: start_time: 1185151801 rtime: 251 utime: 218 stime: 33 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 -1209005520 (LWP 3215)]
[New Thread -1254356080 (LWP 3315)]
[New Thread -1218782320 (LWP 3223)]
[New Thread -1243526256 (LWP 3220)]
[New Thread -1232225392 (LWP 3219)]
(no debugging symbols found)
0x00989402 in __kernel_vsyscall ()

+ Trace 149833

Thread 2 (Thread -1254356080 (LWP 3315))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 ??
from /lib/libgthread-2.0.so.0
#10 ??
from /usr/lib/libgnomevfs-2.so.0
#11 ??
#12 ??
from /usr/lib/libgnomevfs-2.so.0
#13 ??
#14 ??
from /usr/lib/libgnomevfs-2.so.0
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
from /lib/libglib-2.0.so.0
#21 ??
#22 ??
from /lib/libglib-2.0.so.0



----------- .xsession-errors ---------------------
(rhythmbox:3215): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
scsi_read error: sector=128 length=12 retry=1
                 Sense key: 0 ASC: 0 ASCQ: 3
                 Transport error: Unspecified error
                 System error: Input/output error
Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second.
scsi_read error: sector=128 length=6 retry=2
                 Sense key: 0 ASC: 0 ASCQ: 3
                 Transport error: Unspecified error
                 System error: Input/output error
Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second.
Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second.
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-24 12:17:09 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 434003 ***