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 456695 - crash in Rhythmbox Music Player: Opening a song from Magn...
crash in Rhythmbox Music Player: Opening a song from Magn...
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-13 19:20 UTC by jnilsson
Modified: 2007-07-15 00:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jnilsson 2007-07-13 19:20:22 UTC
What were you doing when the application crashed?
Opening a song from Magnatune


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (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: Glider
Icon Theme: gnome

Memory status: size: 144637952 vsize: 144637952 resident: 51482624 share: 23801856 rss: 51482624 rss_rlim: 4294967295
CPU usage: start_time: 1184379497 rtime: 668 utime: 636 stime: 32 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 -1208972752 (LWP 3859)]
[New Thread -1220465776 (LWP 3876)]
[New Thread -1232417904 (LWP 3866)]
(no debugging symbols found)
0x007dc402 in __kernel_vsyscall ()

Thread 1 (Thread -1208972752 (LWP 3859))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libpython2.5.so.1.0
  • #5 PyEval_GetRestricted
    from /usr/lib/libpython2.5.so.1.0
  • #6 ??
    from /usr/lib/libpython2.5.so.1.0
  • #7 PyMarshal_ReadObjectFromString
    from /usr/lib/libpython2.5.so.1.0
  • #8 PyMarshal_ReadLastObjectFromFile
    from /usr/lib/libpython2.5.so.1.0
  • #9 ??
    from /usr/lib/libpython2.5.so.1.0
  • #10 ??
    from /usr/lib/libpython2.5.so.1.0
  • #11 ??
    from /usr/lib/libpython2.5.so.1.0
  • #12 ??
    from /usr/lib/libpython2.5.so.1.0
  • #13 ??
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyImport_ImportModuleLevel
    from /usr/lib/libpython2.5.so.1.0
  • #15 ??
    from /usr/lib/libpython2.5.so.1.0
  • #16 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #17 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #18 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #19 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #20 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #21 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #22 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #23 ??
    from /usr/lib/libpython2.5.so.1.0
  • #24 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #25 ??
    from /usr/lib/libpython2.5.so.1.0
  • #26 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #27 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #28 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #29 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #30 ??
    from /lib/libglib-2.0.so.0
  • #31 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #32 ??
    from /lib/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #34 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
adding certinfo William Knox Carey <knox@intertrust.com>
The application 'pup' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x140454d (Search for); these messages lack timestamps and therefore suck.
sh: mpg123: command not found
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
/usr/lib/python2.5/site-packages/_xmlplus/dom/minidom.py:1924: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
  from xml.dom import expatbuilder
/usr/lib/python2.5/site-packages/_xmlplus/dom/minidom.py:1924: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
  from xml.dom import expatbuilder
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-15 00:21:28 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 ***