Bug 564769 – crash in Rhythmbox Music Player: nothing

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 564769 - crash in Rhythmbox Music Player: nothing


Summary:	crash in Rhythmbox Music Player: nothing


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-12-16 18:32 UTC by greenthumbs
Modified:	2008-12-16 22:16 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description greenthumbs 2008-12-16 18:32:03 UTC

Version: 0.11.6

What were you doing when the application crashed?
nothing


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Wed Nov 26 19:14:11 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 103473152 vsize: 103473152 resident: 48930816 share: 19496960 rss: 48930816 rss_rlim: 4294967295
CPU usage: start_time: 1229452232 rtime: 690 utime: 643 stime: 47 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6505720 (LWP 3374)]
[New Thread 0xb603db90 (LWP 3388)]
(no debugging symbols found)
0xb7f45424 in __kernel_vsyscall ()

+ Trace 210862

Thread 1 (Thread 0xb6505720 (LWP 3374))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 g_object_ref
from /usr/lib/libgobject-2.0.so.0
#8 ??
from /usr/lib/librhythmbox-core.so.0
#9 ??
from /usr/lib/librhythmbox-core.so.0
#10 ??
from /usr/lib/librhythmbox-core.so.0
#11 ??
#12 ??
#13 ??
from /usr/lib/librhythmbox-core.so.0
#14 ??
#15 ??
#16 free
from /lib/i686/cmov/libc.so.6
#17 ??
from /usr/lib/librhythmbox-core.so.0
#18 ??
#0 __kernel_vsyscall



----------- .xsession-errors (65 sec old) ---------------------
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
closing
closing
closing
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600022 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Jonathan Matthew 2008-12-16 22:16:46 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!