Bug 469734 – crash in Rhythmbox Music Player: Closing Rhythmbox

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


Summary:	crash in Rhythmbox Music Player: Closing Rhythmbox


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-08-23 22:00 UTC by chris_platt
Modified:	2007-08-26 22:01 UTC

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

Description chris_platt 2007-08-23 22:00:41 UTC

What were you doing when the application crashed?
Closing Rhythmbox


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.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 472195072 vsize: 472195072 resident: 43536384 share: 24186880 rss: 43536384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187906082 rtime: 478 utime: 376 stime: 102 cutime:4 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912517718288 (LWP 3553)]
[New Thread 1210108240 (LWP 3983)]
[New Thread 1136679248 (LWP 3707)]
[New Thread 1094719824 (LWP 3558)]
(no debugging symbols found)
0x000000382d60c808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 157477

Thread 2 (Thread 1210108240 (LWP 3983))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /lib64/libglib-2.0.so.0
#6 g_log
from /lib64/libglib-2.0.so.0
#7 ??
from /lib64/libgthread-2.0.so.0
#8 ??
from /usr/lib64/libgnomevfs-2.so.0
#9 ??
from /usr/lib64/libgnomevfs-2.so.0
#10 ??
from /lib64/libglib-2.0.so.0
#11 ??
from /lib64/libglib-2.0.so.0
#12 start_thread
from /lib64/libpthread.so.0
#13 clone
from /lib64/libc.so.6



----------- .xsession-errors ---------------------
Unmatched element: package
Unmatched element: package
Unmatched element: package
Unmatched element: package
Unmatched element: package
Unmatched element: package
Unmatched element: package
Unmatched element: package
(rhythmbox:3553): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3553): 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 tama 2007-08-26 19:05:53 UTC

Looks like a duplicate of bug 434003.

Same errors in .xsession and similar stacks.
It's running in x86_64 too, should that matter.

Comment 2 Jonathan Matthew 2007-08-26 22:01:55 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 ***