Bug 478827 – 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 478827 - 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:	2007-09-21 03:38 UTC by wjw2580
Modified:	2007-09-22 08:37 UTC

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

Description wjw2580 2007-09-21 03:38:55 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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 521113600 vsize: 521113600 resident: 41553920 share: 20504576 rss: 41553920 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190345680 rtime: 258 utime: 222 stime: 36 cutime:1 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 46912496458304 (LWP 2025)]
[New Thread 1147169104 (LWP 2094)]
[New Thread 1115699536 (LWP 2036)]
[New Thread 1094719824 (LWP 2032)]
(no debugging symbols found)
0x000000320260c728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 164301

Thread 2 (Thread 1147169104 (LWP 2094))

#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 ---------------------
GThread-ERROR **: file gthread-posix.c: line 171 (): error '设备或资源忙' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x18085d0
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x18081ab
~ScimInputContextPlugin()
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x3f
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-09-22 08:37:01 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 ***