Bug 499203 – crash in Rhythmbox Music Player: neviem

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 499203 - crash in Rhythmbox Music Player: neviem


Summary:	crash in Rhythmbox Music Player: neviem


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-11-23 17:01 UTC by batman_bat
Modified:	2007-11-25 11:49 UTC

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

Description batman_bat 2007-11-23 17:01:33 UTC

What were you doing when the application crashed?
neviem


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 135319552 vsize: 135319552 resident: 33099776 share: 18948096 rss: 33099776 rss_rlim: 4294967295
CPU usage: start_time: 1195837128 rtime: 738 utime: 664 stime: 74 cutime:2 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 -1208808912 (LWP 3861)]
[New Thread -1279267952 (LWP 4032)]
[New Thread -1331717232 (LWP 3983)]
[New Thread -1289757808 (LWP 3974)]
[New Thread -1268778096 (LWP 3970)]
[New Thread -1256297584 (LWP 3966)]
[New Thread -1220789360 (LWP 3867)]
(no debugging symbols found)
0x00a3d402 in __kernel_vsyscall ()

+ Trace 179377

Thread 2 (Thread -1279267952 (LWP 4032))

#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 ??
#17 ??
#18 ??
#19 ??
#20 ??
from /lib/libglib-2.0.so.0
#21 ??
#22 ??
from /lib/libglib-2.0.so.0



----------- .xsession-errors (318 sec old) ---------------------
--- Hash table keys for warning below:
--> file:///home/Jozef
(nautilus:3418): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Loading "installonlyn" plugin
--- Hash table keys for warning below:
--> file:///home/Jozef
(nautilus:3450): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 1 element at quit time (keys above)
--- Hash table keys for warning below:
--> file:///home/Jozef
(nautilus:3450): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
--------------------------------------------------

Comment 1 Susana 2007-11-25 11:49:00 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 ***