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 467862 - crash in Rhythmbox Music Player: escuchando musica (liste...
crash in Rhythmbox Music Player: escuchando musica (liste...
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-08-18 02:44 UTC by pedro_mccumber
Modified: 2007-08-20 08:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description pedro_mccumber 2007-08-18 02:44:34 UTC
What were you doing when the application crashed?
escuchando musica (listen music)


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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 329842688 vsize: 329842688 resident: 166359040 share: 31363072 rss: 166359040 rss_rlim: 4294967295
CPU usage: start_time: 1187399297 rtime: 11967 utime: 11069 stime: 898 cutime:2 cstime: 5 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 -1208788432 (LWP 4403)]
[New Thread -1437459568 (LWP 4742)]
[New Thread -1426969712 (LWP 4741)]
[New Thread -1416479856 (LWP 4740)]
[New Thread -1405990000 (LWP 4739)]
[New Thread -1332561008 (LWP 4732)]
[New Thread -1364030576 (LWP 4729)]
[New Thread -1226679408 (LWP 4430)]
[New Thread -1261737072 (LWP 4421)]
(no debugging symbols found)
0x0012a402 in __kernel_vsyscall ()

Thread 1 (Thread -1208788432 (LWP 4403))

  • #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_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #9 ??
    from /usr/lib/libpython2.5.so.1.0
  • #10 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #11 ??
    from /usr/lib/libpython2.5.so.1.0
  • #12 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #13 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #15 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (12 sec old) ---------------------
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1803ccb
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x180495f
sys:1: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
rhythmbox: Python/ceval.c:2626: PyEval_EvalCodeEx: La declaración `tstate != ((void *)0)' no se cumple.
sys:1: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  159
  Minor opcode:  6
  Resource id:  0x48
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-08-20 08:07:54 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 ***