Bug 569119 – crash in Rhythmbox Music Player: cambio di web-radio

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 569119 - crash in Rhythmbox Music Player: cambio di web-radio


Summary:	crash in Rhythmbox Music Player: cambio di web-radio


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:	2009-01-25 19:53 UTC by skyy
Modified:	2009-01-25 22:44 UTC

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

Description skyy 2009-01-25 19:53:14 UTC

Version: 0.11.6

What were you doing when the application crashed?
cambio di web-radio


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26.2-avalon #1 SMP Tue Sep 9 17:24:44 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: GartoonRedux

Memory status: size: 182050816 vsize: 182050816 resident: 42708992 share: 21532672 rss: 42708992 rss_rlim: 4294967295
CPU usage: start_time: 1232913063 rtime: 2686 utime: 2619 stime: 67 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6505720 (LWP 4067)]
[New Thread 0xae5fab90 (LWP 4151)]
[New Thread 0xaedfbb90 (LWP 4150)]
[New Thread 0xaf5fcb90 (LWP 4147)]
[New Thread 0xb2ffeb90 (LWP 4128)]
[New Thread 0xb063fb90 (LWP 4123)]
[New Thread 0xb0e40b90 (LWP 4122)]
[New Thread 0xb1641b90 (LWP 4121)]
[New Thread 0xb1f56b90 (LWP 4120)]
[New Thread 0xb2757b90 (LWP 4116)]
[New Thread 0xb4b18b90 (LWP 4115)]
[New Thread 0xb27bcb90 (LWP 4114)]
[New Thread 0xb37ffb90 (LWP 4079)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 211862

Thread 4 (Thread 0xaf5fcb90 (LWP 4147))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
#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 ??
from /usr/lib/libmms.so.0
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??



----------- .xsession-errors ---------------------
** 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)
GCJ PLUGIN: thread 0x805fd78: NP_GetMIMEDescription
GCJ PLUGIN: thread 0x805fd78: NP_GetMIMEDescription return
GCJ PLUGIN: thread 0x805fd78: NP_GetValue
GCJ PLUGIN: thread 0x805fd78: NP_GetValue: returning plugin name.
GCJ PLUGIN: thread 0x805fd78: NP_GetValue return
GCJ PLUGIN: thread 0x805fd78: NP_GetValue
GCJ PLUGIN: thread 0x805fd78: NP_GetValue: returning plugin description.
GCJ PLUGIN: thread 0x805fd78: NP_GetValue return
Cannot access memory at address 0x7
Cannot access memory at address 0x7
--------------------------------------------------

Comment 1 Jonathan Matthew 2009-01-25 22:44:19 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!

Crashed somewhere in libmms, so that's probably where the bug is.