Bug 510413 – crash in Rhythmbox Music Player: 打开播放器

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 510413 - crash in Rhythmbox Music Player: 打开播放器


Summary:	crash in Rhythmbox Music Player: 打开播放器


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 15:15 UTC by jinge81520
Modified:	2008-01-18 23:09 UTC

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

Description jinge81520 2008-01-18 15:15:14 UTC

What were you doing when the application crashed?
打开播放器		


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: 135520256 vsize: 135520256 resident: 29294592 share: 18022400 rss: 29294592 rss_rlim: 4294967295
CPU usage: start_time: 1200669104 rtime: 355 utime: 324 stime: 31 cutime:3 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208477136 (LWP 3970)]
[New Thread -1283454064 (LWP 3996)]
[New Thread -1272964208 (LWP 3995)]
[New Thread -1238729840 (LWP 3993)]
[New Thread -1262474352 (LWP 3991)]
[New Thread -1251251312 (LWP 3977)]
(no debugging symbols found)
0x00931402 in __kernel_vsyscall ()

+ Trace 185836

Thread 3 (Thread -1272964208 (LWP 3995))

#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 free
from /lib/libc.so.6



----------- .xsession-errors ---------------------
  File "/usr/lib/python2.5/site-packages/_xmlplus/sax/handler.py", line 38, in fatalError
    raise exception
xml.sax._exceptions.SAXParseException: <unknown>:1:0: no element found
Traceback (most recent call last):
  File "/usr/lib/rhythmbox/plugins/jamendo/JamendoSource.py", line 162, in finish_loadscreen
    self.__load_db ()
  File "/usr/lib/rhythmbox/plugins/jamendo/JamendoSource.py", line 294, in __load_db
    tracks = self.__saxHandler.tracks
AttributeError: JamendoSaxHandler instance has no attribute 'tracks'
(rhythmbox:3970): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error '设备或资源忙' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
Error, selection data didn't received, retring!
--------------------------------------------------

Comment 1 Jonathan Matthew 2008-01-18 23:09:04 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 ***