Bug 490581 – crash in Rhythmbox Music Player: going into visualastion ...

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 490581 - crash in Rhythmbox Music Player: going into visualastion ...


Summary:	crash in Rhythmbox Music Player: going into visualastion ...


Status:	RESOLVED DUPLICATE of bug 465946

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.10.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-26 16:44 UTC by TJSki1985
Modified:	2007-10-27 04:39 UTC

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

Description TJSki1985 2007-10-26 16:44:14 UTC

Version: 0.10.1

What were you doing when the application crashed?
going into visualastion mode


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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 152502272 vsize: 152502272 resident: 46678016 share: 25649152 rss: 46678016 rss_rlim: 4294967295
CPU usage: start_time: 1193415792 rtime: 5673 utime: 4999 stime: 674 cutime:4 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 -1209058768 (LWP 2972)]
[New Thread -1345332336 (LWP 3383)]
[New Thread -1288701040 (LWP 3354)]
[New Thread -1243149424 (LWP 3025)]
[New Thread -1218827376 (LWP 3024)]
[New Thread -1264338032 (LWP 3023)]
[New Thread -1274827888 (LWP 3022)]
[New Thread -1232659568 (LWP 2984)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 173080

Thread 2 (Thread -1345332336 (LWP 3383))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 ??
#6 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#7 ??
#8 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#9 ??
#10 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#11 ??
#12 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#13 ??
#14 ??
#15 ??
#16 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#17 rhythmdb_entry_type_foreach
#18 ??
#19 ??
#20 ??
from /lib/libglib-2.0.so.0
#21 start_thread
from /lib/libpthread.so.0
#22 clone
from /lib/libc.so.6



----------- .xsession-errors (21 sec old) ---------------------
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x320012c specified for 0x3200131 (Tip of the).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x320012c specified for 0x3200131 (Tip of the).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x320012c specified for 0x3200131 (Tip of the).
** Message: Found best visual for GL: 0x25
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
Xlib: unexpected async reply (sequence 0x38d02)!
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-10-27 04:39:34 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 465946 ***