This bug was fixed in the package onboard - 1.0.0-0ubuntu1
---
onboard (1.0.0-0ubuntu1) trusty; urgency=low
* Request for sponsorship for new upstream release (LP: #1282231)
* debian/control:
- Raise Standards-Version to 3.9.5
- Add librsvg2-common to Depends for Kubuntu
This bug should be fixed with the 1.0.0 release. If you still encounter
problems, please feel free to reopen this bug or file a new one.
** Changed in: onboard
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Branch linked: lp:ubuntu/trusty-proposed/onboard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249493
Title:
onboard keyboard crashes when started in node.js running custom layout
To manage
Thanks for the investigation, and yes, this three stage lookup exists for most
of Onboard's files. The problem seems to be that stage 1) is meant for absolute
paths, rather than local directories, but this isn't enforced. As you
discovered, having a file in the current directory with the same
Should be fixed in trunk now. I've added a check for absolute paths when
locating layouts, themes, etc..
** Changed in: onboard
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So, I figured out what it was. . . the file was fine and onboard is
working fine, but with some unexpected and desired results. I had
created a ubuntu shortcut file named NextGen in the same directory from
which I was running my program. This seemed to cause onboard to use
that file instead of
Implanted into a new layout, the part you posted loads without the error here.
There might be something with the file, perhaps the encoding, but it's hard to
tell from pasted text. Could you attach an archive of the whole layout?
$ tar -cvzf NextGen.tar.gz ~/.local/share/onboard/layouts/NextGen*
