** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Importance: Undecided => Medium
--
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/1195857
Ti
Testing with Onboard trunk this doesn't seem to happen anymore. There have been
a couple of multi-monitor fixes since Raring's 0.99.0~alpha1, this particular
one might be solved. Please try the latest version from our PPA.
https://launchpad.net/~onboard/+archive/ppa
If the problem persists plea
This sounds similar to bug #837456, with the new twist of having it happen on
modifier presses instead of all keys. Can you confirm the us layout is active
after the qwerty switch?
$ setxkbmap -query
$ setxkbmap -print
Does
$ setxkbmap fr
fix the problem temporarily?
(assuming French keyboard. C
Thanks for the bug report. Could you give us some more details under
what circumstances moving the keyboard isn't possible? Which desktop
environment/window manager are you using?
Note that all layouts included with Onboard come with a "move" button marked by
a four-way arrow. The default layout
*** This bug is a duplicate of bug 968044 ***
https://bugs.launchpad.net/bugs/968044
Thanks for the bug report, this particular problem has been reported
before, though. I'll mark it as a duplicate of bug #968044. This bug has
been fixed since, Onboard from version 0.97.1 is better protected
a
Fixed in trunk.
** Changed in: onboard
Status: Confirmed => 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/1082243
Title:
Needs high contrast icon
Status in Onb
** 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/1082243
Title:
Needs high contrast icon
Status in Onboard on-screen keyboard:
I've double checked, upgrades from Oneiric to Precise should have been
mostly safe. Oneiric started out with Onboard 0.95.1, but 0.96.1
arrived with SRU lp:880085 in oneiric-updates. Going through Onboard
0.95->0.96->0.97 doesn't trigger this bug. I guess that's the main
reason we haven't heard of
** Also affects: onboard
Importance: Undecided
Status: New
** 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/1123789
T
FYI, here's a backtrace of gsettings-data-convert from before the fix.
** Attachment added: "gsettings-data-convert_backtrace.txt"
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1123789/+attachment/3527573/+files/gsettings-data-convert_backtrace.txt
--
You received this bug notificat
Thanks for the confirmation, Jim. Onboard is (still) installed by
default, you didn't need to to anything to get it.
I've fixed the Onboard problem in the 0.97 branch. Sebastien, should we
ask for an SRU for Precise? Only the onboard.convert file changed.
--
You received this bug notification be
** Changed in: onboard (Ubuntu)
Status: Incomplete => 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/1123789
Title:
onboard.convert causes gsettings-data-convert to c
Jim, as a workaround try removing Onboard's pre-0.96 preferences. This
should stop the migration and allow Onboard to install.
gconftool-2 --recursive-unset /apps/onboard
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
Sebastien, I can reproduce the error in a Precise VM:
$ gconftool-2 -s /apps/onboard/horizontal_position -t int 10
$ sed -i "s/onboard.convert;//" ~/.local/share/gsettings-data-convert
$ gsettings-data-convert --file /usr/share/GConf/gsettings/onboard.convert
(gsettings-data-convert:25137): GLib-G
*** This bug is a duplicate of bug 1074448 ***
https://bugs.launchpad.net/bugs/1074448
Yes, we should. I'm not sure when it will happen, though. We're under pressure
to add user-facing features this cycle. Patches are welcome.
Marking this as a duplicate of bug #1074448 and I've opened new bu
I don't think they are duplicates. As I understand it, bug #1089462 is about
the dependency to libreoffice-gtk, which contains libreoffice's bridge to ATK.
No libreoffice-gtk, no auto-show.
This bug assumes libreoffice-gtk is installed, i.e. the prerequisite for
auto-show is there, but there's a
@Mitchell, would you mind to explain what kind of keyboard issues you
experienced before turning off multi-touch?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gksu in Ubuntu.
https://bugs.launchpad.net/bugs/421660
Title:
gksu's and
** 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 cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1070760
Title:
1st time running onboard with default theme is painfull
Ah, I should have mentioned libreoffice-gtk has to be installed. I'll add that
to the summary.
Note that manually showing Onboard pauses auto-show/hide and locks the keyboard
visible. It doesn't act on Writer's focus messages then. Manual hiding turns
auto-show back on.
** Description changed:
Still happens here on the 16GB Nexus 7 after re-running ubuntu-
nexus7-installer. Do I have to install images manually to get the
latest?
First thing I did after installation was
$ sudo apt-get install libreoffice-gtk libreoffice-writer
Then I dragged Writer to the launcher and started it.
Onboard
Public bug reported:
Typing into Writer generates an AT-SPI event for lost focus. Onboard
hides when that happens and has to be manually shown again to be able to
continue typing.
Steps to reproduce:
1. Start Onboard screen keyboard, auto-show enabled
2. Start Writer with an empty document
->
** Bug watch added: GNOME Bug Tracker #690244
https://bugzilla.gnome.org/show_bug.cgi?id=690244
** Also affects: gnome-screensaver via
https://bugzilla.gnome.org/show_bug.cgi?id=690244
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a mem
So no, Onboard isn't the cause. The unlock dialog's buttons still lock
up when Onboard isn't embedded into the screensaver.
The ultimate cause most likely lies within gnome-screensaver itself,
there is a lot of pointer grabbing going on during normal operation.
However, the trigger seems to be the
There's a crasher when the system font size changes with this version.
Fix is in trunk. Please wait if the package isn't on it's way yet.
--
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/1
Confirming, I've seen this too. However I'm not convinced yet this is
Onboard's doing. When it happens here, the whole screen becomes
unresponsive, including the buttons of the unlock dialog. This doesn't
happen when I plug Onboard into any other XEmbed socket. Not saying
Onboard is necessarily inn
Sean, Raring still has the old 0.98.2 release without docking and
without the touch enhancements. We're close to releasing a fresh (alpha)
version with improved docking. I'm busily ironing out some last minute
bugs.
** Changed in: onboard
Status: Confirmed => Fix Committed
--
You received
Jeff, thanks for the details.
I can confirm that In Chromium auto-show only works in the url-bar. Apparently
linux accessibility is still work in progress:
http://dev.chromium.org/developers/accessibility/linux-accessibility
There's also this open bug report for Orca:
https://code.google.com/p/ch
Kyle, I just tried again after updating, and with auto-show enabled it
happens here every time, on 12.10 amd64 and arm7l. Typing quickly, I can
get a couple of letters in until Onboard hides. If I wait after the
first one it happens as well.
To clarify, I believe, for the given input, Onboard does
The current default behavior is to always embed Onboard into the screen-
saver, but it will only actually show if either the keyboard is enabled
in system settings (org.gnome.desktop.a11y.applications.screen-keyboard-
enabled == true), or Onboard is currently running in the user session.
If you don
Well, we'd love to add this as a feature, but I'm not aware of anything
that would allow us to generally exempt Onboard from pointer grabs. If
this exists, I'd be interested to learn about it.
Back in GTK2 times Onboard used to have a toggle for "Password dialogs
as normal windows", which basicall
Scott, thank you. it works here after update and fixes the issues.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1070760
Title:
1st time running onboard with default theme is painfully
Since no one has mentioned it yet, gksu's grab can be turned off:
$ gconftool-2 --set /apps/gksu/disable-grab --type boolean true
or for a little gui run
$ gksu-properties
and select Grab mode: disable
You should then be able to type passwords with Onboard.
--
You received this bug notification
Scott,
could we get python3-virtkey updated to 0.62.0 in the Nexus 7 PPA too? This
would allow Onboard to show proper key labels for the number block and fix the
action of the NumLock key.
Raring has it already (0.62.0-0ubuntu1), though I've only now updated Onboard's
version requirements.
Built
Sure, I'll ask Francesco to make a snapshot of trunk, he'll post here
when it's ready. Feedback is very welcome. There's some new stuff too,
multi-touch support and rudimentary docking (still working on that).
A note of precaution: trunk rev. 1069 seems safe to install on the Nexus
7, I just did,
Good news, I've been able to squeeze some more performance out of Onboard, with
a lot of optimizations and a little bit of corner cutting. A warm start with
Compact+Ambiance is down to around 6 seconds. The other themes a second or so
less. Most typing has become more fluid too, the delays on mo
I've opened an upstream bug here:
https://bugs.freedesktop.org/show_bug.cgi?id=56891
CPU performance isn't that bad, almost a quarter of the i3 per thread. It's
apparently just cairo rendering to the xlib/xcb backends that takes the big
hit. I'm not sure why, either the intel driver on the i3 ac
** Attachment added: "The cairo trace, just starting up and closing Onboard
with the Ubuntu default theme."
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1070760/+attachment/3426968/+files/onboard.trace.lzma
--
You received this bug notification because you are a member of Desktop
Pac
I'll attach some cairo-perf results of Onboard starting up with the Ambiance
theme. The Nexus 7 takes a whopping >200x longer than the i3 laptop.
Single-threaded CPU performance just differs by a factor of some 4.5, and that
number would probably have been ok with Onboard. 200x though, that's no
Christopher, Onboard doesn't select any keyboard layouts. It only passively
reacts to system layout or group changes. Even if the reporter returns with
more information it is highly unlikely that anything can be done about it from
Onboard's side.
IMO, the most likely cause is bug #837456. Burli'
** 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/1053194
Title:
Onboard shouldn't show link to Universal Access Panel
I'll close this for upstream Onboard, the fix was released with Onboard
0.98.1.
** 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
That SIGKILL after SIGTERM was just a precaution. I felt the greeter
should be able to kill Onboard dead in case anything unforeseen happens.
Fixing this bug better not prevent you from logging in, I thought.
However, in my tests Onboard always shut down rapidly on SIGTERM. It's
not writing anythin
Try clicking more slowly. I just reproduced it by holding the button
down on the return key for a second. I have gnome-terminal auto-starting
in the session and it starts scrolling from all the enter presses right
after activating it.
And yes, without sending SIGTERM Onboard doesn't get the chance
*** This bug is a duplicate of bug 905686 ***
https://bugs.launchpad.net/bugs/905686
** This bug is no longer a duplicate of bug 954318
apport-gtk crashed
** This bug has been marked a duplicate of bug 905686
nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID:
Assertio
*** This bug is a duplicate of bug 905686 ***
https://bugs.launchpad.net/bugs/905686
I'll go ahead and mark this as a duplicate of the latest catch-all bug
for _XAllocID asserts.
** This bug has been marked a duplicate of bug 905686
nautilus assert failure: nautilus: ../../src/xcb_io.c:528
*** This bug is a duplicate of bug 905686 ***
https://bugs.launchpad.net/bugs/905686
** This bug is no longer a duplicate of bug 954318
apport-gtk crashed
** This bug has been marked a duplicate of bug 905686
nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID:
Assertio
*** This bug is a duplicate of bug 905686 ***
https://bugs.launchpad.net/bugs/905686
** This bug is no longer a duplicate of bug 954318
apport-gtk crashed
** This bug has been marked a duplicate of bug 905686
nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID:
Assertio
Apparently bug #1055698 can reproduce _XAllocID asserts reliably.
Onboard in unity-greeter is not exactly a minimal test case, but perhaps
this is still of some help.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
htt
*** This bug is a duplicate of bug 905686 ***
https://bugs.launchpad.net/bugs/905686
There is little we can do about this from Onboard's side, unfortunately.
Something with the interaction between libcairo and libx11 seems to
cause _XAllocID to fail. See bug #905686 and bug #507062.
However,
I think the layout preview is handled by libgnomekbd. Moving there.
** Package changed: onboard (Ubuntu) => libgnomekbd
--
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/1051169
Title:
Trunk now hides the button if gnome-control-center isn't in PATH. I'm
going to merge this into the 0.98 branch, so we'll have it in the 0.98.1
release.
** Changed in: onboard
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packa
Ok, I've opened bug #1053496 for adding the mousetweaks settings and
subscribed Gerd. Let's discuss it there.
--
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/1053194
Title:
Onboard sho
Yes, we should hide/disable that button, though perhaps only as a stop
gap measure for Quantal.
For later, I wonder if we shouldn't integrate the remaining mousetweaks
settings into Onboard's preferences. As far as I'm aware, desktops
without gnome-control-center have no easy way to configure the
Do I understand you right, are you trying to take the screen shot by
pressing Onboard's "Prnt" key? If so, then releasing the shift key (or
any latched modifier) is expected, this is just how Onboard works. You'd
have to lock the key, i.e. press it twice to make it stick.
However, you can catch On
Marking fix released as Onboard sets itself as transient for dash since
0.97.1. Updated and re-tested in 0.98.
** Changed in: onboard (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: unity (Ubuntu)
Status: Confirmed => Invalid
** Changed in: unity
Status: Confirmed
Confirming that this bug affects Onboard in Ubuntu 12.04 too. When auto-
show is enabled, Onboard doesn't pop up when renaming files in nautilus.
This seems fixed in Ubuntu 12.10 with nautilus 1:3.5.4-0ubuntu3, though,
at least for Onboard.
--
You received this bug notification because you are a
I have retested this with in gir1.2-gtk-3.0, 3.1.90-0ubuntu1 and found
it to be fixed.
** Changed in: gtk+3.0 (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: gtk+3.0 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: onboard
Status: New => Invalid
--
Yo
201 - 257 of 257 matches
Mail list logo
