Bug 447849 – crash in Rhythmbox Music Player: I closed RhythmBox

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 447849 - crash in Rhythmbox Music Player: I closed RhythmBox


Summary:	crash in Rhythmbox Music Player: I closed RhythmBox


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-06-15 11:51 UTC by john
Modified:	2007-06-15 12:46 UTC

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

Description john 2007-06-15 11:51:32 UTC

What were you doing when the application crashed?
I closed RhythmBox


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 142946304 vsize: 142946304 resident: 54857728 share: 25198592 rss: 54857728 rss_rlim: 4294967295
CPU usage: start_time: 1181908219 rtime: 2419 utime: 2304 stime: 115 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 -1208301008 (LWP 2977)]
[New Thread -1279304816 (LWP 3126)]
[New Thread -1300284528 (LWP 3117)]
[New Thread -1310774384 (LWP 3020)]
[New Thread -1258325104 (LWP 2986)]
(no debugging symbols found)
0x00d02402 in __kernel_vsyscall ()

+ Trace 141176

Thread 2 (Thread -1279304816 (LWP 3126))

#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 ---------------------
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: <info>  You are now connected to the wired network.
** Message: <info>  You are now connected to the wireless network 'linksys'.
(gnome-about:2921): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x69 specified for 0x14015e3 ().
(rhythmbox:2977): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:2977): 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-06-15 12:46:30 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 ***