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 506982 - crash in Rhythmbox Music Player: double clicked play butt...
crash in Rhythmbox Music Player: double clicked play butt...
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: 2008-01-03 07:34 UTC by camsacar
Modified: 2008-01-03 09:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description camsacar 2008-01-03 07:34:33 UTC
What were you doing when the application crashed?
double clicked play button		


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 178655232 vsize: 178655232 resident: 38891520 share: 19374080 rss: 38891520 rss_rlim: 4294967295
CPU usage: start_time: 1199337487 rtime: 26609 utime: 25029 stime: 1580 cutime:2 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 -1208845776 (LWP 9567)]
[New Thread -1380115568 (LWP 12699)]
[New Thread -1242948720 (LWP 12691)]
[New Thread -1295529072 (LWP 12690)]
[New Thread -1338156144 (LWP 12689)]
[New Thread -1264059504 (LWP 10410)]
[New Thread -1253569648 (LWP 10408)]
[New Thread -1285039216 (LWP 10407)]
[New Thread -1231647856 (LWP 9573)]
(no debugging symbols found)
0x00b9a402 in __kernel_vsyscall ()

Thread 1 (Thread -1208845776 (LWP 9567))

  • #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 (19 sec old) ---------------------
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
fixme:hook:IsWinEventHookInstalled (32773)-stub!
fixme:hook:IsWinEventHookInstalled (32773)-stub!
fixme:hook:IsWinEventHookInstalled (32773)-stub!
fixme:hook:IsWinEventHookInstalled (32773)-stub!
rhythmbox: Python/ceval.c:2626: PyEval_EvalCodeEx: Assertion `tstate != ((void *)0)' failed.
sys:1: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-01-03 09:11:46 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 ***