Your message dated Sun, 3 Apr 2011 22:32:35 +0200
with message-id <201104032232.36226.gud...@gudjon.org>
and subject line Re: Bug#620723: eric: Eric won't start anymore, throwing a
siplib error
has caused the Debian Bug report #620723,
regarding eric: Eric won't start anymore, throwing a siplib error
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
620723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eric
Version: 4.4.12-1
Severity: grave
Justification: renders package unusable
Hello,
When trying to run eric on my machine, the application aborts with
the following error:
python: /tmp/buildd/sip4-4.12.1/siplib/siplib.c:10831: sipEnumType_alloc:
Assertion `(((currentType)->td_flags & 0x0007) == 0x0003)' failed.
Aborted
I'm running Debian Testing and I noticed that there have been quite
a few python and pyqt4 upgrades recently, and thus I suspect one of
them is to blame. I set the bug severity to grave as it prevents me
from running the application; please feel free to change it to a
more appropriate level it that's the case.
I understand that this problem may be caused by a bug in some other
package other than eric itself (maybe one of the pyqt4 packages),
but as I'm not sure about that, I decided to report it here knowing
that the maintainers will change it to the appropriate package if
that's the case.
Thank you very much,
Adriano
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=pt_BR (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages eric depends on:
ii bicyclerepair 0.9-6 A refactoring tool for python
ii python 2.6.6-12 interactive high-level object-orie
ii python-chardet 2.0.1-1 universal character encoding detec
ii python-pygments 1.4+dfsg-1 syntax highlighting package writte
ii python-qscintilla2 2.4.3-1+b1 Python bindings for QScintilla 2
ii python-qt4 4.8.3-2 Python bindings for Qt4
ii python-support 1.0.11 automated rebuilding support for P
Versions of packages eric recommends:
ii eric-api-files 4.4.12-1 API description files for use with
Versions of packages eric suggests:
ii pyqt4-dev-tools 4.8.3-2 Development tools for PyQt4
pn python-doc <none> (no description available)
pn python-kde4-doc <none> (no description available)
pn python-profiler <none> (no description available)
pn python-qt4-doc <none> (no description available)
pn python-qt4-sql <none> (no description available)
ii qt4-designer 4:4.7.2-3 graphical designer for Qt 4 applic
pn qt4-dev-tools <none> (no description available)
pn qt4-doc-html <none> (no description available)
ii ruby 4.5 An interpreter of object-oriented
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: eric
Version: 4.4.12-1
Hi
This bug is caused by python-qscintilla2. You have three options to solve
the problem
1. Upgrade python-qscintilla2 to version 2.4.3-2 from unstable.
2. Rebuild python-qscintilla2,
$apt-get source python-qscintilla2
$cd qscintilla2-2.4.3
$fakeroot dpkg-buildpackage
$cd ..
$sudo dpkg -i *.deb
This situation has happened several times earlier and this trick always seems
to solve the problem.
3. Wait for a few days until python-qscintilla2 reaches testing.
Regards
Gudjon
--- End Message ---
