Bug 457246 – crash in Rhythmbox Music Player: can not open mp3 file

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 457246 - crash in Rhythmbox Music Player: can not open mp3 file


Summary:	crash in Rhythmbox Music Player: can not open mp3 file


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-16 01:30 UTC by cxshit
Modified:	2007-07-16 22:18 UTC

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

Description cxshit 2007-07-16 01:30:16 UTC

What were you doing when the application crashed?
can not open mp3 file


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.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 884293632 vsize: 884293632 resident: 237367296 share: 36720640 rss: 237367296 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184549049 rtime: 3628 utime: 3465 stime: 163 cutime:3 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912554752784 (LWP 5643)]
[New Thread 1136679248 (LWP 5916)]
[New Thread 1220598096 (LWP 5847)]
[New Thread 1157658960 (LWP 5771)]
[New Thread 1105209680 (LWP 5698)]
[New Thread 1084229968 (LWP 5648)]
(no debugging symbols found)
0x00002aaaac536808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 148268

Thread 2 (Thread 1136679248 (LWP 5916))

#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 (1975 sec old) ---------------------
478  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
478  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
479  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
479  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
479  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
479  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
479  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
479  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
479  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
479  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
480  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
480  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
480  [Porter] ERROR edu.tsinghua.lumaqq.qq.net.Porter  - 
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-16 22:18:47 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 ***