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 453198 - crash in Rhythmbox Music Player: iniciando el servicio de...
crash in Rhythmbox Music Player: iniciando el servicio de...
Status: RESOLVED DUPLICATE of bug 436456
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-02 19:18 UTC by fjavigon02
Modified: 2007-07-02 23:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description fjavigon02 2007-07-02 19:18:32 UTC
What were you doing when the application crashed?
iniciando el servicio de Magnatune


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.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 177504256 vsize: 177504256 resident: 51326976 share: 22130688 rss: 51326976 rss_rlim: 4294967295
CPU usage: start_time: 1183403875 rtime: 599 utime: 563 stime: 36 cutime:1 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 -1208567248 (LWP 11267)]
[New Thread -1243792496 (LWP 11279)]
[New Thread -1218671728 (LWP 11278)]
[New Thread -1232491632 (LWP 11273)]
(no debugging symbols found)
0x00c60402 in __kernel_vsyscall ()

Thread 1 (Thread -1208567248 (LWP 11267))

  • #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 __assert_fail
    from /lib/libc.so.6
  • #8 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #9 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #10 ??
    from /usr/lib/libpython2.5.so.1.0
  • #11 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #12 ??
    from /usr/lib/libpython2.5.so.1.0
  • #13 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #15 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #16 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #17 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #18 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #19 ??
    from /lib/libexpat.so.0
  • #20 ??
    from /lib/libexpat.so.0
  • #21 ??
    from /lib/libexpat.so.0
  • #22 ??
    from /lib/libexpat.so.0
  • #23 XML_ParseBuffer
    from /lib/libexpat.so.0
  • #24 XML_Parse
    from /lib/libexpat.so.0
  • #25 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #26 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #27 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #28 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #29 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #30 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #31 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #32 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #33 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #34 ??
    from /usr/lib/libpython2.5.so.1.0
  • #35 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #36 ??
    from /usr/lib/libpython2.5.so.1.0
  • #37 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #38 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #39 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #40 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #41 ??
    from /lib/libglib-2.0.so.0
  • #42 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #43 ??
    from /lib/libglib-2.0.so.0
  • #44 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #45 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (11096 sec old) ---------------------
(gnome-background-properties:3196): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:3196): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:3196): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:3196): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:3196): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:3196): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:3196): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-02 23:01:56 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 436456 ***