Bug 473129 – crash in Rhythmbox Music Player: updating fresh install ...

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 473129 - crash in Rhythmbox Music Player: updating fresh install ...


Summary:	crash in Rhythmbox Music Player: updating fresh install ...


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-09-03 11:28 UTC by ricksturgeon
Modified:	2007-09-05 16:58 UTC

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

Description ricksturgeon 2007-09-03 11:28:01 UTC

What were you doing when the application crashed?
updating fresh install	






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: 118611968 vsize: 118611968 resident: 29306880 share: 17297408 rss: 29306880 rss_rlim: 4294967295
CPU usage: start_time: 1188818684 rtime: 702 utime: 632 stime: 70 cutime:3 cstime: 1 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 -1208378832 (LWP 3299)]
[New Thread -1266689136 (LWP 3371)]
[New Thread -1245709424 (LWP 3356)]
[New Thread -1287668848 (LWP 3340)]
[New Thread -1233077360 (LWP 3304)]
(no debugging symbols found)
0x00516402 in __kernel_vsyscall ()

+ Trace 160052

Thread 2 (Thread -1266689136 (LWP 3371))

#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 ---------------------
  File "/usr/lib/rhythmbox/plugins/magnatune/MagnatuneSource.py", line 312, in __download_update_cb
    out.write(catalog.read("opt/magnatune/info/song_info.xml"))
  File "/usr/lib/python2.5/zipfile.py", line 471, in read
    zinfo = self.getinfo(name)
  File "/usr/lib/python2.5/zipfile.py", line 462, in getinfo
    return self.NameToInfo[name]
KeyError: 'opt/magnatune/info/song_info.xml'
Loading "installonlyn" plugin
(rhythmbox:3299): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3299): 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 palfrey 2007-09-05 16:58:43 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 434003 ***