[Bug 1210568] Re: Onboard does not take desktop theme
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 package manager, but might easily if you run from source. Trunk has a likely fix now. The system default theme is always considered, not only on first start. This only stops once the theme was manually changed in preferences. ** 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/1210568 Title: Onboard does not take desktop theme To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1210568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210575] Re: Right-click emulation of Onboard does not work
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 middle and right click conversion (for bug #1191098) that would probably sidestep your problem too. It has yet to be tested on touch-screens, though... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210575 Title: Right-click emulation of Onboard does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1210575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210568] Re: Onboard does not take desktop theme
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 org.onboard|grep "[ -]theme" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210568 Title: Onboard does not take desktop theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1210568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210568] Re: Onboard does not take desktop theme
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. https://bugs.launchpad.net/bugs/1210568 Title: Onboard does not take desktop theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1210568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210568] Re: Onboard does not take desktop theme
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 terminal onboard -dinfo and if you see anything other than the Nightshade colors post the terminal output here. @Franceso, yes I assumed Nightshade was the default theme now. I just installed from the PPA and couldn't reproduce the problem - got Nightshade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210568 Title: Onboard does not take desktop theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1210568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206122] Re: Onboard keymap lost at reboot
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 distributions. 'setxkbmap ' or 'sudo dpkg-reconfigure keyboard- configuration' used to help, but only for the current session. IIRC the latter worked because it called setxkbmap at configuration time, only once, though, not on reboot. Perhaps try calling setxkbmap or lxkeymap early, in ~/.xprofile, or even ~/.profile? > The command xmodmap -pke always matches the onboard keymap, > even when it's not the keymap I want. Good, they should be always in sync. Unfortunately it's largely out of our (Onboard's) hands then. X for some unknown reason decides to switch the key map and Onboard just reflects that change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206122 Title: Onboard keymap lost at reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1206122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1195857] Re: onboard crashed with SIGSEGV in PyObject_Call()
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 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/1195857 Title: onboard crashed with SIGSEGV in PyObject_Call() To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1195857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1195857] Re: onboard crashed with SIGSEGV in PyObject_Call()
** 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 crashed with SIGSEGV in PyObject_Call() To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1195857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189946] Re: onboard crashes in dock mode
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 longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189946 Title: onboard crashes in dock mode To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1189946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176425] Re: Shrinking workarea on secondary screen without 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 please post your monitor setup xrandr | grep " connected" and tell me which one of those is your primary monitor, i.e. the one Onboard is displayed on. ** Changed in: onboard Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176425 Title: Shrinking workarea on secondary screen without keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1176425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176819] Re: FR Keyboard layout not retained
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. Change "fr" to whatever keyboard map you actually use.) What version of OS and Onboard are you running? $ cat /etc/issue $ apt-cache policy onboard ** Changed in: onboard (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176819 Title: FR Keyboard layout not retained To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1176819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183735] Re: By default, Onboard keyboard cannot be moved through the screen
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 "Compact" has it in the sidebar to the right, just below the hide button. Make sure to turn the window decoration off when testing this, as the button will only show when window decoration is disabled. Either drag the button to move the keyboard around, or hold it down briefly to show enlarged touch handles. On a multi-touch capable touch screen you should be able to move the keyboard with a two (or more) finger drag gesture too. ** Changed in: onboard (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183735 Title: By default, Onboard keyboard cannot be moved through the screen To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1183735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920384] Re: onboard not starts, just blinking and turns off
*** 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 against common translation errors. ** This bug has been marked a duplicate of bug 968044 Onboard crashes with Russian locale -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920384 Title: onboard not starts, just blinking and turns off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/920384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082243] Re: Needs high contrast icon
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 this bug go to: https://bugs.launchpad.net/onboard/+bug/1082243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082243] Re: Needs high contrast icon
** 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: https://bugs.launchpad.net/onboard/+bug/1082243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123789] Re: onboard.convert causes gsettings-data-convert to crash
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 this problem before. Asking for a SRU seems less necessary for now. We're prepared anyway, though, just in case. -- 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 notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1123789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123789] Re: onboard.convert causes gsettings-data-convert to crash
** 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: onboard.convert causes gsettings-data-convert to crash To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1123789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123789] Re: onboard.convert causes gsettings-data-convert to crash
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1123789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123789] Re: onboard.convert causes gsettings-data-convert to crash
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1123789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123789] Re: onboard.convert causes gsettings-data-convert to crash
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1123789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123789] Re: onboard.convert causes gsettings-data-convert to crash
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. https://bugs.launchpad.net/bugs/1123789 Title: onboard.convert causes gsettings-data-convert to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1123789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123789] Re: onboard.convert causes gsettings-data-convert to crash
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-GIO-ERROR **: Settings schema 'apps.onboard' does not contain a key named 'x' Trace/breakpoint trap (core dumped) There's clearly a problem with Onboard 0.97.x. 'onboard.convert' references non-existent gsettings keys apps.onboard.x/y/width/height. I let this slip through testing apparently. The switch from gconf to gsettings came with Onboard 0.96, so this must have been a migration from <=0.95 to 0.97, skipping 0.96. If I'm not mistaken, upgrades from Oneiric and earlier to Precise had to be affected. I can't really explain why we haven't heard of this issue earlier. Onboard 0.98 and later don't seem to be affected. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1123789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105801] Re: Please support XDG base directory spec
*** 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 bug #1105843 for the second part of the summary. ** This bug has been marked a duplicate of bug 1074448 How about support XDG dir structure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105801 Title: Please support XDG base directory spec To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1105801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090960] Re: Typing into Writer hides Onboard screen keyboard
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 problem with the implementation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090960 Title: Typing into Writer hides Onboard screen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1090960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421660] Re: gksu's and gksudo's modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues
@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 modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/421660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070760] Re: 1st time running onboard with default theme is painfully slow
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1070760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090960] Re: Typing into Writer hides Onboard screen keyboard
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: 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 + 1. sudo apt-get install libreoffice-gtk libreoffice-writer + 2. Start Onboard screen keyboard, auto-show enabled + 3. Start Writer with an empty document -> keyboard shows, ok - 3. Type one character + 4. Type one character -> keyboard hides, when it should stay visible Ubuntu 13.04 LibreOffice 1:3.6.2~rc2-0ubuntu6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090960 Title: Typing into Writer hides Onboard screen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1090960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090960] Re: Typing into Writer hides Onboard screen keyboard
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 showed, I typed "w" and Onboard hid again. Same thing on a laptop with fully updated raring x86_64. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090960 Title: Typing into Writer hides Onboard screen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1090960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090960] [NEW] Typing into Writer hides Onboard screen keyboard
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 -> keyboard shows, ok 3. Type one character -> keyboard hides, when it should stay visible Ubuntu 13.04 LibreOffice 1:3.6.2~rc2-0ubuntu6 ** Affects: df-libreoffice Importance: Unknown Status: Unknown ** Affects: ubuntu-nexus7 Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Bug watch added: LibreOffice Bugzilla #58369 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=58369 ** Also affects: df-libreoffice via https://www.libreoffice.org/bugzilla/show_bug.cgi?id=58369 Importance: Unknown Status: Unknown ** Also affects: ubuntu-nexus7 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/1090960 Title: Typing into Writer hides Onboard screen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1090960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088495] Re: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088495 Title: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1088495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088495] Re: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen
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 way indicator-session locks the screen. I can reproduce the lockups pretty reliably, on desktop and Nexus 7, with: dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock; dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity They seem to disappear with adding a one second delay between those calls: dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock; sleep 1; dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity I'll link them both for now, gnome-screensaver and indicator-session. They'll be better able to sort this out. ** Also affects: indicator-session Importance: Undecided Status: New ** Also affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Changed in: onboard Status: New => Invalid ** Changed in: Ubuntu Raring Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088495 Title: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1088495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1089396] Re: New upstream releases available for Onboard and virtkey
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: New upstream releases available for Onboard and virtkey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1089396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088495] Re: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen
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 innocent, but I'd start debugging in gnome- screensaver. If I find the time I'll have a look. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088495 Title: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1088495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 960537] Re: Dash search box doesn't unhide Onboard on-screen keyboard
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 auto-show. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/960537 Title: Dash search box doesn't unhide Onboard on-screen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/960537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078554] Re: Onboard doesn't respect launcher icon size
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078554 Title: Onboard doesn't respect launcher icon size To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1078554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 936310] Re: Some applications don't 'auto-show' onboard
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/chromium/issues/detail?id=24585 Onboard's needs are just a small subset of Orca's, so once that bug is closed Onboard's auto-show should be supported as well. The qt-frontend of VirtualBox does well with auto-show on ubuntu 12.10. I've tested 4.1.18 from quantal's repos, as well as version 4.2 from your link. Both show/hide Onboard for all the text entries I tried. In theory all qt applications should be supported. The bridge to AT-SPI for the qt toolkit is qt-at-spi, which is installed by default on quantal. Could you check if it is there on precise? Auto-show with virtualized applications is unlikely to happen, I agree. VirtualBox would need to act as a proxy for the guest's AT-SPI calls for this to work. Dash on quantal seems to show Onboard sometimes, though not reliably and not for long. It seems there is progress, but the bug is still open: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/960537 ** Bug watch added: code.google.com/p/chromium/issues #24585 http://code.google.com/p/chromium/issues/detail?id=24585 ** Description changed: I'm testing onboard 0.97 in 2 different computers (one with oneiric: 0.97.0+tr756-0ppa~oneiric1, another one with precise alpha2: 0.97.0-0ubuntu1), both of them with auto-show when editing, show when unlocking, show tooltips, always on top. Most applications work fine with the new 'auto-show when editing' option, but I've found a few 'text applications' with wrong behaviour: - If onboard is hidden, they don't unhide (the right bevaviour is unhide) - If onboard was automatically unhided by another application , they hide onboard (the right behaviour is do nothing). Please note that in case of onboard was unhidden by a 'manual' clicking on onboard's icon, those applications don't hide onboard (right behaviour) I post all of wrong applications I've found in only one bug, if you prefer I can file different bugs. - opening the dash: this bug is different than #915250 , and this new bug is present even in unity-2d and with 'always on top' marked New bug reported here: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/960537 - wxmaxima: cells and text boxes - qtoctave: the editor - skype: the user/password window - tuxpaint: the option to write text in a image (in some other applications as gimp or xournal this feature works fine) - the right-click option to rename files in nautilus New bug reported here: https://bugzilla.gnome.org/show_bug.cgi?id=672498 - wine: tested with Adob Digital Editions - texmaker - fbreader - vlc (text boxes in preferences) + + - chromium-browser (all text entries except the url-bar) + Upstream bug report for Orca here: + https://code.google.com/p/chromium/issues/detail?id=24585 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/936310 Title: Some applications don't 'auto-show' onboard To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/936310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1077260] Re: When using software center search, onboard goes away until text box is reslected after entering 2 chars
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 react correctly. I think the software-center devs should have a look at this bug report and, if possible, try to keep the focus on the search box. Last time I didn't realize that software-center wasn't linked, so I'll add them now. ** Also affects: software-center (Ubuntu) Importance: Undecided Status: New ** Changed in: onboard Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1077260 Title: When using software center search, onboard goes away until text box is reslected after entering 2 chars To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1077260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993253] Re: Turning off on-screen keyboard leaves it on the locked screen
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't already use Onboard, it shouldn't actually show up in the screen-saver either. Barring bugs, the only unsupported case would be, if you did start Onboard from a launcher, kept using it, but still didn't want to see it in the screen-saver. The only recurse to that is to turn off screen- saver embedding in Onboard's preferences (org.onboard.xembed-onboard = false). Having control center turn off org.gnome.desktop.screensaver.embedded- keyboard-enabled wouldn't help all that much, because Onboard on startup keeps restoring those keys to something that allows it to show, until it is told not to do so. The dialog you saw is Onboard trying to restore them, but realizing the screen-saver keys have been changed by a third party and leaving the decision to the user. So my question is, is there a common use case, where you do want to use Onboard, but not have it show up in the lock screen? ** Changed in: onboard (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993253 Title: Turning off on-screen keyboard leaves it on the locked screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/993253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421660] Re: gksu's and gksudo's modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues
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 toggled the disable-grab key. This fell by the wayside with the switch to GTK3 and gsettings. We could possibly bring it back, though going by the age of this bug and duplicates, I'm not sure if we should. Is this still an issue today? -- 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 modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/421660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070760] Re: 1st time running onboard with default theme is painfully slow
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 manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1070760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421660] Re: gksu's and gksudo's modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues
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 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 modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/421660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070760] Re: 1st time running onboard with default theme is painfully slow
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 from source, it works alright with Onboard 0.99-tr1071-0nexus7.1 and current trunk on my Nexus 7. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1070760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070760] Re: 1st time running onboard with default theme is painfully slow
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, but for anything outside of releases it's probably wise to have some alternative keyboard input/auto-login ready. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1070760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070760] Re: 1st time running onboard with default theme is painfully slow
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 modifier presses and layer switches are shorter most of the time. The splash-screen like empty frame on startup is gone, Onboard just pops into existence when it's ready. I'll mark the Onboard part as committed, but more speed improvements will likely come over time. ** 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/1070760 Title: 1st time running onboard with default theme is painfully slow To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1070760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070760] Re: 1st time running onboard with default theme is painfully slow
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 accelerates cairo really well or the tegra driver does extremely poorly. The weird thing is, cairo rendering to image backends is almost 10 times faster than to the x backends. I would try and exploit this to speed up Onboard, but then it would be the reverse on intel... Perhaps we need something closer to OpenGL for rendering, that's where the Tegra shines. I'm experimenting with a clutter right now ** Bug watch added: freedesktop.org Bugzilla #56891 https://bugs.freedesktop.org/show_bug.cgi?id=56891 -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1070760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070760] Re: 1st time running onboard with default theme is painfully slow
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070760 Title: 1st time running onboard with default theme is painfully slow To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1070760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070760] Re: 1st time running onboard with default theme is painfully slow
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 nothing we can make up for. Adding cairo to the list. ** Attachment added: "cairo_trace_onboard_ambiance.txt" https://bugs.launchpad.net/ubuntu-nexus7/+bug/1070760/+attachment/3426964/+files/cairo_trace_onboard_ambiance.txt ** Also affects: cairo (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/1070760 Title: 1st time running onboard with default theme is painfully slow To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1070760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 934460] Re: Onboard always starts with english layout
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's hints in bug #920030 are a perfect fit for the symptoms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/934460 Title: Onboard always starts with english layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/934460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053194] Re: Onboard shouldn't show link to Universal Access Panel if gnome-control-center isn't installed
** 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- control-center isn't installed To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1053194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879942] Re: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard
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 Title: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/879942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978430] Re: "Enter" hangs when using it entering password with onboard in lightdm
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 anything to disk then either. The only times the branched greeter got to actually send SIGKILL was when I deliberately added a delay to Onboard's SIGTERM handler for testing. -- 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" hangs when using it entering password with onboard in lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/978430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978430] Re: "Enter" hangs when using it entering password with onboard in lightdm
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 to clean up and release pressed keys. The linked branch does that and in case anything gets stuck it sends a SIGKILL too for good measure. That was just a suggestion, but perhaps you can re-use some of the pieces. Another option may be to make the greeter log in on key release instead of key press when hitting return. Onboard wouldn't have to release any keys that way. I felt that was a more invasive change, though, so I haven't suggested it. -- 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" hangs when using it entering password with onboard in lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/978430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954318] Re: apport-gtk crashed
*** 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: _XAllocID: Assertion `ret != inval_id' failed. ** 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/954318 Title: apport-gtk crashed To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/954318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966076] Re: onboard crashed with SIGABRT in raise()
*** 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: Assertion `ret != inval_id' failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966076 Title: onboard crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/966076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984374] Re: onboard crashed with SIGABRT in raise()
*** 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: Assertion `ret != inval_id' failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984374 Title: onboard crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/984374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1038675] Re: onboard crashed with SIGABRT in raise()
*** 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: Assertion `ret != inval_id' failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1038675 Title: onboard crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1038675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
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. https://bugs.launchpad.net/bugs/905686 Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/905686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055698] Re: onboard assert failure: python3: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
*** 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, the fact that you can reproduce the failure reliably may be of interest. Perhaps this can be a test case to finally figure out the cause. I was so far unable to reproduce this here, though, but these asserts seem more common on i386 systems like yours (see bug #954318) and I'm testing on x86_64. I'll mark this as a duplicate of bug #905686 for now. ** This bug has been marked a duplicate of bug 905686 nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055698 Title: onboard assert failure: python3: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-greeter/+bug/1055698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1051169] Re: Keyborad Layout Chart has missing keys on NEO2 layout
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 Chart has missing keys on NEO2 layout To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/1051169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053194] Re: Onboard shouldn't show link to Universal Access Panel if gnome-control-center isn't installed
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053194 Title: Onboard shouldn't show link to Universal Access Panel if gnome- control-center isn't installed To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1053194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053194] Re: Onboard shouldn't show link to Universal Access Panel if gnome-control-center isn't installed
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 link to Universal Access Panel if gnome- control-center isn't installed To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1053194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053194] Re: Onboard shouldn't show link to Universal Access Panel if gnome-control-center isn't installed
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 hover click delay. Also, if there were alternative configuration GUIs, we would have to maintain detecting them and presenting the right button. There would be two new sliders for delay and motion threshold added to preferences. In return, the button to open g-c-c would go and we could restart the discussion about removing the second checkbox "enable hc window on exit". Ideally the number of widgets wouldn't change (ignoring labels). ** Changed in: onboard (Ubuntu) Status: New => Confirmed ** Also affects: onboard Importance: Undecided Status: New ** 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/1053194 Title: Onboard shouldn't show link to Universal Access Panel if gnome- control-center isn't installed To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1053194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036543] Re: screen shot from the onboard keyboard layout shift state in Ubuntu 12.04 not possible
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 Onboard in any state by taking a delayed screen shot. Run the "Screenshot" application, set "Grab after a delay of" to 10 seconds, click "Take Screenshot", adjust Onboard to your liking and wait. The same from the command line would be "gnome-screenshot -d 10". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036543 Title: screen shot from the onboard keyboard layout shift state in Ubuntu 12.04 not possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1036543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041303] Re: Feature freeze exception request: Plz update Onboard to 0.98.0 targeted at quantal
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 Ubuntu. https://bugs.launchpad.net/bugs/1041303 Title: Feature freeze exception request: Plz update Onboard to 0.98.0 targeted at quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1041303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986843] Re: Onboard randomly sets as default in lock screen
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. https://bugs.launchpad.net/bugs/986843 Title: Onboard randomly sets as default in lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/986843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879942] Re: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879942 Title: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/879942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879942] Re: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard
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 there a clean way to opt out of restarting at termination? I can see rate limiting in the gnome-session source, but must have missed a clear way to end restarts. > Maybe the GNOME developers would consider allowing alternate > screen keyboards since their built-in keyboard is very lacking. Getting GMOME to support alternative osks may not be easy. As I understand it, the Activities view is inaccessible to portable keyboards, so only shell extensions can fully replace the built-in keyboard. It's either GNOME Shell only or the rest of the world. That's a sad state of affairs IMO, and it isn't only an obstacle for Onboard, but hurts a whole eco-system of brilliant input devices like Dasher and Cellwriter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879942 Title: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/879942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879942] Re: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard
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 right, are you asking to lock Onboard out of GNOME Shell entirely? Me thinks a solution should tackle the auto-start problem, rather than outright ban $ALTERNATIVE-OSK. I'm open to suggestions, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879942 Title: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/879942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041303] Re: Feature freeze exception request: Plz update Onboard to 0.98.0 targeted at quantal
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 incentive for us to test and release late, in order to catch as many of the platform changes as possible. The straw that broke the camels back this time was not having an installable daily live at hand for installation testing (passed eventually): https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/988811 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041303 Title: Feature freeze exception request: Plz update Onboard to 0.98.0 targeted at quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1041303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041303] Re: Feature freeze exception request: Plz update Onboard to 0.98.0 targeted at quantal
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 compatible with Quantal's libdconf1 (migration of preferences) - moved its gsettings path from apps.onboard to org.onboard, as requested (LP: #982699) - stacks on top of Unity Dash again (Dash window name changed) There aren't many new features this time, the most notable perhaps being support for key shadows and dwell-enabling the floating icon. Most work has concentrated on Word Prediction, which isn't ready for widespread release yet. The usual number of assorted bug fixes and enhancements include better multi-monitor support, better working "Menu" and "Super" keys and keeping Onboard on top of full-screen windows (force-to-top mode in Unity only). Testing was done in Unity, GNOME Shell and GNOME Classic, but no more in Unity-2d, since it was dropped from Quantal recently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041303 Title: Feature freeze exception request: Plz update Onboard to 0.98.0 targeted at quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1041303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900191] Re: Pressing Super key does not reveal Unity Dash
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 super key press and release. I haven't found a way to achieve that duration without disabling the sticky key feature and we need sticky keys to allow for entering Super key combinations. ** 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/900191 Title: Pressing Super key does not reveal Unity Dash To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/900191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999155] Re: Onboard crashes due to mixup in Catalan Translation
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999155 Title: Onboard crashes due to mixup in Catalan Translation To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/999155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918749] Re: SRU oneiric: New release available: version 0.96.2
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/918749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991318] Re: Onboard window is wider than the screen
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 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 about this bug go to: https://bugs.launchpad.net/onboard/+bug/991318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991318] Re: Onboard window is wider than the screen
** 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 about this bug go to: https://bugs.launchpad.net/onboard/+bug/991318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915250] Re: Onboard doesn't work with unity dash (but it works with unity-2d)
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 => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915250 Title: Onboard doesn't work with unity dash (but it works with unity-2d) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/915250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 916056] Re: Missing mouse buttons
** 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 to: https://bugs.launchpad.net/onboard/+bug/916056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954318] Re: apport-gtk crashed
** 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 go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/954318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954318] Re: apport-gtk crashed
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/954318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954318] Re: apport-gtk crashed
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 and this bug hasn't occurred here yet. Searching around, this bug is possibly a duplicate of Bug #507062, the stacktrace is slightly different though. I'll add libx11 to the list for now. -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/954318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035273] Re: [Precise] Accessible for rename text entry isn't marked "editable"
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035273 Title: [Precise] Accessible for rename text entry isn't marked "editable" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1035273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978430] Re: "Enter" hangs when using it entering password with onboard in lightdm
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" hangs when using it entering password with onboard in lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/978430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025031] Re: UnicodeEncodeError for unrecognized files with unicode filenames in pbuilder
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. Though, from what I found that seems cumbersome to do, I'd rather avoid it until it's really necessary. -- 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: https://bugs.launchpad.net/ubuntu/+source/python-distutils-extra/+bug/1025031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025031] Re: UnicodeEncodeError for unrecognized files with unicode filenames in pbuilder
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: UnicodeEncodeError for unrecognized files with unicode filenames in pbuilder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-distutils-extra/+bug/1025031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025031] Re: UnicodeEncodeError for unrecognized files with unicode filenames in pbuilder
-- 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: https://bugs.launchpad.net/ubuntu/+source/python-distutils-extra/+bug/1025031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025031] [NEW] UnicodeEncodeError for unrecognized files with unicode filenames in pbuilder
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 Onboard in pbuilder
fails:
make[1]: Entering directory `/tmp/buildd/onboard-0.97.0'
python3 setup.py clean -a
running clean
'build/lib.linux-x86_64-3.2' does not exist -- can't clean it
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.2' does not exist -- can't clean it
WARNING: the following files are not recognized by DistUtilsExtra.auto:
HACKING
Onboard/osk/osk_devices.c
Onboard/osk/osk_devices.h
Onboard/osk/osk_module.c
Onboard/osk/osk_module.h
Onboard/osk/osk_util.c
Onboard/osk/osk_util.h
Onboard/pypredict/README
Onboard/pypredict/attic/Makefile
Onboard/pypredict/attic/multilevel
Onboard/pypredict/attic/ngram-test
Onboard/pypredict/attic/randbench
Onboard/pypredict/attic/test-client
Onboard/pypredict/lm.cpython-32mu.so
Onboard/pypredict/lm/lm.cpp
Onboard/pypredict/lm/lm.h
Onboard/pypredict/lm/lm_dynamic.cpp
Onboard/pypredict/lm/lm_dynamic.h
Onboard/pypredict/lm/lm_dynamic_cached.h
Onboard/pypredict/lm/lm_dynamic_impl.h
Onboard/pypredict/lm/lm_dynamic_kn.h
Onboard/pypredict/lm/lm_merged.cpp
Onboard/pypredict/lm/lm_merged.h
Onboard/pypredict/lm/lm_python.cpp
Onboard/pypredict/lm/pool_allocator.cpp
Onboard/pypredict/tools/analyze
Onboard/pypredict/tools/entropy
Onboard/pypredict/tools/ksr
Onboard/pypredict/tools/optimize
Onboard/pypredict/tools/predict
Onboard/pypredict/tools/split_corpus
Onboard/pypredict/tools/train
corpora/de/Deutsches Leben der Gegenwart.txt
Traceback (most recent call last):
File "setup.py", line 221, in
cmdclass = {'test': TestCommand},
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 105, in
setup
print (' ' + f)
UnicodeEncodeError: 'ascii' codec can't encode characters in position 19-20:
ordinal not in range(128)
The file it fails to print is "corpora/de/Ein Stück Lebensgeschichte und
andere Erzählungen.txt"
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: python3-distutils-extra 2.34-1 [modified:
usr/lib/python3/dist-packages/DistUtilsExtra/auto.py]
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic x86_64
ApportVersion: 2.3-0ubuntu4
Architecture: amd64
Date: Sun Jul 15 22:01:43 2012
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, username)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: python-distutils-extra
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: python-distutils-extra (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug quantal running-unity
--
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:
https://bugs.launchpad.net/ubuntu/+source/python-distutils-extra/+bug/1025031/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025022] [NEW] UnicodeDecodeError with UTF-8 encoded extensionless script in pbuilder
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 pbuilder:
running build_i18n
Traceback (most recent call last):
File "setup.py", line 151, in
cmdclass = {'test': TestCommand},
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 100, in
setup
distutils.core.setup(**attrs)
File "/usr/lib/python3.2/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.2/distutils/dist.py", line 917, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.2/distutils/dist.py", line 936, in run_command
cmd_obj.run()
File "/usr/lib/python3.2/distutils/command/build.py", line 126, in run
self.run_command(cmd_name)
File "/usr/lib/python3.2/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.2/distutils/dist.py", line 936, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 624, in run
line = open(f).readline()
File "/usr/lib/python3.2/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 137:
ordinal not in range(128)
The offending character seems to be the (c) sign in this file:
http://bazaar.launchpad.net/~onboard/onboard/trunk/view/head:/onboard
Similar to bug #1017468 the reason is probably pbuilder setting LANG=C.
Buildiing with e.g. LANG=en_US.UTF-8 works fine.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: python3-distutils-extra 2.34-1
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic x86_64
ApportVersion: 2.3-0ubuntu4
Architecture: amd64
Date: Sun Jul 15 21:15:11 2012
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, username)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: python-distutils-extra
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: python-distutils-extra (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug quantal running-unity
--
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:
https://bugs.launchpad.net/ubuntu/+source/python-distutils-extra/+bug/1025022/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025022] Re: UnicodeDecodeError with UTF-8 encoded extensionless script in pbuilder
-- 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: https://bugs.launchpad.net/ubuntu/+source/python-distutils-extra/+bug/1025022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024374] Re: Wrong include path in libexttextcat.pc
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 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: https://bugs.launchpad.net/ubuntu/+source/libexttextcat/+bug/1024374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024374] Re: Wrong include path in libexttextcat.pc
-- 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: https://bugs.launchpad.net/ubuntu/+source/libexttextcat/+bug/1024374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024374] [NEW] Wrong include path in libexttextcat.pc
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/
Builds fail unless the pc file is patched manually.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libexttextcat0 3.2.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic x86_64
ApportVersion: 2.3-0ubuntu4
Architecture: amd64
Date: Fri Jul 13 14:18:57 2012
ProcEnviron:
TERM=xterm
PATH=(custom, username)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: libexttextcat
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: libexttextcat (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug quantal running-unity
--
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:
https://bugs.launchpad.net/ubuntu/+source/libexttextcat/+bug/1024374/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1017468] Re: UnicodeDecodeError with glade files in pbuilder
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 is fixed for Onboard. Thanks for the quick response. Unfortunately, without the above workaround, the build still fails in pbuilder. Different lines, but similar problems. I'll try to file bug reports later, but it boils down to any file read (auto.py:624) and print statement (auto.py:105 ) not being safe when run with LANG="C". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1017468 Title: UnicodeDecodeError with glade files in pbuilder To manage notifications about this bug go to: https://bugs.launchpad.net/python-distutils-extra/+bug/1017468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978430] Re: "Enter" hangs when using it entering password with onboard in lightdm
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 all kinds of havoc on the desktop. The effect is the same as if you forever held down the enter key on you physical keyboard. It might not always be reproducible, though. If the greeter takes just long enough to kill Onboard everything may be fine. I've seen it happen on Quantal not long ago though. Thanks for looking at those bug reports btw. :) -- 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" hangs when using it entering password with onboard in lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/978430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016661] Re: Onboard does not respect my keyboard layout
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 restart X (reboot), go to System Settings -> Keyboard Layout, remove all layouts and re-add them? That's just a stab in the dark, but I remember this having helped in the past. You don't need to update the description that often, btw.. Sometimes it helps to see the progression of a bug report. If you just add a new comment you can attach large logs instead of pasting them too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016661 Title: Onboard does not respect my keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1016661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016661] Re: Onboard does not respect my keyboard layout
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 setxkbmap -print xmodmap -pke Then try this and see if it coaxes Onboard into typing bépo: setxkbmap fr bepo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016661 Title: Onboard does not respect my keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1016661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016980] Re: onboard crashed with signal 5 in _XReply()
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 => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016980 Title: onboard crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1016980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016980] Re: onboard crashed with signal 5 in _XReply()
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016980 Title: onboard crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1016980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016661] Re: Entering password with Onboard when screen is locked does not work
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 you have problems typing those special characters anywhere else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016661 Title: Entering password with Onboard when screen is locked does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1016661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999111] Re: SRU: update to onboard 0.97.1 bugfix release (debian source supplied)
Ok, so I've talked this through with Francesco. What we'd like to do is to just suggest a (few) patch(es) for the Ubuntu source package instead. This would only cover the translation related crashes. I'll have to double check, but IIRC there have been two issues, a fix for Exception handlers like in bug #958385 and another one for common format exceptions like in above bug #1013279. The former was already added to the Ubuntu package by Micah Gersten some time ago. I'm going to suggest adding http://bazaar.launchpad.net/~onboard/onboard/0.97/revision/772 for the latter. For whoever needs it (or hates the opacity flickering), the full update is then available in Quantal and as usual in our PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999111 Title: SRU: update to onboard 0.97.1 bugfix release (debian source supplied) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/999111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999155] Re: Onboard crashes due to mixup in Catalan Translation
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. https://bugs.launchpad.net/bugs/999155 Title: Onboard crashes due to mixup in Catalan Translation To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/999155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
