Bug 484917 – crash in Rhythmbox Music Player: tentando escutar um mp3

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 484917 - crash in Rhythmbox Music Player: tentando escutar um mp3


Summary:	crash in Rhythmbox Music Player: tentando escutar um mp3


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-10-09 03:03 UTC by vinyciol
Modified:	2007-10-09 11:10 UTC

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

Description vinyciol 2007-10-09 03:03:38 UTC

What were you doing when the application crashed?
tentando escutar um mp3	


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 545759232 vsize: 545759232 resident: 40738816 share: 20094976 rss: 40738816 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191898742 rtime: 732 utime: 646 stime: 86 cutime:0 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912709347520 (LWP 3825)]
[New Thread 1168148816 (LWP 3936)]
[New Thread 1105209680 (LWP 3843)]
[New Thread 1094719824 (LWP 3831)]
(no debugging symbols found)
0x00002aaab1889728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 168918

Thread 2 (Thread 1168148816 (LWP 3936))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /lib64/libglib-2.0.so.0
#6 g_log
from /lib64/libglib-2.0.so.0
#7 ??
from /lib64/libgthread-2.0.so.0
#8 ??
from /usr/lib64/libgnomevfs-2.so.0
#9 ??
from /usr/lib64/libgnomevfs-2.so.0
#10 ??
from /lib64/libglib-2.0.so.0
#11 ??
from /lib64/libglib-2.0.so.0
#12 start_thread
from /lib64/libpthread.so.0
#13 clone
from /lib64/libc.so.6



----------- .xsession-errors ---------------------
localuser:vinycio being added to access control list
SESSION_MANAGER=local/bd06f0b8.virtua.com.br:/tmp/.ICE-unix/2805
** (gnome-session:2805): WARNING **: Host name lookup failure on localhost.
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(gnome-terminal:3370): Vte-CRITICAL **: _vte_ring_insert_preserve: assertion `position <= _vte_ring_next(ring)' failed
(rhythmbox:3825): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo ou recurso está ocupado' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-10-09 11:10:52 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 ***