[Bug 526791] Re: onboard crashed with SIGSEGV in XkbGetNames()

2010-09-30 Thread Francesco Fumanti
** Changed in: python-virtkey Status: Fix Committed => Fix Released ** Changed in: onboard (Ubuntu) Status: Fix Committed => Fix Released -- onboard crashed with SIGSEGV in XkbGetNames() https://bugs.launchpad.net/bugs/526791 You received this bug notification because you are a mem

[Bug 526791] Re: onboard crashed with SIGSEGV in XkbGetNames()

2010-06-11 Thread NoBugs!
Fix released? I still sometimes get this crash report on up-to-date 10.04. Do I need to manually install the patch? -- onboard crashed with SIGSEGV in XkbGetNames() https://bugs.launchpad.net/bugs/526791 You received this bug notification because you are a member of Ubuntu Bugs, which is subscrib

[Bug 526791] Re: onboard crashed with SIGSEGV in XkbGetNames()

2010-06-10 Thread Daniel Holbach
** Tags added: patch-accepted-upstream -- onboard crashed with SIGSEGV in XkbGetNames() https://bugs.launchpad.net/bugs/526791 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com http

[Bug 526791] Re: onboard crashed with SIGSEGV in XkbGetNames()

2010-05-04 Thread marmuta
I've pushed a workaround to onboard and virtkey trunks. Instead of crashing on a missing X keyboard, onboard now waits until one becomes available (if ever) and should generally react more dynamically to keyboard and keyboard layout changes. Bug 548891 for vmware users seems resolved, but the worka

[Bug 526791] Re: onboard crashed with SIGSEGV in XkbGetNames()

2010-04-28 Thread Chris Cheney
I think I see this issue also under VMware on a ThinkPad X200 while trying to work on bug 548891. At least very often the virtual keyboard will just briefly when I try to enable it instead of showing up and letting me use it. -- onboard crashed with SIGSEGV in XkbGetNames() https://bugs.launchpad

[Bug 526791] Re: onboard crashed with SIGSEGV in XkbGetNames()

2010-04-13 Thread marmuta
The direct cause of the segfault appears to be a missing error exit in python-virtkey.c. I don't have launchpad access to virtkey, so I'll attach a tiny patch. However this doesn't fix the root cause, it only shifts the error from a SIGSEGV to a python backtrace: Traceback (most recent call last):

[Bug 526791] Re: onboard crashed with SIGSEGV in XkbGetNames()

2010-04-13 Thread marmuta
** Also affects: virtkey Importance: Undecided Status: New -- onboard crashed with SIGSEGV in XkbGetNames() https://bugs.launchpad.net/bugs/526791 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubu

[Bug 526791] Re: onboard crashed with SIGSEGV in XkbGetNames()

2010-04-01 Thread Greg Grossmeier
** Visibility changed to: Public -- onboard crashed with SIGSEGV in XkbGetNames() https://bugs.launchpad.net/bugs/526791 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://li