[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
It seems I have to insist again: patch https://launchpadlibrarian.net/405256420/patch should definitely really really be applied. As explained in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1508146/comments/73 that script should really *not* pass --force to setupcon. There is no reason for that except that it was copy/pasted from the Debian installer, where it is needed due to the use of bterm. On Ubuntu it should really not be used. Can somebody at last apply that patch that has been waiting for 2 years? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Lucid: New Status in kbd source package in Lucid: New Status in xorg-server source package in Lucid: New Status in console-setup source package in Maverick: New Status in kbd source package in Maverick: New Status in xorg-server source package in Maverick: New Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Won't Fix Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Released Status in kbd source package in Bionic: Won't Fix Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Released Status in kbd source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Released Status in kbd source package in Disco: Won't Fix Status in linux source package in Disco: Won't Fix Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Fix Released Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (kbd) [Impact] * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. [Test case] * Verify that safe mode switches work and dangerous ones are skipped without -f. Please note that the test will temporarily break the system's keyboard and it is recommended to run the test in a VM. rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? The keyboard is in Unicode (UTF-8) mode 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in xlate (8-bit) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in some unknown mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in raw (scancode) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in raw (scancode) mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 [Regression Potential] * kbd_mode stops performing breaking mode switches and this may make scripts ineffective when trying to perform a breaking change. This is the intention of the change and the emitter error helps in finding the offending script. The following packages found to call kbd_mode directly: console-setup xinit console-cyrillic initramfs-tools dracut console-tools xview ubiquity's embedded c
[Touch-packages] [Bug 1882966] Re: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04
I guess this is due to the following change in at-spi2-atk: * Meson: don't hard-code shared_library (!19). which made meson emit a lot of new libraries in Requires.private of atk- bridge-2.0.pc, and thus the -dev package now has to add them in Depends. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1882966 Title: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04 Status in at-spi2-atk package in Ubuntu: Confirmed Bug description: The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter packages makes it impossible to build Orca Master in Ubuntu-MATE 20.04. Reproduction steps: 1. You need to have Ubuntu-MATE 20.04 with the latest updates; 2. Install the following packages: git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev libatspi2.0-dev libatk-bridge2.0-dev 3. Clone the Orca repository: git clone https://gitlab.gnome.org/GNOME/orca.git 4. Navigate to the cloned repository: cd orca 5. Run the command: ./autogen.sh The command output ends with the following lines: checking for ATKBRIDGE... no configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met: Package 'atk', required by 'atk-bridge-2.0', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS and ATKBRIDGE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are forcibly downgraded to version 2.34.1-3, this error disappears. Many thanks for fixing this issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1882966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
But scripts changing between scancode and ascii/unicode (such as for some terminal emulation, dosbox, etc.) would break. I'm not saying they are widespread, but I have seen this kind of use, and requiring such flag will suddenly break them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Confirmed Status in kbd source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same: $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
How will kbd_mode know whether it's safe or not? Adding a -f option to kbd_mode will at best break some *other* existing scripts, while this very script should really definitely *NOT* pass -f to setupcon. That is the nonsense which needs to be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Confirmed Status in kbd source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
That is when updating the console-setup package, yes. As mentioned on https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1508146/comments/73 that's because its config script passes --force to setupcon, it really shouldn't, as mentioned there -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Xorg can't do anything about intercepting Alt-key, it's the kernel which takes the shortcut away. Again, as mentioned on https://bugs.launchpad.net/ubuntu/+source /console-setup/+bug/520546/comments/66 « proposed fix: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch As mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146 , Ubuntu probably wants to apply the attached patch. » Can somebody with t he proper rights do something about this? That patch exists since months now... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 Is there really any reason why keyboard-configuration.postinst passes --force to setupcon? In Debian we do this in the Debian installer because it is running within a bterm and thus can't detect it's running on the Linux console. But we never do this for an installed system. Apparently Ubuntu took that code snipped and dropped the check for being running within the Debian installer, and thus erroneously run with --force when DISPLAY is empty (typically from unattended upgrades and such), with the resulting observed effects of this bug report. I guess Ubuntu wants to apply the attached patch ** Attachment added: "proposed fix" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+attachment/5227479/+files/patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in console-setup package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
As mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1508146 , Ubuntu probably wants to apply the attached patch. ** Attachment added: "proposed fix" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
>From the upstream policykit bug entry, it is actually a misuse of the policykit API from brltty. I have uploaded a fix in Debian's brltty 5.6-5. Ubuntu should definitely include the policykit-fix patch contained in that 5.6-5 version as an update to ubuntu 18.04, otherwise all blind users will have the issue, thus unable to use the graphical desktop. ** Package changed: policykit-1 (Ubuntu) => brltty (Ubuntu) ** Changed in: brltty (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in brltty package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
Yes, disabling that patch fixes the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
I can confirm the same issue on Debian: upgrading from version 0.105-20 to version 0.105-21 brings the same issue. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-1116 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
This is most probably due to the introduction of Fix-CVE-2018-1116 -Trusting-client-supplied-UID.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
This seems to be an issue within policykit itself. Printing the actual error shows: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: process with PID 12570 has been replaced >From reading the source code, it seems that policykit is checking the start time of the program and finds a mismatch. It happens that orca is run as a Python script, so I thought that might be due to the script startup procedure, but starting a C brlapi client gives the same issue. At any rate, really looks like not an issue in brltty itself. ** Package changed: brltty (Ubuntu) => policykit-1 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More hel
[Touch-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
Note: to reproduce the issue, one just needs to install an Ubuntu 18.04 system, start brltty by hand as root with: sudo brltty -b no then try to connect to it as normal logged-in user through brlapi: python3 >>> import brlapi >>> b = brlapi.Connection() which shouldn't raise an exception. Logs can be seen in /var/log/syslog (unfortunately the current package source code only prints errno instead of the GError). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp