This bug has somehow been fixed. As I mentioned above, LottaNZB works
just fine using Python 2.6.
** Changed in: lottanzb
Status: New = Invalid
** Changed in: pygobject (Ubuntu)
Status: Incomplete = Invalid
--
Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
According to a message by Matthias Klose in ubuntu-devel, the Python
interpreter will be updated from 2.5.4 to 2.6 within the next days and
numerous packages will be rebuilt for that purpose. Since the bug only
affects Python 2.5 I assume that everything will be fine after the
transition. I'll
Changelog of python-gobject_2.16.1-0ubuntu2:
https://edge.launchpad.net/ubuntu/jaunty/+source/pygobject/2.16.1-0ubuntu2
* Remove explicit dependencies on python2.5.
* Rename -dbg extensions for python2.6 as well. LP: #333557.
** Also affects: lottanzb
Importance: Undecided
Status:
I seem to have found a solution. Right now, the GObjectSingletonMeta
metaclass is part of the util module. Moving it to the core module where
it is actually used by the App class solved the problem. This is totally
weird.
I was able to create a simple script that demonstrates the problem.
demo.py
Forgot to remove unnecessary stuff from the demo.py file. Download this
one and not the one above.
** Attachment added: demo.py
http://launchpadlibrarian.net/23146820/demo.py
--
Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
https://bugs.launchpad.net/bugs/334784
You received this
...and the demo_util.py file.
** Attachment added: demo_util.py
http://launchpadlibrarian.net/23146823/demo_util.py
--
Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
https://bugs.launchpad.net/bugs/334784
You received this bug notification because you are a member of Ubuntu
Desktop
2.16.1-0ubuntu1 and 2.16.1-0ubuntu2 don't have any code changes; are you
sure that you didn't use 2.15.x before?
--
Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
https://bugs.launchpad.net/bugs/334784
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
The most interesting thing about it is that the order of the three
import statements in demo.py has an effect on what happens:
# Finally leads to the segfault described in this bug report.
from kiwi.environ import Application
from gobject import property, GObject
from demo_util import
@Matthias:
I've downloaded the required files from
https://edge.launchpad.net/ubuntu/jaunty/+source/pygobject/2.16.1-0ubuntu1,
built it using dpkg-source -x and installed the package using dpkg
--install --force-all (which replaced the ubuntu2 version). Everything
was fine after this. Upgrading
lant...@gauss:~/Desktop$ python demo.py # Using 2.16.1-0ubuntu2.
Segmentation fault (core dumped)
lant...@gauss:~/Desktop$ sudo dpkg --install --force-all
python-gobject_2.16.1-0ubuntu1_amd64.deb
[...]
Vorbereiten zum Ersetzen von python-gobject 2.16.1-0ubuntu2 (durch
Sorry for bothering you once more. I'm not quite sure what to think
about it. In addition to the ubuntu1, I built the ubuntu2 pacakge by
myself a few minutes ago, and now it looks as if the application
segfaults if either the self-built ubuntu1 package (why did this work
before?!) or the official
12 matches
Mail list logo
