Segmentation fault and no module named onboard
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Onboard |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi. I use 64bits archlinux and today I've updated my system and onboard refuses to work. I recceive this error
Traceback (most recent call last):
File "/usr/bin/onboard", line 12, in <module>
from Onboard.Exceptions import chain_handler
ImportError: No module named 'Onboard'
I used a onboard trunk version built by myself. Changed to the current 0.98.1 from arch repo and now the error message is more cryptic
[1] 726 segmentation fault (core dumped) onboard
I've tested with lots of different onboard versions (0.98.0, 0.98.1 and 2 different trunks), some of them from Arch's repos and some of them built by myself (using Arch's PKGBUILD's) and the pattern was the same: all the onboard version built BEFORE the update give the no-module error, all the versions built AFTER the update give the segmentation fault.
Probably it is not an onboard bug, it seems pretty obvious that some updated package broke onboard, and maybe downgrading that buggy package will make onboard work again. However there are too muck packages to test blindly. Those were today's modified packages:
[2012-10-17 14:40] removed python-mechanize (0.2.5-2)
[2012-10-17 14:40] removed python-imaging (1.1.7-4)
[2012-10-17 14:40] removed python-notify (0.1.1-11)
[2012-10-17 14:40] removed python-simplejson (2.6.1-1)
[2012-10-17 14:40] upgraded bzr (2.5.1-1 -> 2.5.1-2)
[2012-10-17 14:40] upgraded python2-cssutils (0.9.9-2 -> 0.9.9-3)
[2012-10-17 14:40] upgraded python2-cherrypy (3.2.2-1 -> 3.2.2-2)
[2012-10-17 14:40] installed python2-mechanize (0.2.5-3)
[2012-10-17 14:40] upgraded python2-lxml (2.3.5-1 -> 3.0-1)
[2012-10-17 14:40] installed python2-imaging (1.1.7-5)
[2012-10-17 14:40] upgraded sip (4.13.3-2 -> 4.14-2)
[2012-10-17 14:40] upgraded python2-sip (4.13.3-2 -> 4.14-2)
[2012-10-17 14:40] upgraded python-dbus-common (1.1.1-1 -> 1.1.1-2)
[2012-10-17 14:40] upgraded python2-dbus (1.1.1-1 -> 1.1.1-2)
[2012-10-17 14:40] upgraded pyqt-common (4.9.4-2 -> 4.9.5-2)
[2012-10-17 14:40] upgraded python2-pyqt (4.9.4-2 -> 4.9.5-2)
[2012-10-17 14:40] upgraded python2-psutil (0.6.1-1 -> 0.6.1-2)
[2012-10-17 14:40] upgraded calibre (0.9.2-1 -> 0.9.2-2)
[2012-10-17 14:40] upgraded hplip (3.12.10.a-2 -> 3.12.10.a-3)
[2012-10-17 14:40] upgraded python2-xdg (0.23-1 -> 0.23-2)
[2012-10-17 14:40] installed python2-notify (0.1.1-12)
[2012-10-17 14:40] upgraded ibus (1.4.2-1 -> 1.4.2-2)
[2012-10-17 14:40] upgraded pygobject-devel (3.2.2-1 -> 3.2.2-2)
[2012-10-17 14:40] upgraded pygobject2-devel (2.28.6-6 -> 2.28.6-7)
[2012-10-17 14:40] upgraded python (3.2.3-3 -> 3.3.0-1)
[2012-10-17 14:40] upgraded python-cairo (1.10.0-1 -> 1.10.0-2)
[2012-10-17 14:40] upgraded python-dbus (1.1.1-1 -> 1.1.1-2)
[2012-10-17 14:40] upgraded python-
[2012-10-17 14:40] upgraded python-gobject (3.2.2-1 -> 3.2.2-2)
[2012-10-17 14:40] upgraded python-virtkey (0.61.0-1 -> 0.61.0-2)
[2012-10-17 14:40] upgraded python2-crypto (2.6-2 -> 2.6-3)
[2012-10-17 14:40] upgraded python2-distribute (0.6.28-1 -> 0.6.28-3)
[2012-10-17 14:40] upgraded python2-
[2012-10-17 14:40] upgraded python2-gobject (3.2.2-1 -> 3.2.2-2)
[2012-10-17 14:40] upgraded python2-gobject2 (2.28.6-6 -> 2.28.6-7)
[2012-10-17 14:40] upgraded python2-httplib2 (0.7.4-1 -> 0.7.6-1)
[2012-10-17 14:40] upgraded python2-pyinotify (0.9.3-2 -> 0.9.3-3)
[2012-10-17 14:40] upgraded python2-pyopenssl (0.13-1 -> 0.13-2)
[2012-10-17 14:40] upgraded python2-virtkey (0.61.0-1 -> 0.61.0-2)
[2012-10-17 14:40] upgraded python2-
[2012-10-17 14:40] upgraded system-
[2012-10-17 14:40] upgraded system-
Any idea of the wrong package? Maybe ibus? Thanks
Changed in onboard: | |
status: | New → Fix Committed |
Try running in the debugger:
$ gdb --args python3 /usr/bin/onboard
gdb$ r
wait for the segfault, then:
gdb$ bt
the topmost entries in the backtrace should hint at which modules are involved in the crash.