Bug 585316 – crash in Rhythmbox Music Player: Activar la tienda Magnat...

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 585316 - crash in Rhythmbox Music Player: Activar la tienda Magnat...


Summary:	crash in Rhythmbox Music Player: Activar la tienda Magnat...


Status:	RESOLVED DUPLICATE of bug 575781

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-06-10 08:38 UTC by roberto.castilla.lopez
Modified:	2009-06-10 08:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Description roberto.castilla.lopez 2009-06-10 08:38:52 UTC

Version: 0.12.0

What were you doing when the application crashed?
Activar la tienda Magnatune


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.29-2-amd64 #1 SMP Sun May 17 17:15:47 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10601901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 583507968 vsize: 583507968 resident: 48160768 share: 22843392 rss: 48160768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1244623126 rtime: 203 utime: 186 stime: 17 cutime:1 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 0x7f0deb979810 (LWP 3055)]
[New Thread 0x7f0dd6857950 (LWP 3063)]
[New Thread 0x7f0dcb49f950 (LWP 3060)]
0x00007f0deae9131f in waitpid () from /lib/libpthread.so.0

+ Trace 215945

Thread 1 (Thread 0x7f0deb979810 (LWP 3055))

#0 waitpid
from /lib/libpthread.so.0
#1 IA__g_spawn_sync
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gspawn.c line 382
#2 IA__g_spawn_command_line_sync
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gspawn.c line 694
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 raise
from /lib/libc.so.6
#7 abort
from /lib/libc.so.6
#8 Py_FatalError
at ../Python/pythonrun.c line 1561
#9 PyEval_SaveThread
at ../Python/ceval.c line 316
#10 ??
from /usr/lib/pymodules/python2.5/gtk-2.0/gobject/_gobject.so
#11 dict_dealloc
at ../Objects/dictobject.c line 855
#12 subtype_dealloc
at ../Objects/typeobject.c line 697
#13 instancemethod_dealloc
at ../Objects/classobject.c line 2311
#14 ??
from /usr/lib/pymodules/python2.5/gtk-2.0/gio/_gio.so
#15 IA__g_datalist_clear
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gdataset.c line 120
#16 IA__g_object_unref
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gobject/gobject.c line 2421
#17 ??
from /usr/lib/gio/modules/libgvfsdbus.so
#18 ??
from /usr/lib/gio/modules/libgvfsdbus.so
#19 ??
from /usr/lib/gio/modules/libgvfsdbus.so
#20 ??
from /usr/lib/gio/modules/libgvfsdbus.so
#21 complete_in_idle_cb
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/gio/gsimpleasyncresult.c line 577
#22 IA__g_main_context_dispatch
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c line 1814
#23 g_main_context_iterate
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c line 2448
#24 IA__g_main_loop_run
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c line 2656
#25 IA__gtk_main
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkmain.c line 1205
#26 main
at main.c line 336
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (260 sec old) ---------------------
camel-Message: --
camel-Message: --
camel-Message: --
(evolution:2301): libecal-WARNING **: e-cal.c:320: Unexpected response
calendar-gui-Message: Error occurred while existing dialog active:
calendar-gui-Message: Check if default client matches (1242118655.21400.2@marro 1242118655.21400.2@marro)
calendar-gui-Message: Check if default client matches (1242118655.21400.2@marro 1242118541.21400.0@marro)
calendar-gui-Message: Error occurred while existing dialog active:
calendar-gui-Message: Error occurred while existing dialog active:
calendar-gui-Message: Error occurred while existing dialog active:
--------------------------------------------------

Comment 1 Jonathan Matthew 2009-06-10 08:54:47 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 575781 ***