Sorry, I accidently wrote to a duplicate of this bug instead of this one.
I do have a question though: I see there is a fix released. Is it already
implemented?
I am un gutsy with the latest updates and the error is still happening.
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https:
Fixed with:
gst0.10-python (0.10.9-1) unstable; urgency=low
* New upstream release, "I've heard a lot of stories in my time":
+ Fixes crash at exit (Closes: #448621).
* debian/control:
+ Build depend on gstreamer and gst-plugins-base >= 0.10.15 to get
bindings for the new APIs.
** Changed in: listen
Status: New => Won't Fix
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/123870
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubun
** Changed in: pygobject (Ubuntu)
Status: Confirmed => New
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/123870
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs maili
** Also affects: gst0.10-python (Ubuntu)
Importance: Undecided
Status: New
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/123870
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I believe that this is a bug in gst0.10-python, which calls the
gst_deinit via "atexit" (the C function, not the python module). Since
I'm absolutely clueless about extension modules, somebody else should
confirm this ;)
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launch
This still happens on hardy, with python-gobject 2.14.0-4, and
libglib2.0-0 2.14.4-1ubuntu1.
I found out that Py_Finalize calls _PyGILState_Fini which sets the
autoInterpreterState to NULL. Libgstreamer is deinitialized after that
in the exit call from libc and calls the finalize method of the
pyg
using Gutsy Studio release found this crash report today in my crash
folder
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/123870
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
Using Gutsy beta. Quod Libet crashed when adding Internet Radio tags.
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/123870
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
** Changed in: pygobject (Ubuntu)
Importance: High => Medium
Status: Incomplete => New
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/123870
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
And the testcase:
Install listen, and then:
MOZILLA_FIVE_HOME=/usr/lib/firefox LD_LIBRARY_PATH=/usr/lib/firefox gdb python
(gdb) run /usr/lib/listen/listen.py
Then simply close listen, and you'll have the crash.
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.ne
I'm not sure, since I'm not an expert with gdb, but every crash (including all
the duplicates) has a call to gobject before the crash:
#2 0xb7cc2c2d in ?? () from
/var/lib/python-support/python2.5/gtk-2.0/gobject/_gobject.so
So I thought that was the cause.
Also, bdmurray told me to move it her
Why do you think that's a pygobject bug? Do you a simple testcase to
trigger it?
** Changed in: pygobject (Ubuntu)
Status: Triaged => Incomplete
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/123870
You received this bug notification because you a
** Changed in: pygobject (Ubuntu)
Status: Confirmed => Triaged
--
listen.py crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/123870
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
Moving to pygobject.
Increasing importance due to all the packages it's affecting.
>From the dups, this is happening in some apps, all of them with a similar
>backtrace.
In listen's case, it's not very important, since it's upon exit, but in other
apps it's happening at startup, which is worse.
15 matches
Mail list logo
