Bug 510487 – crash in Rhythmbox Music Player: codes??

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 510487 - crash in Rhythmbox Music Player: codes??


Summary:	crash in Rhythmbox Music Player: codes??


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:	2008-01-18 21:19 UTC by santosnuno88
Modified:	2008-01-18 21:28 UTC

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

Description santosnuno88 2008-01-18 21:19:24 UTC

What were you doing when the application crashed?
codes??


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

Memory status: size: 122380288 vsize: 122380288 resident: 51875840 share: 19746816 rss: 51875840 rss_rlim: 4294967295
CPU usage: start_time: 1011384926 rtime: 747 utime: 679 stime: 68 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 -1208083920 (LWP 10657)]
[New Thread -1266041968 (LWP 10728)]
[New Thread -1255552112 (LWP 10727)]
[New Thread -1244640368 (LWP 10664)]
(no debugging symbols found)
0x005d3402 in __kernel_vsyscall ()

+ Trace 185879

Thread 2 (Thread -1266041968 (LWP 10728))

#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 (7 sec old) ---------------------
Loading "installonlyn" plugin
Loading "installonlyn" plugin
Loading "installonlyn" plugin
Loading "installonlyn" plugin
Loading "installonlyn" plugin
Aviso do gestor de janelas: Janela 0x4d de WM_TRANSIENT_FOR inválido especificada para 0x2000140 ().
The application 'pup' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
sys:1: GtkWarning: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
(rhythmbox:10657): 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 Christian Kirbach 2008-01-18 21:28:06 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 ***