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 451252 - crash in Rhythmbox Music Player: double-clicked on an ite...
crash in Rhythmbox Music Player: double-clicked on an ite...
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-26 14:02 UTC by mcl
Modified: 2007-06-26 22:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mcl 2007-06-26 14:02:49 UTC
What were you doing when the application crashed?
double-clicked on an item in the play queue that was below the current playing item.
Note: I created a queue, started the 2nd one, noticed (I think) that the 1st had moved below the current. That was what I clicked on.


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: Permissive
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 844365824 vsize: 844365824 resident: 57376768 share: 30183424 rss: 57376768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182850870 rtime: 12762 utime: 11569 stime: 1193 cutime:2 cstime: 2 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 46912496372288 (LWP 8706)]
[New Thread 1210108240 (LWP 10984)]
[New Thread 1178638672 (LWP 10982)]
[New Thread 1168148816 (LWP 10981)]
[New Thread 1157658960 (LWP 10980)]
[New Thread 1147169104 (LWP 10978)]
[New Thread 1126189392 (LWP 10977)]
[New Thread 1115699536 (LWP 10974)]
[New Thread 1136679248 (LWP 10973)]
[New Thread 1094719824 (LWP 10972)]
[New Thread 1105209680 (LWP 8716)]
(no debugging symbols found)
0x000000334a2c7956 in poll () from /lib64/libc.so.6

Thread 9 (Thread 1136679248 (LWP 10973))

  • #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_CallFunction
    from /usr/lib64/libpython2.5.so.1.0
  • #11 PyErr_WarnEx
    from /usr/lib64/libpython2.5.so.1.0
  • #12 ??
    from /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #13 g_logv
    from /lib64/libglib-2.0.so.0
  • #14 g_log
    from /lib64/libglib-2.0.so.0
  • #15 g_type_check_instance_cast
    from /lib64/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib64/gstreamer-0.10/libgstgnomevfs.so
  • #17 gnome_vfs_module_callback_invoke
    from /usr/lib64/libgnomevfs-2.so.0
  • #18 ??
    from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
  • #19 ??
    from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
  • #20 ne_begin_request
    from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
  • #21 ??
    from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
  • #22 ??
    from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
  • #23 ??
    from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
  • #24 gnome_vfs_open_uri_cancellable
    from /usr/lib64/libgnomevfs-2.so.0
  • #25 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #26 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #27 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #28 ??
    from /lib64/libglib-2.0.so.0
  • #29 ??
    from /lib64/libglib-2.0.so.0
  • #30 start_thread
    from /lib64/libpthread.so.0
  • #31 clone
    from /lib64/libc.so.6


----------- .xsession-errors (10 sec old) ---------------------
(rhythmbox:8706): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:8706): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:8706): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:8706): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:8706): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:8706): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:8706): RhythmDB-WARNING **: trying to sync properties of non-editable file
** Message: don't know how to handle application/xml
rhythmbox: Python/ceval.c:2626: PyEval_EvalCodeEx: Assertion `tstate != ((void *)0)' failed.
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-26 22:53:11 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 ***