> We'll very likely make the 18.10 release
I meant to write:
We'll very likely make the 18.04 release
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1672465
Title:
Onboard doesn't
** Also affects: onboardosk
Importance: Undecided
Status: New
** Changed in: onboardosk
Status: New => Confirmed
** Changed in: onboardosk
Importance: Undecided => High
** Changed in: onboard
Status: In Progress => Won't Fix
--
You received this bug notification
Let me give you an update on the current state of Onboard in gnome-
shell.
First, things changed - a lot. The work is happening in a new independent
project OnboardOSK at
https://launchpad.net/onboardosk
This is basically a fork of Onboard, written mainly in C++. There's no Python
involved
> Did anyone try to replace caribou with onboard in gnome-shell, is that
> doable/easy?
I did, and came to the conclusion that fully replacing caribou with the
existing Onboard is close to impossible. That's mainly because applications
don't have access to the activities and authentication
Thank you, for testing.
** Changed in: onboard
Status: New => Fix Committed
** Changed in: onboard (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
Thanks for the bug report. I believe this issue has a fix in trunk, see
https://bazaar.launchpad.net/~onboard/onboard/trunk/revision/2264
and
https://bazaar.launchpad.net/~onboard/onboard/trunk/revision/2265
What Ubuntu version are you running, and did you install Onboard 1.4.1
from our PPA?
**
** Also affects: onboard
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1699844
Title:
Onboard settings and scanning problem
Status in
Thanks, I had fixed that one in trunk already. The current snapshot should be
able to start.
https://launchpad.net/%7Eonboard/+archive/snapshots
I believe there are more regressions on older Ubuntu releases, though.
Francesco mentioned preferences for example. There'll probably be
another minor
ay.
Francesco
PS: This is a bit of topic, but in my opinion nevertheless worth
mentioning here:
Marmuta and I are experiencing crashes to login when Onboard is
running and menus, especially the appindicator menus are used. On my
system, the crashes seem to happen especially, when also
good day.
Francesco
PS: This is a bit of topic, but in my opinion nevertheless worth
mentioning here:
Marmuta and I are experiencing crashes to login when Onboard is
running and menus, especially the appindicator menus are used. On my
system, the crashes seem to happen especially,
age in Ubuntu:
Confirmed
Bug description:
Hi,
Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
package shipping currently in the development version of Ubuntu zesty.
You will find the corresponding debdiff attached to this bug thread.
Marmuta performed te
** Tags added: hidpi
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1562734
Title:
Onboard keyboard shows black box on login
Status in Onboard:
Invalid
Status in onboard
@DH, you can find partial workarounds in comment
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1562734/comments/15
and question
https://answers.launchpad.net/onboard/+question/404618
That's all I know of currently, unfortunately. For anything better we
need cooperation from
*** This bug is a duplicate of bug 1562734 ***
https://bugs.launchpad.net/bugs/1562734
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #1562734, so it is being marked as such. Please
Thanks for the quick response, Brad.
I agree, launchpad works quite well for us. There's not really much
pressure to move away, currently. Also, I feel, as long as Onboard is
installed by default in Ubuntu, we should stay close. The situation may
change with unity 8, we'll see.
> I've always
s/do ask/do you ask/, you know what I mean.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1615575
Title:
Emoji support
Status in Onboard:
Confirmed
Status in onboard package in
Thanks, N.W.
> Are there any plans to move Onboard to GitHub?
Not currently. Why do ask?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1615575
Title:
Emoji support
Status in
Yes, we discussed that recently. Showing colored emoji would be nice, but there
seems to be precious little support for SVG in OpenType on Linux. AFAICT only
Mozilla applications can handle emojione or twemoji at the moment. Even
emojione-picker uses svg files instead. If there is high-level
This confused me too occasionally. There's a warning when starting in
the project directory, now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1619380
Title:
onboard 1.3.0
@Francesco, it's not clear to me yet that upstream onboard is affected.
I did tests with a fresh pt_BR install of Yakkety and couldn't reproduce
the issue. The answer to #6 would be helpful. Until then my best guess
is there is a version mismatch between onboard and its installed
gsettings schema.
There are some emoji in the Small and Phone layouts.
Small: press "12?", then "☺" on the SHIFT key.
Phone: press "12!@" then "1/3" twice
It's a limited selection in both cases, though.
The other layouts don't have any, although there's an older branch were they do:
@Duncan Simpson, please try to upgrade to Onboard 1.3.0. There's a good chance
the Xenial packages will work on Mint 18. You can get them from our stable PPA
at
https://launchpad.net/~onboard/+archive/ubuntu/stable
--
You received this bug notification because you are a member of Desktop
** Changed in: onboard
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1550534
Title:
Suggestions arrows not available on Compact layout
Status in
** Changed in: onboard
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1546654
Title:
Standard configuration proposal
Status in Onboard:
Confirmed
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1570318
Title:
Bad wording in string
Status in Onboard:
Fix
** Changed in: onboard
Status: Confirmed => Fix Released
** Changed in: onboard (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
** Changed in: onboard
Status: Fix Committed => Fix Released
** Changed in: onboard (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
There's UI to change the aspect ratio limit too in 1.3.0. Requires
docking enabled and extend setting checked (default).
Depending on the active layout, either long press the move button or
long press Return and select the move button to show the touch handles.
The single handle on the right
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1586493
Title:
"Expand on landscape screens" option not working in
Fix released in Onboard 1.3.0.
** Changed in: onboard
Status: Fix Committed => Fix Released
** Changed in: onboard (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
Thank you and thanks for the reminder. Francesco already left for
holiday. I'll be available in case anything breaks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1613063
Title:
@pon tech, this is a regression with Onboard 1.2.0, unfortunately. There
are a couple of options:
- Try to install AppIndicator3 and its typelib. On Ubuntu this would be
gir1.2-appindicator3, however http://packages.linuxmint.com doesn't seem
to know it. Perhaps it can't be easily installed then,
*** This bug is a duplicate of bug 1574081 ***
https://bugs.launchpad.net/bugs/1574081
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #1574081, so it is being marked as such. Please
Georgios, there are hazy plans for input method support in the next
release. That would possibly enable auto-show for a wider range of
applications. I've only been experimenting with it, so far. If that
eventually results in something useful I'll update this bug report.
--
You received this bug
*** This bug is a duplicate of bug 1572331 ***
https://bugs.launchpad.net/bugs/1572331
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #1572331, so it is being marked as such. Please
Me neither, thanks for testing. Typing emoji and various diacritics
seems a lot more reliable too. I have yet to find a key that doesn't
work. Also, I can't reproduce bug #1352549 anymore.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Fixed in trunk, I believe. The changes for Bug #1562381 help here too.
Sorry it took so long.
** Changed in: onboard
Status: Confirmed => Fix Committed
** Changed in: onboard
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Rev. 2153 increases the limit a bit.
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Status: New => Fix Committed
** Changed in: onboard (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Trunk has an aspect ratio limit for docking, but that's still work in
progress. There's supposed to be some UI in the future that allows to
toggle/change it. For now you can do this:
gsettings set org.onboard.window docking-aspect-change-range "[0.0,
10.0]"
--
You received this bug notification
Finally fixed in trunk, I believe. Not a duplicate of bug #837456 after
all. It took rewriting key parts of virtkey and a number of workarounds
at the python level, so regression potential is high-ish. However I
didn't notice any remaining issues after rev. 2151. I believe it's ready
for more
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Status: New => Confirmed
** Changed in: onboard
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard
What Onboard exactly does at the point of the layout switch is calling
XSync() right after XTestFakeKeyEvent() (not remapping the layout on the
fly, which it can do to). So its probably the same bug #837456.
I'm still hesitant to duplicate. That bug is so old and nothing ever
came from it. I feel
I had that problem too with some languages. Try adding more input sources in
System Settings->Text Entry. Then temporarily select one that isn't one of the
four listed in
$ setxkbmap -query | grep layout
Ubuntu-GNOME seems to always set up the maximum of 4 layout groups and
only switches
I'm not sure about the responsible package, that's why I hesitated to
mark it as a duplicate. I could reproduce bug #837456 anywhere, but this
one seems to be restricted to Ubuntu-GNOME. I want to check what exactly
Onboard does when it happens too. Haven't had time yet.
Wayland support is on my
Can finally confirm with Russian on Ubuntu-GNOME. Onboard layout doesn't
matter.
What appears to happen is that certain key-presses cause a switch of the system
keyboard layout (group) to English (US). We've seen that before in
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/837456
A few, I tried English, German, Russian and Greek. I can't imagine how
it could depend on the keymap, though. The keys of Small's second layer
are basically the same for all.
I did eventually find a problem however that seems to occur only on this
tablet: the AltGr key in Compact layout doesn't
The tablet arrived last week, but it took me a couple of tries to get
plain Ubuntu 16.04 installed and the touch-screen working. It runs
pretty well now, maybe too good. I typed for half an hour into various
applications and didn't get a key stuck or excessive repeats happening.
However, I did
I've added a patch to the upstream bug report of bug #1572331 that
seems to solve the scaling issue. Waiting for feedback.
I then tested delaying Onboard's launch in unity-greeter:
https://code.launchpad.net/~marmuta/unity-greeter/delay-keyboard-until-settings-daemon-done
That indeed works
Thanks, I had fixed that in trunk already.
https://bazaar.launchpad.net/~onboard/onboard/trunk/revision/2113
AppIndicator is meant to be optional, that's why it is only a recommends
dependency.
** Changed in: onboard
Status: New => Fix Committed
** Changed in: onboard (Ubuntu)
** Also affects: onboard
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1574081
Title:
python traceback on start
Status in Onboard:
Fix
Ah, messed up the numbering. Here are the configure events again.
** Attachment added: "onboard-configure-events-corrected.txt"
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1562734/+attachment/4640804/+files/onboard-configure-events-corrected.txt
--
You received this bug
The keyboard seems to go below the screen, that's why we see a black
rectangle there. On my 1920x1200 screen, scaled to 960x600, it
apparently ends up at y=750.
See attachment for the configure events. Case 1) is the black rectangle
case. The values are all over the place. GdkEventConfigure
** Also affects: unity-greeter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1562734
Title:
Onboard keyboard shows black
The scaling issue seems to be a Gtk problem. I've opened a bug report here
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331
A workaround for that in Onboard wouldn't be pretty.
I have yet to figure out why the keyboard becomes all black, and not
just half the size.
--
You received
Public bug reported:
See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
Source code below.
What I expect to happen is that the GtkPlug has the same size as the GtkSocket.
What actually happens is that GtkPlug only covers a quarter of the area of the
GtkSocket.
Impact: Onboard
> the keyboard only covered the upper left quarter of the black box
Yes, that was the hint I needed, thanks. It's an issue with the window scaling
factor. I wasn't aware of unity-settings-daemon changing it. That should
explain the 500ms delay too. Onboard probably starts up with scaling-factor
Sorry for the delay. I want to help, but I'm not sure I can. I didn't
get answers to my questions in #2. Is this bug about visibly stuck keys
or not? If not, then everything else about visibly stuck keys is
unrelated and should go into a different bug report.
The log file shows the symptom but no
Thank you. The string is different in trunk, but the spelling errors
were still there. It may still change before the next release, but it
currently reads:
"AppIndicator (default) is recommended for broadest
compatibility. A middle click on the icon shows the keyboard. In KDE
Plasma a left click
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Importance: Undecided => Low
** Changed in: onboard
Status: New => Confirmed
** Changed in: onboard (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you
Thanks for the log. It's recreated on each reboot, so I only see the one
from the latest boot. The contents are slightly different from what I
get here, but I don't see anything really suspicious. Everything seems
to go as planned, and the fact that you can briefly see the keyboard now
only
Thank you both. There's no obvious error or traceback in the logs. I'd
still like to see Asvin's x-0-greeter.log, but at the moment it doesn't
look like Onboard crashes outright. Actually, there's little hint it is
being started at all, but this seems to be the normal case.
There is an
I've tried two old 16.04 partitions and a freshly installed one so far,
but wasn't able to reproduce the problem yet. Any additional information
you can provide is highly appreciated.
Asvin, X, please post the file "/var/log/lightdm/x-0-greeter.log". There's a
chance we will find an error
*** This bug is a duplicate of bug 1562734 ***
https://bugs.launchpad.net/bugs/1562734
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #1562734, so it is being marked as such. Please
This could be Onboard crashing on something. If so, there should be an
error message + traceback in /var/log/lightdm/.
Does this print anything interesting?
sudo su
zgrep -i onboard /var/log/lightdm/*
--
You received this bug notification because you are a member of Desktop
Packages, which is
Thank you, fixed in trunk.
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Status: New => Fix Committed
** Changed in: onboard (Ubuntu)
Status: New => Confirmed
** Changed in: onboard
Importance: Undecided => Low
--
You received
Hmm, I can't reproduce this here, neither with touch nor mouse pointer.
Does the "." key visibly get stuck in pressed state when it happens? Every time
you press it or only occasionally?
Debug output might help. Please run
$ killall onboard; onboard -dall &>onboard-debug-output.txt
make the
I have this in trunk now, see screen-shot. I think I feel more
comfortable with enabling dock-expand on landscape screens this way.
Comments welcome. The aspect limit can still be removed in onboard-
defaults.conf or gsettings and you'll get the old behavior.
For the other changes requested by
@Sebastien
> it works fine and looks better imho, even on a desktop
Hmm, that squished look...I don't know. There's an awful lot of mouse travel
necessary too. How about we put a limit on the aspect ratio and add
semi-transparent bars to the sides? It'll look similar to GNOME's keyboard,
only
The main reason the defaults are as they are, is that we haven't come up
with anything better that works equally well for all screen sizes.
Docking is great if there are fingers hovering over that general area of
the screen, but less so if there's a pointer that has to travel the
distance to the
Thanks again for bringing attention to this, Jacob. I've pushed a couple
of commits recently that I believe fix this bug. Find attached a screen
shot of the new Small layout for Russian. If you think there should be
any further changes, please let us know.
Here's what changed:
- There's an extra
How about adding э/Э to the long-press popups of Russian е/Е? Possibly
ӭ/Ӭ too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1534210
Title:
The Small layout for Onboard is missing
Thanks a lot. Shouldn't we add back the single quote somewhere, though?
I realize the regular Russian key map doesn't contain it, but the
phonetic flavors do. We could perhaps make room for it on the number
layer by moving the ampersand to the symbols layer.
** Also affects: onboard
@Luis Mascote, do you remember what you did to grow Onboard larger than
the screen? I'm trying, but can't seem to figure it out. AFAIK it can
happen when changing screen resolution/connected monitors, but I'm not
sure how to do it in regular usage. Is this on Compiz/Unity?
Concerning the resize
*** This bug is a duplicate of bug 1283491 ***
https://bugs.launchpad.net/bugs/1283491
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #1283491 so it is being marked as such. Any
I've tested onboard+onboard-data 1.0.1-0ubuntu1 from the -proposed repository
on a fresh install of current trusty and didn't find any regressions.
Login and unlocking the screen work as before. The keyboard is usable with
org.gnome.interface scaling-factor != 1 - I've tried 0.5, 1, 2 and 4 in
Thanks for the quick feedback, I think I need to look at the touch driver as
well.
You're welcome. I think you won't need to do this anymore.
Screens/kernel/drivers are probably fine.
I could eventually reproduce both issues in KWin and 1) was an Onboard
thing. Wrong order of initialization,
Great log file, thank you. Here's what happens:
...
12:43:42.951 Enter
12:43:42.952 TouchBegin (master, dev_id=2)
12:43:43.066 ButtonRelease (slave, dev_id=13)
12:43:43.067 TouchEnd (master, dev_id=2)
...
Two observations:
1) There are indeed touch events coming in, but only from the master
Public bug reported:
Customized Ubuntu 15.04, running KWin via an .xsession call. Using
Onboard for on-screen keyboard. The keyboard won't get focus unless I
tap on it twice (or unless I drag into the keyboard, and then tap it).
In my previous environment I used Compiz and didn't have this
Hmm, there's no touch visible in your log. The last line is an Enter event
(xi_type=7) from the master pointer (dev_id=2). A touch would start with
TouchBegin (xi_type=18) and would come from your touch screen slave device
(dev_id=13). Could you attach a longer log, up until the point when you
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1467723
Thanks for the bug report. Onboard's svg icon size was set too large and
lxpanel-indicator-applet-plugin doesn't seems to scale icons down. What
your image shows is basically the upper edge of a gigantic icon... Fixed
in trunk.
Francesco, when you find the time please prepare a new snapshot.
OK, I've opened bug #1461823 for this new issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1461221
Title:
undecorated onboard doesn't comply with compiz effects
Status in
Yes, current Onboard hides and shows the keyboard window wherever
possible, instead of minimizing/restoring it. IIRC it's been like this
since we switched to GTK-3 in 2012 and more out of necessity than by
design. Gnome-3/GTK-3 were trying to get rid of minimizing back then and
the required APIs
*** This bug is a duplicate of bug 1297692 ***
https://bugs.launchpad.net/bugs/1297692
Hi whitis, thanks for the detailed bug report. This particular bug has
been reported before as https://bugs.launchpad.net/onboard/+bug/1297692.
Glad you found the PPA and yes, newer versions of Onboard have
** Changed in: onboard
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1297692
Title:
Onboard not working with wacom driver
Status in
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have the right 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
** Also affects: at-spi2-atk (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-atk in Ubuntu.
https://bugs.launchpad.net/bugs/1432428
Title:
unity-panel-service crashes when
How can I get more debug info, or is the crash file of any help?
You should be able to file another bug report with your crash file:
$ ubuntu-bug /var/log/_usr_lib_unity_unity-panel-service.1000.crash
If that worked you may want to duplicate this bug to the new one.
From what I can tell the
Found it, the scaling was applied twice. Looking at your screen-shots
there was another issue with keys getting stuck on the main keyboard.
This shouldn't happen anymore either. Try it please and let me know how
it goes.
Francesco, another snapshot please. Thanks in advance.
** Changed in:
Thanks for the bug report. I can't reproduce it in Vivid, but will try
in Utopic later. 1.1.0~1908-0ppa1~utopic is slightly outdated too by
now. We should get you an updated snapshot just in case.
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Importance: Undecided = High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1421840
** Changed in: onboard
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1352549
Title:
layout reverts to default after inserting unicode character via
Multi-touch in Onboard is supposed to work as you described, Andreas. I
heard of people successfully using it in the wild too.
Please check if
Preferences-Keyboard-Advanced-Touch input
is set to multi-touch. This is the default.
Check if you own a Wacom touch-screen. Those are by default
Hi Anthony,
thanks for the reminder and apologies for the delay. We were actually about to
create the release last weekend, but it failed testing. Onboard doesn't rise
above Dash currently. We now believe this was caused by a recent change in
Unity, though, and it looks like there's not much
Is there a way to force that menu under onboard?
After doing some experimenting today, I'd say probably not in a useful way, at
least from Onboard's side. It is possible to raise the keyboard over the
Firefox drop-downs, trunk does that temporarily, but that isn't enough. They
keep receiving
Espen, do you have the screen keyboard setting enabled?
System settings - Universal Access - Typing - On Screen Keyboard
There are two lock screens since Ubuntu 14.04, IIRC, and that switch
toggles between them. If it's 'on' you should get the old lock screen
that has Onboard embedded.
--
You
Fixed in trunk. Grid with azerty has an 'm' key too now.
** Changed in: onboard
Status: New = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1293259
Title:
In
** Also affects: at-spi2-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: onboard
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
Seth and the other reporters, are these segfaults still happening? The
bug report and duplicates were for Ubuntu 13.10. There were no new
reports past Saucy.
** Changed in: onboard (Ubuntu)
Status: New = Incomplete
** Changed in: at-spi2-core (Ubuntu)
Status: New = Incomplete
--
** Also affects: at-spi2-atk (Ubuntu)
Importance: Undecided
Status: New
** Changed in: onboard
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-atk in Ubuntu.
1 - 100 of 256 matches
Mail list logo
