Onboard segfaults on Ubuntu Hardy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtkey |
New
|
Undecided
|
Unassigned | ||
virtkey (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Unassigned | ||
Intrepid |
Fix Released
|
High
|
Unassigned |
Bug Description
Running Ubuntu hardy with latest archive updates. When attempting to run onboard in any way, a segmentation fault occurs. However, whenever booting the live CD and using the on-screen keyboard
accessibility profile, onboard loads properly. However, when you shut it down, and attempt to run it again, the segmentatino fault occurs.
TEST CASE:
1. Make sure the onboard package is installed.
2. Attempt to run onboard, either from GNOME's run dialog, or from a terminal.
3. Onboard should segfault.
4. Install the python-virtkey package from proposed with Chris' patch.
5. Attempt to run onboard again.
6. Onboard should load successfully.
Regression potential:
Since the package segfaults, except when being booted via the accessibility profile from the live CD, and since geometry information is not needed by python-virtkey, as well as onboard being the only package in the archive that depends on python-virtkey, the chance of a regression is next to nothing.
Course for Intrepid:
As soon as intrepid opens, I will upload a fixed virtkey package.
Changed in onboard: | |
importance: | Undecided → High |
description: | updated |
Changed in virtkey: | |
importance: | Undecided → High |
status: | New → Fix Committed |
status: | Fix Committed → Triaged |
Here is a backtrace:
#0 0xb73d7f8c in XkbGetNames () from /usr/lib/ libX11. so.6 virtkey. c:170 virtkey. c:124 ceval.c: 3573 ceval.c: 2836 funcobject. c:517 abstract. c:1861 classobject. c:2519 abstract. c:1861 typeobject. c:4943 typeobject. c:436 abstract. c:1861 ceval.c: 3784 ceval.c: 2836 ceval.c: 494 veOneFlags (fp=0xb7f48440, filename=0x8123f04 "<stdin>", flags=0xbfd2da78) at ../Python/ pythonrun. c:1273 veLoopFlags (fp=0xb7f48440, filename=0x8123f04 "<stdin>", flags=0xbfd2da78) at ../Python/ pythonrun. c:723 Flags (fp=0xb7f48440, filename=0x8123f04 "<stdin>", closeit=0, flags=0xbfd2da78) at ../Python/ pythonrun. c:692 main.c: 523 python. c:23
#1 0xb6e61932 in getKbd (cvirt=0x83d7ab8) at python-
#2 0xb6e61b0f in virtkey_new (self=0x0, args=0xb7dbc02c) at python-
#3 0x080c9993 in PyEval_EvalFrameEx (f=0x83d0514, throwflag=0) at ../Python/
#4 0x080cb0d7 in PyEval_EvalCodeEx (co=0xb7d84770, globals=0xb7d9502c, locals=0x0, args=0xb7d8bdd8, argcount=1, kws=0x0, kwcount=0, defs=0x839b3d8, defcount=1, closure=0x0) at ../Python/
#5 0x08113430 in function_call (func=0x839c9cc, arg=0xb7d8bdcc, kw=0x0) at ../Objects/
#6 0x0805cb37 in PyObject_Call (func=0x0, arg=0xb7d8bdcc, kw=0x0) at ../Objects/
#7 0x08062b9b in instancemethod_call (func=0x839c9cc, arg=0xb7d8bdcc, kw=0x0) at ../Objects/
#8 0x0805cb37 in PyObject_Call (func=0x0, arg=0xb7dbc02c, kw=0x0) at ../Objects/
#9 0x0809d26b in slot_tp_init (self=0xb7d9a38c, args=0xb7dbc02c, kwds=0x0) at ../Objects/
#10 0x0809ee64 in type_call (type=0x83d1064, args=0xb7dbc02c, kwds=0x0) at ../Objects/
#11 0x0805cb37 in PyObject_Call (func=0x0, arg=0xb7dbc02c, kw=0x0) at ../Objects/
#12 0x080c7987 in PyEval_EvalFrameEx (f=0x83d22ac, throwflag=0) at ../Python/
#13 0x080cb0d7 in PyEval_EvalCodeEx (co=0xb7d84410, globals=0xb7dd5acc, locals=0xb7dd5acc, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at ../Python/
#14 0x080cb227 in PyEval_EvalCode (co=0xb7d84410, globals=0xb7dd5acc, locals=0xb7dd5acc) at ../Python/
#15 0x080eadb0 in PyRun_Interacti
#16 0x080eafd6 in PyRun_Interacti
#17 0x080eb0f2 in PyRun_AnyFileEx
#18 0x08059335 in Py_Main (argc=0, argv=0xbfd2db44) at ../Modules/
#19 0x080587f2 in main (argc=Cannot access memory at address 0x0
) at ../Modules/