Bug 478215 – crash in Rhythmbox Music Player: quitting

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 478215 - crash in Rhythmbox Music Player: quitting


Summary:	crash in Rhythmbox Music Player: quitting


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-18 23:24 UTC by greg.deutscher
Modified:	2007-09-20 17:22 UTC

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

Description greg.deutscher 2007-09-18 23:24:24 UTC

What were you doing when the application crashed?
quitting


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 08:53:03 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: 103301120 vsize: 103301120 resident: 28065792 share: 16490496 rss: 28065792 rss_rlim: 4294967295
CPU usage: start_time: 1190139762 rtime: 135 utime: 111 stime: 24 cutime:3 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209014560 (LWP 3874)]
[New Thread -1226634352 (LWP 3885)]
[New Thread -1262490736 (LWP 3884)]
[New Thread -1252000880 (LWP 3881)]
[New Thread -1238852720 (LWP 3879)]
(no debugging symbols found)
0x00386402 in __kernel_vsyscall ()

+ Trace 163878

Thread 2 (Thread -1226634352 (LWP 3885))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/i686/nosegneg/libc.so.6
#6 abort
from /lib/i686/nosegneg/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 ---------------------
closing
Loading "installonlyn" plugin
kbuildsycoca running...
Invalid entry (missing '=') at /tmp/kde-root/kconf_updateE5C28b.tmp:1
Invalid entry (missing '=') at /tmp/kde-root/kconf_updateCN07Jb.tmp:1
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4d specified for 0x380000c (scribus).
ScimInputContextPlugin()
~ScimInputContextPlugin()
ScimInputContextPlugin()
~ScimInputContextPlugin()
(rhythmbox:3874): 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-20 17:22:35 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 ***