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 455072 - crash in Rhythmbox Music Player: open
crash in Rhythmbox Music Player: open
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-09 08:05 UTC by jilichao2008
Modified: 2007-07-09 11:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jilichao2008 2007-07-09 08:05:20 UTC
What were you doing when the application crashed?
open


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 1056468992 vsize: 1056468992 resident: 211447808 share: 18280448 rss: 211447808 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183881364 rtime: 3992 utime: 3753 stime: 239 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912709347520 (LWP 4039)]
[New Thread 1178904912 (LWP 4186)]
[New Thread 1168415056 (LWP 4185)]
[New Thread 1157925200 (LWP 4184)]
[New Thread 1126189392 (LWP 4183)]
[New Thread 1084229968 (LWP 4182)]
[New Thread 1115699536 (LWP 4181)]
[New Thread 1199884624 (LWP 4179)]
[New Thread 1147435344 (LWP 4178)]
[New Thread 1126455632 (LWP 4060)]
[New Thread 1105209680 (LWP 4050)]
[New Thread 1094719824 (LWP 4046)]
(no debugging symbols found)
0x00002aaab188a89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912709347520 (LWP 4039))

  • #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 (20 sec old) ---------------------
** (gnome-cd:3991): WARNING **: ERROR: Could not open CD device for reading.
** (gnome-cd:3991): WARNING **: ERROR: Could not open CD device for reading.
** (gnome-cd:3991): WARNING **: ERROR: Could not open CD device for reading.
** (gnome-cd:3991): WARNING **: ERROR: Could not open CD device for reading.
** (gnome-cd:3991): WARNING **: ERROR: Could not open CD device for reading.
** (gnome-cd:3991): WARNING **: ERROR: Could not open CD device for reading.
gnome-mount 0.6
sys:1: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
rhythmbox: Python/ceval.c:2626:PyEval_EvalCodeEx: 断言“tstate != ((void *)0)”失败。
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-09 11:24:51 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 ***