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 448332 - crash in Rhythmbox Music Player: click (double) in play i...
crash in Rhythmbox Music Player: click (double) in play i...
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-06-16 21:57 UTC by juan_sr
Modified: 2007-06-17 11:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description juan_sr 2007-06-16 21:57:05 UTC 
What were you doing when the application crashed?
click (double) in play icon.


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 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 690761728 vsize: 690761728 resident: 59338752 share: 31977472 rss: 59338752 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182030714 rtime: 881 utime: 798 stime: 83 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496458304 (LWP 27531)]
[New Thread 1189394768 (LWP 27638)]
[New Thread 1168415056 (LWP 27636)]
[New Thread 1157925200 (LWP 27635)]
[New Thread 1084229968 (LWP 27634)]
[New Thread 1115699536 (LWP 27633)]
[New Thread 1147435344 (LWP 27632)]
[New Thread 1136945488 (LWP 27630)]
[New Thread 1126455632 (LWP 27628)]
[New Thread 1115965776 (LWP 27558)]
[New Thread 1105209680 (LWP 27551)]
(no debugging symbols found)
0x00000033bea0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 141525

Thread 1 (Thread 46912496458304 (LWP 27531))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 __assert_fail
    from /lib64/libc.so.6
  • #6 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #7 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #8 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #9 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #10 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #11 PyEval_CallObjectWithKeywords
    from /usr/lib64/libpython2.5.so.1.0
  • #12 ??
    from /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #13 ??
    from /lib64/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #15 ??
    from /lib64/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (22 sec old) ---------------------
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x14076ff
(rhythmbox:27531): GStreamer-CRITICAL **: 
Trying to dispose element vorbisdec9, but it is not in the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
rhythmbox: Python/ceval.c:2626: PyEval_EvalCodeEx: Assertiva `tstate != ((void *)0)' falhou.
sys:1: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x65
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-17 11:04:52 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 ***