I have yet another variant ready for testing. This one is really
experimental and not fully fleshed out, but give it a try. Make sure to
save what you are working on, there is a slight risk of the touch-screen
to become unresponsive (until reboot).
Update your branch (bzr pull), rebuild, close
Thank you, that helped. The clue was 'Default': '' in system-theme-
associations, which shouldn't have been empty.
What might have happened is that onboard-defaults.conf (system defaults)
didn't exist the very first time you started Onboard. This wouldn't
usually happen when it was installed via
Till, that was my question, so the Classic Onboard theme was only active
initially and selecting Nightshade in preferences made it stick. Now it
may be difficult to reproduce what happened, though.
Try this, exit Onboard and run
gsettings reset org.onboard schema-version
Then start it from
Good to hear. The problem may still exist for others, though. Would you be able
to try my suggestion in comment #7? Also, perhaps the output of
dconf dump /apps/onboard/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, I misunderstood. No, I don't need onboard -dinfo then.
So dconf migration isn't the cause, and gconf migration is gone from
trunk anyway. Follow system theme was broken in the past, but is
supposed to be fixed in your version.
One last try, what does this show:
gsettings list-recursively
Till, could you please run
xev | tee taps.txt
and tap like 5 times right in the middle of that xev window. Try to perform the
taps like you always do them when trying to use Onboard's right click.
Attach taps.txt here, maybe there's a clue in there.
I'm currently working on a replacement for the
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195857
Title:
onboard
I haven't been able to reproduce this bug myself, but trunk rev. 1526
probably fixes it anyway. Similar to bug #189946, the python thread
state wasn't set up properly. Saucy's Python 3.3.2 isn't as lenient as
previous versions and is likely is to crash in that case.
** Changed in: onboard
When it loses the key map, does Onboard switch to US English key labels?
Then this old bug here might be related:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/837456
Recent versions of Ubuntu seem no longer affected, but I keep hearing similar
issues with Ubuntu flavors and other
Fixed in trunk. Python thread state wasn't properly set up, and Python
3.3.2 added a recursion check that relied on it. The version mismatch
wasn't at fault.
** Changed in: onboard
Status: New = Fix Committed
** Also affects: ubuntu
Importance: Undecided
Status: New
** No
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.
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
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
Fixed in trunk.
** 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.
https://bugs.launchpad.net/bugs/1082243
Title:
Needs high contrast icon
To manage notifications about
** Changed in: onboard
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/1082243
Title:
Needs high contrast icon
To manage notifications about this bug go to:
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
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):
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: onboard (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123789
Title:
onboard.convert causes gsettings-data-convert to crash
To manage
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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123789
Title:
*** 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
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
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/421660
Title:
gksu's and gksudo's
** Changed in: onboard
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070760
Title:
1st time running onboard with default theme is painfully slow
To
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.
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
-
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
** 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089396
Title:
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
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
I can't tell what bug #1071508 is about, that's why I asked for more
information, plus marked it incomplete for Onboard. If I had to take a
guess, I'd say it's closer to a duplicate of bug #936310. I consider
that one to be the master report for application specific issues with
Onboard's
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:
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
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
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 basically
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
Scott, thank you. it works here after update and fixes the issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070760
Title:
1st time running onboard with default theme is painfully slow
To
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.
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
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
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
** 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 Ubuntu
Bugs,
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.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879942
** Changed in: onboard
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053194
Title:
Onboard shouldn't show link to Universal Access Panel if gnome-
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
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
*** 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,
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
*** 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:
*** 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:
*** 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:
*** 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:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051169
Title:
Keyborad Layout
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053194
Title:
Onboard shouldn't show
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 Ubuntu
Bugs,
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
The Ubuntu dconf fix isn't needed anymore. The change to libdconf1's API is
already part of v0.98. That was the initial commit:
http://bazaar.launchpad.net/~onboard/onboard/0.98/revision/876
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes zaaran, unfortunately that's the expected behavior after running
Onboard once in Precise, see bug #938302. This shouldn't happen anymore
starting with v0.97.1 (in Quantal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed in trunk, I believe.
http://bazaar.launchpad.net/~onboard/onboard/trunk/revision/946
X-GNOME-AutoRestart doesn't seem to be a problem.
** Changed in: onboard
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ok, I don't see a way around this either now. I'll try something like:
if is-auto-starting and is-gnome-shell then fail, basically a working
replacement for NotShowIn=GNOME;. Manually starting Onboard will then
stay possible, no matter the system state.
What about X-GNOME-AutoRestart=true, is
Jeremy, do you know why GNOME Shell GNOME Fallback share the same xdg-
desktop name? Is that something that's set in stone? Those DE's are
different enough, why are they lumped together under the same name?
NotShowIn=GNOME; would probably do the job if it wasn't for this.
Did I understand you
Thank you :)
Thanks for the reminder too, though I'd be easier for us to make the FF
deadline if the ground wasn't shifting under Onboard right around this
time. Maybe there should be phased freezes for platform/libraries (X,
GTK, Unity) and applications (Onboard, ...). Right now there is an
Francesco asked me to add to this FFE request, so here's my list of
reasons, why I believe current Onboard 0.97.1 should be superseded.
Onboard v0.98...
- uses Python 3 by default and drops all Python 2 dependencies (if not told
otherwise)
- is compatible with Quantal's Xinput 2.2 (scanner)
- is
Trunk has a fix for this now, pressing left or right Super reveals the
launcher. Opening Dash requires pressing Super+Tab.
With Super alone, opening the launcher (and not Dash) is the best I can do at
the moment. In order to open Dash, Unity apparently checks for a very short
duration between
** Changed in: onboard (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916056
Title:
Missing mouse buttons
To manage notifications about this bug go
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 =
** 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/991318
Title:
Onboard window is wider than the screen
To manage notifications
According to comment #6 this bug wasn't an issue anymore with trunk.
However an actual check if Onboard fits on screen was still missing.
I've added that now with commit 920.
** Changed in: onboard
Status: New = Fix Committed
** Changed in: onboard
Importance: Undecided = Low
--
You
Francesco, can we close this? Apparently this old SRU went nowhere.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/918749
Title:
SRU oneiric: New release available: version 0.96.2
To manage
Tested Onboard 0.97.0-0ubuntu4 proposed in Precise and didn't experience
any crashes with the Catalan translation. No warning in the console
either, so the Catalan translation seems to have been updated in the
meantime.
** Tags removed: verification-needed
** Tags added: verification-done
--
There is something about the interaction between libcairo2 and
libx11-xcb1 that causes _XAllocID to fail. I don't believe we can do
much about this from Onboard, unfortunately.
Notably, this report and all duplicates occurred on i386 systems. Our
development and testing is mainly done on x86_64
** Also affects: onboard
Importance: Undecided
Status: New
** No longer affects: onboard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954318
Title:
apport-gtk crashed
To manage
** Also affects: libx11 (Ubuntu)
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/954318
Title:
apport-gtk crashed
To manage notifications about this bug
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
Anything else I can do to help this bug move forward? I'd appreciate any
feedback on the linked branch, what should be improved?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978430
Title:
Enter
Thank you, that was quick. With p-d-e trunk the build runs through now, for
both Python 2 and 3.
You're right, but non-ASCII file names aren't actually handled during the build
yet, they just happen to be around. If that changes we probably have to
explicitly set the locale during (p)builds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025022
Title:
UnicodeDecodeError with UTF-8 encoded extensionless script in pbuilder
To manage notifications about this bug go to:
Public bug reported:
[Test case]
Install version 2.34.1
1. have a package with an extensionless python script with some UTF-8
characters using p3-d-e
2. run pdebuild
- crash
Another bug report, as promised. Building Onbord trunk for Python 3 with
python3-distutils-extra 2.34.1 still fails in
Public bug reported:
[Test case]
Install version 2.34.1
1. have an unrecognized file with UTF-8 characters in it's filename using p3-d-e
For example: $ touch Ein Stück Lebensgeschichte und andere Erzählungen.txt
2. run pdebuild
- crash
One more, building the word prediction branch of
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025031
Title:
UnicodeEncodeError for unrecognized files with unicode filenames in
pbuilder
To manage notifications about this bug go to:
Btw., is there a way to turn the listing of unrecognized files off?
Also, shouldn't files from C extensions not be recognized files?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025031
Title:
Precise:
Sorry, I can't really verify if this bug is fixed there, too many missing
dependencies. Onboard builds for Python 3 only on Quantal.
The Python 2 build, using python-distutils-extra, still works with
precise-proposed enabled in pbuilder.
Quantal:
Using python3-distutils-extra this bug
Public bug reported:
Hi, I'm trying to include textcat.h, but it isn't found at the path
provided by pkg-config.
There seems to be a bad include path in Quantal's libexttextcat.pc:
Cflags: -I${includedir}/libextextcat/
I guess it is supposed to be:
Cflags: -I${includedir}/libexttextcat/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024374
Title:
Wrong include path in libexttextcat.pc
To manage notifications about this bug go to:
I think so, took it from a quilt patch.. Thanks for the fast response.
** Patch added: fix-pk-config-include-path.patch
https://bugs.launchpad.net/ubuntu/+source/libexttextcat/+bug/1024374/+attachment/3222327/+files/fix-pk-config-include-path.patch
--
You received this bug notification
You'd need to press enter with Onboard to reproduce this. When enter is
clicked, Onboard fakes pressing enter down, then gets killed before it can send
the key-release. X thinks the key is still pressed down, key repeat sets it and
everything is spammed with n enter presses per second, wreaking
Thank you, this all looks very bépo to me. I can't spot anything wrong,
wonder what's going on. It doesn't seem to be directly caused by
Onboard's at least.
setxkbmap fr bepo isn't really a permanent workaround. You'd have to
run it again (or make it run) after reboot. Instead, could you please
Weird, Onboard showing a different layout than it types isn't supposed to
happen anymore.
When you switch between typing on a physical keyboard and Onboard, do you see
Onboard's key labels changing to a different layout?
Please run these in a terminal and attach the ouput:
setxkbmap -query
Confirming, as Francesco has seen this happening before. X reports
BadWindow in XGetWindowProperty.
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard (Ubuntu)
Status: New = Confirmed
** Changed in: onboard
Status: New = In Progress
--
Fixed in trunk, I believe. Needs more testing though, I still can't
reproduce the X errors here. Francesco, when you get the chance to test
trunk, please let me know how it goes.
** Changed in: onboard
Status: In Progress = Fix Committed
** Changed in: onboard
Importance: Undecided =
Thanks for the bug report. I wonder if this is somehow related to bug #872701.
There has just been an update for gtk+3.0. Could you check if you already have
version 3.4.2-0ubuntu0.3?
$ apt-cache policy libgtk-3-0
In the lock screen dialog, does Onboard show the correct key labels for Bépo?
Do
Closing for upstream Onboard as the fix has been released with Onboard
0.97.1, available in Ubuntu 12.10.
** Changed in: onboard
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
201 - 300 of 665 matches
Mail list logo
