Bug 461868 – crash in Rhythmbox Music Player: exiting

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


Summary:	crash in Rhythmbox Music Player: exiting


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-30 16:51 UTC by crodriguez
Modified:	2007-08-02 10:39 UTC

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

Description crodriguez 2007-07-30 16:51:32 UTC

What were you doing when the application crashed?
exiting


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 95825920 vsize: 95825920 resident: 27295744 share: 15949824 rss: 27295744 rss_rlim: 4294967295
CPU usage: start_time: 1185727857 rtime: 239 utime: 218 stime: 21 cutime:2 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 -1208985040 (LWP 28339)]
[New Thread -1220396144 (LWP 28354)]
[New Thread -1255777392 (LWP 28353)]
[New Thread -1233417328 (LWP 28348)]
[New Thread -1244718192 (LWP 28346)]
(no debugging symbols found)
0x00fe7402 in __kernel_vsyscall ()

+ Trace 151644

Thread 2 (Thread -1220396144 (LWP 28354))

#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 (7 sec old) ---------------------
Loading "installonlyn" plugin
Loading "installonlyn" plugin
Loading "installonlyn" plugin
Loading "installonlyn" plugin
Loading "installonlyn" plugin
Loading "installonlyn" plugin
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 1ac70ce6
CalDAV Eplugin starting up ...
(evolution:28281): e-data-server-DEBUG: Loaded default categories
(evolution:28281): e-data-server-DEBUG: Saving categories to "/root/.evolution/categories.xml"
(rhythmbox:28339): 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...
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-08-02 10:39:58 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 ***