[Bug 1070809] Re: Screen Keyboard messes up Neo-Layout

2014-03-13 Thread Anna Timm
** Also affects: onboard (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070809 Title: Screen Keyboard messes up Neo-Layout To manage

[Bug 1070809] Re: Screen Keyboard messes up Neo-Layout

2014-03-13 Thread Anna Timm
I guess this problem affects every distribution. I have it on Manjaro with onboard v. 0.99.0-1 And its very annoying since you can`t write the most basic symbols EXCLAMATIONMARK It seems like the modification keys are more or less hard coded or unchangeable in onboard. Capslock needs to be

[Bug 1070809] Re: Screen Keyboard messes up Neo-Layout

2013-08-10 Thread Francesco Fumanti
** Also affects: onboard Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070809 Title: Screen Keyboard messes up Neo-Layout To manage notifications about

[Bug 1070809] Re: Screen Keyboard messes up Neo-Layout

2013-02-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: onboard (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070809 Title:

[Bug 1070809] Re: Screen Keyboard messes up Neo-Layout

2013-02-14 Thread Stephan Springer
I can confirm this, although layer 4 is accessible via “Alt Gr”. The layers 3, 5, and 6 are not accessible via the onscreen keyboard, as described above. See http://neo-layout.org/ for a complete layout overview. Hover over “Ebene 1” to “Ebene 6” to see the different layers and which key(s)

[Bug 1070809] Re: Screen Keyboard messes up Neo-Layout

2012-12-24 Thread Fabio Marconi
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at