Bug 497266 – crash in Rhythmbox Music Player: ;fdlg;gl';

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 497266 - crash in Rhythmbox Music Player: ;fdlg;gl';


Summary:	crash in Rhythmbox Music Player: ;fdlg;gl';


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-16 02:33 UTC by sjaya
Modified:	2007-11-18 14:50 UTC

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

Description sjaya 2007-11-16 02:33:23 UTC

What were you doing when the application crashed?
;fdlg;gl';


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: 97968128 vsize: 97968128 resident: 27688960 share: 15847424 rss: 27688960 rss_rlim: 4294967295
CPU usage: start_time: 1195209161 rtime: 245 utime: 214 stime: 31 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 -1208608208 (LWP 8522)]
[New Thread -1246143600 (LWP 8533)]
[New Thread -1220310128 (LWP 8529)]
[New Thread -1234609264 (LWP 8526)]
(no debugging symbols found)
0x00daa402 in __kernel_vsyscall ()

+ Trace 178043

Thread 2 (Thread -1246143600 (LWP 8533))

#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

Comment 1 André Klapper 2007-11-18 14:50:14 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 ***