[Bug 205343] Re: onboard crashes when used remotely even with custom layout

[Kees Cook]

** Description changed:

  Binary package hint: onboard
  
  The title suggested by apport was: onboard crashed with SIGSEGV in XkbGetNames()
  (I changed it to distinguish it from the similar title already filed as bug #197459, which might be a different issue.)
  
  onboard crashes on launch when used remotely, but not when used localy
  
  When I forward the gnome session through NX from nomachine.com, onboard crashes when it gets launched. This is an issue that was already available in Ubuntu 7.10 (gutsy), but it has got worse: 
  - under gutsy it crashed with the default (autogenerated) layout, but not when using a layout saved in my home directory (in ~/.sok/layouts
  - now onboard (version 0.91ubuntu2) crashes in both cases: when using the default layout also and when using a saved layout 
  
  However, as in gutsy, when onboard is used locacally, it works with the
  default layout and with a saved layout.
  
  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Sat Mar 22 23:27:25 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/onboard
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: nvidia
  Package: onboard 0.91ubuntu2
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/onboard
  ProcEnviron:
   SHELL=/bin/bash
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
  Signal: 11
  SourcePackage: onboard
  StacktraceTop:
   XkbGetNames () from /usr/lib/libX11.so.6
   getKbd () from /usr/lib/python2.5/site-packages/virtkey.so
   ?? () from /usr/lib/python2.5/site-packages/virtkey.so
   ?? ()
   ?? ()
  Title: onboard crashed with SIGSEGV in XkbGetNames()
  Uname: Linux 2.6.24-12-386 i686
  UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev sambashare video
+ SegvAnalysis:
+  Segfault happened at: 0xb73b9f8c <XkbGetNames+108>:	mov    0x1c(%eax),%eax
+  PC (0xb73b9f8c) ok
+  source "0x1c(%eax)" (0x0000001c) not located in a known VMA region (needed readable region)!
+  destination "%eax" ok
+ SegvReason: reading NULL VMA

-- 
onboard crashes when used remotely even with custom layout
https://bugs.launchpad.net/bugs/205343
You received this bug notification because you are a member of
Accessibility, which is subscribed to onboard in ubuntu.