Bug 449496 – crash in Rhythmbox Music Player: L'application marchais n...

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 449496 - crash in Rhythmbox Music Player: L'application marchais n...


Summary:	crash in Rhythmbox Music Player: L'application marchais n...


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-06-20 14:47 UTC by arth.prince
Modified:	2007-06-20 21:56 UTC

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

Description arth.prince 2007-06-20 14:47:52 UTC

What were you doing when the application crashed?
L'application marchais normalement lorsque je l'ai fermée ...


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (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: OSX

Memory status: size: 154730496 vsize: 154730496 resident: 82391040 share: 21704704 rss: 82391040 rss_rlim: 4294967295
CPU usage: start_time: 1182350749 rtime: 475 utime: 451 stime: 24 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 -1208251856 (LWP 3195)]
[New Thread -1232544880 (LWP 3235)]
[New Thread -1253524592 (LWP 3223)]
[New Thread -1222055024 (LWP 3222)]
[New Thread -1243034736 (LWP 3216)]
(no debugging symbols found)
0x006e1402 in __kernel_vsyscall ()

+ Trace 142439

Thread 4 (Thread -1222055024 (LWP 3222))

#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 (338 sec old) ---------------------
(beryl-manager:2516): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
bad image index
(beryl-manager:2516): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
bad image index
(beryl-manager:2516): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
bad image index
(beryl-manager:2516): Gtk-WARNI
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-06-20 21:56:45 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 ***