GNOME Bugzilla – Bug 593967
Fatal error in PyEval_SaveThread
Last modified: 2009-10-23 07:18:15 UTC
Version: 2.26.2 What were you doing when the application crashed? Closing movie player (totem) Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.26-2-686 #1 SMP Sun Jun 21 04:57:38 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: yasis GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 163205120 vsize: 163205120 resident: 45232128 share: 20467712 rss: 45232128 rss_rlim: 18446744073709551615 CPU usage: start_time: 1251924666 rtime: 11691 utime: 10934 stime: 757 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem-gstreamer' [Thread debugging using libthread_db enabled] [New Thread 0xb0507b90 (LWP 32538)] [New Thread 0xb12ffb90 (LWP 32534)] [New Thread 0xb4d6cb90 (LWP 32299)] [New Thread 0xb2851b90 (LWP 29144)] [New Thread 0xb34a8b90 (LWP 29143)] [New Thread 0xb5679b90 (LWP 29139)] 0xb7f69424 in __kernel_vsyscall ()
+ Trace 217297
Thread 1 (Thread 0xb68cc760 (LWP 29137))
----------- .xsession-errors (1627 sec old) --------------------- (firefox-bin:14851): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:14851): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:14851): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:14851): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:14851): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:14851): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:14851): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 594260 has been marked as a duplicate of this bug. ***
There is a similar crash and several duplicates on https://bugs.launchpad.net/totem/+bug/421318, it started happening recently and doesn't match totem changes so it could be a pygtk issue
(In reply to comment #2) > There is a similar crash and several duplicates on > https://bugs.launchpad.net/totem/+bug/421318, it started happening recently and > doesn't match totem changes so it could be a pygtk issue Agreed.
*** Bug 596788 has been marked as a duplicate of this bug. ***
*** Bug 596820 has been marked as a duplicate of this bug. ***
This was actually a bug in totem's python plugin loader. This should fix it: commit 11d6c1ba5a3fad3bfb34d44e0a4205025c6c5b69 Author: Alessandro Decina <alessandro.decina@collabora.co.uk> Date: Wed Sep 30 18:33:48 2009 +0100 totem-python-plugin: ensure and release GIL before unrefing python object Should fix 'Fatal Python error: PyEval_SaveThread: NULL tstate' error when closing totem with the BBC plugin loaded. Might happen with other python plugins as well. Fixes #593967.
*** Bug 597821 has been marked as a duplicate of this bug. ***
*** Bug 599366 has been marked as a duplicate of this bug. ***