Bug 497619 – crash in Rhythmbox Music Player: aA

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 497619 - crash in Rhythmbox Music Player: aA


Summary:	crash in Rhythmbox Music Player: aA


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-11-17 11:05 UTC by A
Modified:	2007-11-18 14:51 UTC

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

Description A 2007-11-17 11:05:30 UTC

What were you doing when the application crashed?
aA


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 116498432 vsize: 116498432 resident: 28585984 share: 16883712 rss: 28585984 rss_rlim: 4294967295
CPU usage: start_time: 1195296569 rtime: 518 utime: 408 stime: 110 cutime:2 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 -1208288720 (LWP 5189)]
[New Thread -1263092848 (LWP 5231)]
[New Thread -1229083760 (LWP 5229)]
[New Thread -1252602992 (LWP 5228)]
[New Thread -1242113136 (LWP 5195)]
(no debugging symbols found)
0x00d8c402 in __kernel_vsyscall ()

+ Trace 178313

Thread 2 (Thread -1263092848 (LWP 5231))

#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 (33 sec old) ---------------------
    reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files
closing
closing
(gnome-terminal:4418): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(rhythmbox:5189): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running
(rhythmbox:5189): Rhythmbox-WARNING **: Unable to stop mDNS browsing: MDNS service is not running
(rhythmbox:5189): 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 André Klapper 2007-11-18 14:51:16 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 ***