Bug 488488 – crash in Rhythmbox Music Player: Exiting (clicked the 'x'...

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 488488 - crash in Rhythmbox Music Player: Exiting (clicked the 'x'...


Summary:	crash in Rhythmbox Music Player: Exiting (clicked the 'x'...


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-10-20 03:28 UTC by al
Modified:	2007-10-20 03:31 UTC

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

Description al 2007-10-20 03:28:23 UTC

What were you doing when the application crashed?
Exiting (clicked the 'x' in the top right)


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.20-2925.9.fc7xen #1 SMP Tue May 22 09:29:36 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 522723328 vsize: 522723328 resident: 36032512 share: 18259968 rss: 36032512 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192850768 rtime: 97 utime: 79 stime: 18 cutime:0 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912709351616 (LWP 3488)]
[New Thread 1105209680 (LWP 3503)]
[New Thread 1094719824 (LWP 3495)]
[New Thread 1084229968 (LWP 3494)]
(no debugging symbols found)
0x00002aaab188a728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 171597

Thread 2 (Thread 1105209680 (LWP 3503))

#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 ---------------------
Traceback (most recent call last):
  File "/usr/lib64/rhythmbox/plugins/magnatune/MagnatuneSource.py", line 312, in __download_update_cb
    out.write(catalog.read("opt/magnatune/info/song_info.xml"))
  File "/usr/lib64/python2.5/zipfile.py", line 471, in read
    zinfo = self.getinfo(name)
  File "/usr/lib64/python2.5/zipfile.py", line 462, in getinfo
    return self.NameToInfo[name]
KeyError: 'opt/magnatune/info/song_info.xml'
(rhythmbox:3488): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3488): 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-10-20 03:31:13 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 ***