Bug 466341 – crash in Rhythmbox Music Player: Closing the Application

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 466341 - crash in Rhythmbox Music Player: Closing the Application


Summary:	crash in Rhythmbox Music Player: Closing the Application


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-13 19:14 UTC by hsevcik
Modified:	2007-08-23 09:36 UTC

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

Description hsevcik 2007-08-13 19:14:15 UTC

What were you doing when the application crashed?
Closing the Application


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:10:34 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: 96169984 vsize: 96169984 resident: 33398784 share: 22237184 rss: 33398784 rss_rlim: 4294967295
CPU usage: start_time: 1187032419 rtime: 170 utime: 152 stime: 18 cutime:2 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209046480 (LWP 2983)]
[New Thread -1245660272 (LWP 2990)]
[New Thread -1220736112 (LWP 2988)]
[New Thread -1233753200 (LWP 2987)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 154946

Thread 2 (Thread -1245660272 (LWP 2990))

#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 free
from /lib/libc.so.6



----------- .xsession-errors ---------------------
(evolution:2857): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9eed130'
Data Dir: /usr/share/gnome-applets/invest-applet
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (gnome-cd:2978): WARNING **: Error opening CD
** (gnome-cd:2978): WARNING **: ERROR: Could not open CD device for reading.
** (gnome-cd:2978): WARNING **: ERROR: Could not open CD device for reading.
(rhythmbox:2983): 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-08-23 09:36:34 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 ***