Bug 455728 – crash in Rhythmbox Music Player: Conectando con Magnatune...

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 455728 - crash in Rhythmbox Music Player: Conectando con Magnatune...


Summary:	crash in Rhythmbox Music Player: Conectando con Magnatune...


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-07-10 22:25 UTC by alfredor2002
Modified:	2007-07-11 08:56 UTC

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

Description alfredor2002 2007-07-10 22:25:44 UTC

What were you doing when the application crashed?
Conectando con Magnatune y actualizando


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

Memory status: size: 287621120 vsize: 287621120 resident: 185139200 share: 47251456 rss: 185139200 rss_rlim: 4294967295
CPU usage: start_time: 1184105680 rtime: 2984 utime: 2828 stime: 156 cutime:4 cstime: 4 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 -1208722896 (LWP 5059)]
[New Thread -1378010224 (LWP 5935)]
[New Thread -1275667568 (LWP 5633)]
[New Thread -1264645232 (LWP 5259)]
[New Thread -1275135088 (LWP 5249)]
[New Thread -1251972208 (LWP 5237)]
(no debugging symbols found)
0x00a5d402 in __kernel_vsyscall ()

+ Trace 147125

Thread 2 (Thread -1378010224 (LWP 5935))

#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 (10 sec old) ---------------------
(rhythmbox:5059): Rhythmbox-WARNING **: Unhandled error: Error de reproducción desconocido
(rhythmbox:5059): Rhythmbox-WARNING **: Unhandled error: Error de reproducción desconocido
(rhythmbox:5059): Rhythmbox-WARNING **: Unhandled error: Error de reproducción desconocido
(rhythmbox:5059): Rhythmbox-WARNING **: Unhandled error: Error de reproducción desconocido
(rhythmbox:5059): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo o recurso ocupado' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
warning: .dynamic section for "/usr/lib/liboil-0.3.so.0" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-11 08:56:27 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 ***