Bug 470125 – crash in Rhythmbox Music Player: Nothing

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 470125 - crash in Rhythmbox Music Player: Nothing


Summary:	crash in Rhythmbox Music Player: Nothing


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-25 08:02 UTC by onlyshy
Modified:	2007-08-27 12:45 UTC

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

Description onlyshy 2007-08-25 08:02:42 UTC

What were you doing when the application crashed?
Nothing


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: 500678656 vsize: 500678656 resident: 41009152 share: 20578304 rss: 41009152 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188028973 rtime: 271 utime: 246 stime: 25 cutime:1 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912709347520 (LWP 3289)]
[New Thread 1105209680 (LWP 3319)]
[New Thread 1084229968 (LWP 3316)]
[New Thread 1115699536 (LWP 3314)]
[New Thread 1094719824 (LWP 3293)]
(no debugging symbols found)
0x00002aaab1889728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 157769

Thread 2 (Thread 1105209680 (LWP 3319))

#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

Comment 1 palfrey 2007-08-27 12:45:54 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 ***