[Desktop-packages] [Bug 2039374] Re: xbrlapi causes long delay in GUI login
> if there is an active IPv6 regular (non-loopback) interface with an IPv6 address and network connection, then connection attempts to ::1 seem to hang and timeout Probably it uses the default route to send packets to ::1, which is deemed not to receive any response. > I haven't seen any other daemons with issues from this. Maybe they are using IPv4 for loopback? Probably ** Description changed: - Ubuntu 22.04.3 LTS + Ubuntu 22.04.3 LTS xbrlapi 6.4-4ubuntu3 After logging in to the GUI, there is a delay of over 2 minutes before the desktop environment loads (screen will be black with a mouse cursor) This is caused by /etc/X11/Xsession.d/90xbrlapi The script runs xbrlapi, which hangs for 2 minutes or so, presumably because it is trying to connect to a BrlAPI server that doesn't exist on my machine. I guess this packages was installed by orca, because I did not directly install it myself and I don't need it. Did not happen before 22.04 Others have this issue: https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/2039374 Title: xbrlapi causes long delay in GUI login Status in brltty package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS xbrlapi 6.4-4ubuntu3 After logging in to the GUI, there is a delay of over 2 minutes before the desktop environment loads (screen will be black with a mouse cursor) This is caused by /etc/X11/Xsession.d/90xbrlapi The script runs xbrlapi, which hangs for 2 minutes or so, presumably because it is trying to connect to a BrlAPI server that doesn't exist on my machine. I guess this packages was installed by orca, because I did not directly install it myself and I don't need it. Did not happen before 22.04 Others have this issue: https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/2039374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039374] Re: xbrlapi causes long delay in GUI login
Ok, I better understand why this has never shown up in most situations.
> my system has functional IPV4 and IPV6
Well, it still behaves oddly on the ip6-localhost case:
> connect(3, {sa_family=AF_INET6, sin6_port=htons(4101),
sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "::1", _addr),
sin6_scope_id=0}, 28) = -1 ETIMEDOUT (Connection timed out)
That's really not supposed to time out, and rather just immediately
return a "connection refused". Do you have some firewall rules on the lo
interface? I'm surprised that this doesn't pose troubles to other
system-/session-wide daemons.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/2039374
Title:
xbrlapi causes long delay in GUI login
Status in brltty package in Ubuntu:
New
Bug description:
Ubuntu 22.04.3 LTS
xbrlapi 6.4-4ubuntu3
After logging in to the GUI, there is a delay of over 2 minutes before
the desktop environment loads (screen will be black with a mouse
cursor)
This is caused by /etc/X11/Xsession.d/90xbrlapi
The script runs xbrlapi, which hangs for 2 minutes or so, presumably
because it is trying to connect to a BrlAPI server that doesn't exist
on my machine.
I guess this packages was installed by orca, because I did not
directly install it myself and I don't need it.
Did not happen before 22.04
Others have this issue:
https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/2039374/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039374] Re: xbrlapi causes long delay in GUI login
This is very surprising: what xbrlapi tries to connect to by default is a local socket in /var/lib/BrlAPI/0 so that should be completely independent from TCP/IP networking configuration, and should be either succeeding or failing immediately. Just to be sure: Does /var/lib/BrlAPI/0 exist? Is brltty running on your system? If you have a brltty daemon running it'd be useful to check for its logs. Perhaps you can log into a text console and run strace on the stuck xbrlapi command: strace -p $(pidof xbrlapi) so we get to know what it is stuck on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/2039374 Title: xbrlapi causes long delay in GUI login Status in brltty package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS xbrlapi 6.4-4ubuntu3 After logging in to the GUI, there is a delay of over 2 minutes before the desktop environment loads (screen will be black with a mouse cursor) This is caused by /etc/X11/Xsession.d/90xbrlapi The script runs xbrlapi, which hangs for 2 minutes or so, presumably because it is trying to connect to a BrlAPI server that doesn't exist on my machine. I guess this packages was installed by orca, because I did not directly install it myself and I don't need it. Did not happen before 22.04 Others have this issue: https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/2039374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Concerning 1a86:7523, the udev rules file in ubuntu indeed seems to be
missing the manufacturer filter:
debian/brltty.udev.rules says:
ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm",
GOTO="brltty_usb_run"
while it should be:
ENV{PRODUCT}=="1a86/7523/*", ATTRS{idVendor}=="1a40", ATTRS{idProduct}=="0101",
ENV{BRLTTY_BRAILLE_DRIVER}="bm", GOTO="brltty_usb_run"
This needs to be fixed in the various ubuntu brltty versions, starting
from 6.4.
BTW, for 403/6001 I see there
Ubuntu disable those to avoid conflicts, https://launchpad.net/bugs/1958224
But the line with the manufacturer filter should *not* be disabled, it properly
filters-in the producer of the Braille devices.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
brltty claiming cp210x devices on 22.04
Status in brltty package in Ubuntu:
Fix Released
Status in brltty source package in Jammy:
Fix Released
Status in brltty package in Debian:
Confirmed
Bug description:
* Impact
The brltty udev rules are claiming generic devices IDs which makes
some other devices like Arduino cards not able to interact with the
serial port anymore
* Test Case
Try to use an Arduino over a cp210x or FTDI serial port, it should be
able to talk to the computer
- upgrades from focal/impish to the SRU version should have no
question and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated
- upgrades from brltty 6.4-4ubuntu2
1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is
connectect at the time of the upgrade it should prompt with the debconf question
1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should
be generated
1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not
installed
2. if no matching device is connected
there should be no debconf question nor
/etc/udev/rules.d/86-brltty-usbgeneric.rules generated
- installing brltty when it was not installed
no question and no config generated
* Regression potential
If the debconf logic is wrong users could be prompted with the
question when not needed or not prompted when they should. If the udev
rules was incorrect or wrongly installed it could lead to have brltty
not starting when it should
---
Distributor ID: Ubuntu
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
Codename: jammy
brltty: Installed: 6.4-2ubuntu1
brltty appears once again to be claiming cp210x devices with the
vendor/product ID of:
idVendor=10c4, idProduct=ea60
Example dmesg output:
999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60,
bcdDevice= 1.00
[ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
[ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs
[ 999.215978] usb 3-6.3: SerialNumber: 0005
[ 999.234070] usbcore: registered new interface driver usbserial_generic
[ 999.234081] usbserial: USB Serial support registered for generic
[ 999.235262] usbcore: registered new interface driver cp210x
[ 999.235272] usbserial: USB Serial support registered for cp210x
[ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected
[ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
[ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
[ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as
/devices/virtual/input/input42
[ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty'
sets config #1
[ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 999.995066] cp210x 3-6.3:1.0: device disconnected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
Hello,
beattie, le mar. 20 sept. 2022 15:21:36 -, a ecrit:
> can't find anything in the udev,
That's be in ./lib/udev/rules.d/85-brltty.rules, this line:
ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm",
GOTO="brltty_usb_run"
> I think somebody did not do their testing.
Not many people have a CH340/CH341-based adapter to notice the issue.
Samuel
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1990189
Title:
brlttty claiming CH341 usbtty device blocking access
Status in brltty package in Ubuntu:
New
Bug description:
While this problem seems to have been fixed for FTDI and CP210 based
devices CH340/CH341 based (and possibly other USB serial adapters) are
unusable except by brltty.
[139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using
xhci_hcd
[139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86,
idProduct=7523, bcdDevice= 2.63
[139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2,
SerialNumber=0
[139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
[139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
[139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
[139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as
/devices/virtual/input/input24
[139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while
'brltty' sets config #1
[139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected
from ttyUSB0
[139100.786136] ch341 1-2.1.2:1.0: device disconnected
[143917.740171] usb 1-2.1.2: USB disconnect, device number 17
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: brltty 6.4-4ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Sep 19 12:01:21 2022
InstallationDate: Installed on 2022-08-23 (27 days ago)
InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: brltty
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
The simple workaround is to remove the package, or remove the entry from the udev file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: New Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
Ok. That'd be tricky to filter. Fortunately with brltty 6.5 such generic entries are kept apart so that they can be packaged separately. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: New Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990189] [NEW] brlttty claiming CH341 usbtty device blocking access
Hello, beattie, le lun. 19 sept. 2022 19:07:54 -, a ecrit: > [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, > idProduct=7523, bcdDevice= 2.63 Could you run lsusb -v so we get more information on how the generic bridge announces itself? Samuel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: New Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
> it's a bit unclear to me which entries there should be considered 'generic USB IDs'? They are marked "Generic Identifier", that's 0403:6001 10C4:EA60 10C4:EA80 > I also don't understand why those rules are debian specific See the diff between ./debian/brltty-udeb.udev.rules and ./Autostart/Udev/device.rules.in Note that in debian we use the udev rules *only* inside the installer. The current strategy in Debian is that in the installer we use udev rules to autodetect braille devices. But in the installed system we don't: when the user installs brltty, the user means that they have a Braille device and want to probe it, whether it uses a generic USB ID or not, i.e. we always start brltty > How does upstream handle the devices? When brltty is started it just always probes all devices. Its udev rules file always starts brltty, be it generic IDs or not. > We should stop installing brltty by default going forward That would align with the way it happens in Debian yes. Ideally the udev rules would be split so that the non-generic pieces get always installed to start brltty, and the generic pieces are installed only when necessary. That's a matter of actually spending time on implementing it. > we aren't going to respin ISOs on old serie for such changes and that wouldn't be a solution for already installed systems... Yes, rather disable the generic udev rules. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
orca only suggests brltty, it's the *-desktop packages which seem to be recommending brltty. If Ubuntu really wants to install brltty by default, it should disable the udev entries for the generic USB IDs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
Yes, unfortunately there is no way to fix it in that case. The udev rules properly avoid starting brltty when the iManufacturer field is changed from FTDI to the actual manufacturer of the device, but not when it is left to FTDI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: New Status in brltty source package in Oneiric: Fix Released Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
> In this case, brltty appeared (or at least the device claim) after a dist-upgrade Ah, do you happen to have a log of that dist-upgrade, so we can determine what brought it in? > It still feels very bad form for a vendor device to use the default VID/PID of the underlying converter chip Yes. Unfortunately that's what they have done, those devices are out there, and people have already bought them (and they cost a lot of money) :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Debian is installing the brltty package only when brltty was used during installation. Brltty gets started during installation either through the udev rules, or started manually from the kernel command line. The finish-install script just checks out /var/run/brltty.pid to determine whether a brltty is running. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Yes, but it is meant to be so: the Seika Braille device is announced as such, so we have to recognize such devices in brltty, otherwise the Seika Braille devices would not work at all. The question is rather: why is brltty installed on your system? It is supposed to be installed only if you installed your system with a Braille device connected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950488] Re: brltty ftbfs in jammy
Ah, the patch is already in brltty 6.4 actually, so no change on the Debian side actually :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy Status in brltty package in Ubuntu: Confirmed Bug description: brltty ftbfs in jammy, new version in Debian unstable [...] config.status: executing build-configure commands configure: WARNING: unrecognized options: --without-viavoice dh_testdir /usr/bin/make -C build-py3.10/Bindings/Python make[1]: Entering directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make: *** [debian/rules:136: build-py3.10-stamp] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950488] Re: brltty ftbfs in jammy
Ok, thanks! The corresponding commit upstream is e6ed2372887ac0106db8854f70e9b2fdcadec74f, attached here, could somebody check that this fixes the build issue on Ubuntu? I'll then integrate the patch in Debian as well. ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+attachment/5541197/+files/patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy Status in brltty package in Ubuntu: Confirmed Bug description: brltty ftbfs in jammy, new version in Debian unstable [...] config.status: executing build-configure commands configure: WARNING: unrecognized options: --without-viavoice dh_testdir /usr/bin/make -C build-py3.10/Bindings/Python make[1]: Entering directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make: *** [debian/rules:136: build-py3.10-stamp] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950488] Re: brltty ftbfs in jammy
> it is probably newer python versions being stricter with the use of non existing options? The --without-viavoice is not passed to the python bindings, so that cannot be the problem. That said I have now dropped the option from debian/rules, thanks :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy Status in brltty package in Ubuntu: Confirmed Bug description: brltty ftbfs in jammy, new version in Debian unstable [...] config.status: executing build-configure commands configure: WARNING: unrecognized options: --without-viavoice dh_testdir /usr/bin/make -C build-py3.10/Bindings/Python make[1]: Entering directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make: *** [debian/rules:136: build-py3.10-stamp] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950488] Re: brltty ftbfs in jammy
Please provide the whole build log. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy Status in brltty package in Ubuntu: Confirmed Bug description: brltty ftbfs in jammy, new version in Debian unstable [...] config.status: executing build-configure commands configure: WARNING: unrecognized options: --without-viavoice dh_testdir /usr/bin/make -C build-py3.10/Bindings/Python make[1]: Entering directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make: *** [debian/rules:136: build-py3.10-stamp] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to xorg-server 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
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to xorg-server 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to xorg-server 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to xorg-server 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to xorg-server 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to mutter 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 571956] Re: sd_generic breaks speech-dispatchter
Charlie: do you have the espeak package installed? It is needed to have espeak-generic working -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/571956 Title: sd_generic breaks speech-dispatchter Status in Speech Dispatcher: New Status in speech-dispatcher package in Ubuntu: Triaged Bug description: Binary package hint: speech-dispatcher The Lucid version of speech-dispatcher running the sd_generic module interface currently breaks speech out from speechd. Steps to reproduce uncomment espeak generic from ~/.speech-dispatcher/speechd.conf restart speech-dispatcher run orca from the terminal and pick espeak generic from the voice engine list. Watch the terminal. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: speech-dispatcher 0.6.8~unofficial~rc2-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Fri Apr 30 01:06:22 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) ProcEnviron: PATH=(cusUser Name, no user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: speech-dispatcher To manage notifications about this bug go to: https://bugs.launchpad.net/speech-dispatcher/+bug/571956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
Well, this is not a real solution, we need to fix polkit, otherwise all users will have the same issue, and we don't want to make them all revert back to file-based authentication. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in brltty 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/brltty/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
lasakro, stu: which USB ID does your device have? (otherwise we can't know what to fix in brltty) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: Fix Released Status in brltty source package in Oneiric: Fix Released Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741070] Re: Please merge brltty (main) 5.5-4 from Debian unstable (main)
I don't know how ubuntu manages that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1741070 Title: Please merge brltty (main) 5.5-4 from Debian unstable (main) Status in brltty package in Ubuntu: Fix Committed Bug description: Dear Ubuntu team, BRLTTY 5.5 was published in April 2017. It comes with several fixes and support of new braille devices. Could it be possible to upload it for Ubuntu 18.04 ? Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1741070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
I have pushed the AT_SPI_BUS removal patch to branch https://code.launchpad.net/~samuel-thibault/lightdm-gtk-greeter/at-spi- bus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
Hello, Still now news on this and #1366534 ? This is really hurting users... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
Hello, Just to confirm that the approch proposed by Luke is sound. Removing the AT_SPI_BUS property would really be the safest for the user session: even if systemd doesn't manage to properly clean the at-spi dbus, at least the session isn't exposed to its existence. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664320] Re: xbrlapi loopback interface abuse
Hello, This was reported in debian http://bugs.debian.org/851623 , and that led to upstream fix https://github.com/brltty/brltty/commit/0a5341121ba8f4de24407ce2a4d5369dadf5d099 ** Bug watch added: Debian Bug tracker #851623 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851623 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1664320 Title: xbrlapi loopback interface abuse Status in brltty package in Ubuntu: New Bug description: Xbrlapi creates new TCP connections in port 4101 at loopback interface. These are closed instantly because there is no service listening at 4101 on the lo interface. Xbrlapi should not do that if there is no braille device. This might pose a security risk, but I have not verified it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xbrlapi 5.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 13 19:25:58 2017 InstallationDate: Installed on 2015-07-31 (562 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: brltty UpgradeStatus: Upgraded to yakkety on 2016-11-01 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1664320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579531] Re: openConnection: connect: No such file or directory
I have suggested a patch to Dave, upstream maintainer of brltty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1579531 Title: openConnection: connect: No such file or directory Status in brltty package in Ubuntu: Confirmed Bug description: 16.04 amd64. $HOME/.xsession-errors contains cryptic messages that do not indicate where they come from. They turn out to be harmless but it would be good if they at least were prefixed with the source. openConnection: connect: No such file or directory cannot connect to brltty at :0 They indicate the absence of a braille tty so how about: xbrlapi: Cannot find a Braille Teletype device xbrlapi: cannot connect to brltty at :0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1579531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567658] Re: ubuntuBSD support
I've commited it, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1567658 Title: ubuntuBSD support Status in brltty package in Ubuntu: New Bug description: Hi Please could you apply attached patch to make brltty installable on ubuntuBSD? It just needs to adjust the initramfs-tools dependency. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1567658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 935296] Re: java-atk-wrapper prevents java applications from starting
Hello, While I could reproduce the issue with java-atk-wrapper 0.30, I can not reproduce it with java-atk-wrapper 0.33. I had reported the issue on https://bugzilla.gnome.org/show_bug.cgi?id=698095 , and it was reported as fixed. Perhaps it is the time to consider re-enabling accessibility in /etc/java-7-openjdk/accessibility.properties ? (wily has java-atk- wrapper 0.33) Samuel ** Bug watch added: GNOME Bug Tracker #698095 https://bugzilla.gnome.org/show_bug.cgi?id=698095 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/935296 Title: java-atk-wrapper prevents java applications from starting Status in java-atk-wrapper package in Ubuntu: Confirmed Status in openjdk-6 package in Ubuntu: Fix Released Status in openjdk-7 package in Ubuntu: Fix Released Status in java-atk-wrapper source package in Precise: Confirmed Status in openjdk-6 source package in Precise: Triaged Status in openjdk-7 source package in Precise: Triaged Status in java-atk-wrapper package in Debian: Fix Released Bug description: default java at command line is still java6. invoke java from command line, and minecraft fails to start, usually with no message, but there is some variety. Most usual: charles@basquette:~/Desktop$ java -jar ./minecraft.jar Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", ** WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-oSohfHsLYR: Connection refused charles@basquette:~/Desktop$ another case: charles@basquette:~/Desktop$ java -jar ./minecraft.jar Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", ** WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-oSohfHsLYR: Connection refused [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. java: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Aborted (core dumped) charles@basquette:~/Desktop$ another version, as suggested by: http://ubuntuforums.org/showthread.php?p=11696963 is to invoke as root, yielding: root@basquette:/home/charles/Desktop# java -jar ./minecraft.jar Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", ** WARNING **: Unable to create Ubuntu Menu Proxy: The connection is closed ** WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-oSohfHsLYR: Connection refused java.io.FileNotFoundException: /root/.minecraft/lastlogin (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:137) at net.minecraft.LoginForm.readUsername(LoginForm.java:131) at net.minecraft.LoginForm.(LoginForm.java:76) at net.minecraft.LauncherFrame.(LauncherFrame.java:30) at net.minecraft.LauncherFrame.main(LauncherFrame.java:158) at net.minecraft.MinecraftLauncher.main(MinecraftLauncher.java:13) ^Croot@basquette:/home/charles/Desktop# exit minecraft is stock .jar unchanged for several weeks/months ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: openjdk-6-jre 6b24-1.11.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Sat Feb 18 09:39:32 2012 InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openjdk-6 UpgradeStatus: Upgraded to precise on 2012-01-15 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/935296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365054] Re: package brltty 5.0-2ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Well, yes, brltty needs mountkernfs, like a lot of software actually. Having it disabled seems the culprit here, not brltty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1365054 Title: package brltty 5.0-2ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in “brltty” package in Ubuntu: New Bug description: /usr/bin/dpkg returned an error code (1) upgrade from 14.04 to 14.10 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: brltty 5.0-2ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 AptOrdering: brltty: Configure Architecture: i386 Date: Wed Sep 3 12:06:13 2014 DuplicateSignature: package:brltty:5.0-2ubuntu3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-08-13 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) SourcePackage: brltty Title: package brltty 5.0-2ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-09-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1365054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1013881]
I too believe that Andreas' proposal is the right one. It permits people who really want the extra 5th level to be able to easily get it, while not breaking the 99% usual usage. Just for the record, I had not seen the linuxfr discussion. I guess mostly only people who would want the extra 5th level did realize that it would steal the right control key. If a discussion happened on are people fine with making the right control key the 5th level modifier by *default*, the result would be quite different, I believe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard Status in central project for keyboard configuration: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Released Bug description: Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key of the keyboard has ceased to work. The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 2.5-1ubuntu1.2. If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu9 Architecture: amd64 Date: Sat Jun 16 00:16:09 2012 Dependencies: DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader MachineType: LENOVO 4243E69 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243E69 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4243E69 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-0ubuntu1~xup1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 221112]
I too believe that Andreas' proposal is the right one. It permits people who really want the extra 5th level to be able to easily get it, while not breaking the 99% usual usage. Just for the record, I had not seen the linuxfr discussion. I guess mostly only people who would want the extra 5th level did realize that it would steal the right control key. If a discussion happened on are people fine with making the right control key the 5th level modifier by *default*, the result would be quite different, I believe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard Status in libgnomekbd: Confirmed Status in Listen, a Music player and management: Confirmed Status in Quod Libet is a GTK+-based audio player written in Python.: Unknown Status in The Rhythmbox Music Management Application: Confirmed Status in SciTE - A free source code editor for Win32 and X: New Status in central project for keyboard configuration: Confirmed Status in “quodlibet” package in Ubuntu: Invalid Status in “rhythmbox” package in Ubuntu: Fix Released Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “xkeyboard-config” source package in Precise: Triaged Bug description: [Impact] In the fr(oss) keymap, both space and Ctrl + space return the same XLookupString, which prevents space from being used in some applications. This had been fixed in lucid and maverick, but the patch appears to have been misplaced during the (rather major) update from 1.8 to 2.1, thus the reports of it regressing in comments #135 and #141, as well as dupe bug #938671. [Development Fix] Patch 128_fix_oss_ctrl_space_accelerator.patch fixed this problem in lucid and maverick, but was dropped in natty when we updated to upstream xkeyboard-config 2.1. However, the patch was also sent upstream and accepted there. So for quantal a cherrypick of that commit was backported. [Stable Fix] Since currently quantal is shipping the same xkeyboard-config version as precise, we can carry the same patch there as well. [Test Case] 1. Set keyboard to fr(oss). (Note due to unrelated bug, you need to do this in your /etc/defaults/keyboard config file.) 2. Start rhythmbox 3. Do a song search 4. Type in a search term that includes a space character Broken Behavior: Space triggers the play/pause function in rhythmbox Fixed Behavior: A space character is inserted [Regression Potential] The patch is one we carried in lucid and maverick (when rhythmbox was the default music player IIRC), and has been upstream for a while. So I think it is a safe change. Actually, I'm surprised there have not been more complaints about it lately. But during the interim we'd switched to banshee so perhaps users didn't notice it. [Original Report] I tried to search for The Do in the search bar, but the space bar didn't write a space. Instead, it played the currently selected song (space is the shortcut for playing/pausing the song). I've just installed the last Hardy release candidate. ProblemType: Bug Architecture: i386 Date: Wed Apr 23 19:30:12 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/rhythmbox NonfreeKernelModules: nvidia Package: rhythmbox 0.11.5-0ubuntu6 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux 2.6.24-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1013881]
Hello, Until a solution is to be found, could 518c769d be reverted for now? Breaking the very standard behavior of right control in all applications (e.g. xterminals!!) is really not acceptable, compared to the few issues that the behavior has without it. Samuel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard Status in central project for keyboard configuration: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Released Bug description: Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key of the keyboard has ceased to work. The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 2.5-1ubuntu1.2. If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu9 Architecture: amd64 Date: Sat Jun 16 00:16:09 2012 Dependencies: DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader MachineType: LENOVO 4243E69 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243E69 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4243E69 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-0ubuntu1~xup1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 221112]
Hello, Until a solution is to be found, could 518c769d be reverted for now? Breaking the very standard behavior of right control in all applications (e.g. xterminals!!) is really not acceptable, compared to the few issues that the behavior has without it. Samuel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard Status in libgnomekbd: Confirmed Status in Listen, a Music player and management: Confirmed Status in Quod Libet is a GTK+-based audio player written in Python.: Unknown Status in The Rhythmbox Music Management Application: Confirmed Status in SciTE - A free source code editor for Win32 and X: New Status in central project for keyboard configuration: Confirmed Status in “quodlibet” package in Ubuntu: Invalid Status in “rhythmbox” package in Ubuntu: Fix Released Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “xkeyboard-config” source package in Precise: Triaged Bug description: [Impact] In the fr(oss) keymap, both space and Ctrl + space return the same XLookupString, which prevents space from being used in some applications. This had been fixed in lucid and maverick, but the patch appears to have been misplaced during the (rather major) update from 1.8 to 2.1, thus the reports of it regressing in comments #135 and #141, as well as dupe bug #938671. [Development Fix] Patch 128_fix_oss_ctrl_space_accelerator.patch fixed this problem in lucid and maverick, but was dropped in natty when we updated to upstream xkeyboard-config 2.1. However, the patch was also sent upstream and accepted there. So for quantal a cherrypick of that commit was backported. [Stable Fix] Since currently quantal is shipping the same xkeyboard-config version as precise, we can carry the same patch there as well. [Test Case] 1. Set keyboard to fr(oss). (Note due to unrelated bug, you need to do this in your /etc/defaults/keyboard config file.) 2. Start rhythmbox 3. Do a song search 4. Type in a search term that includes a space character Broken Behavior: Space triggers the play/pause function in rhythmbox Fixed Behavior: A space character is inserted [Regression Potential] The patch is one we carried in lucid and maverick (when rhythmbox was the default music player IIRC), and has been upstream for a while. So I think it is a safe change. Actually, I'm surprised there have not been more complaints about it lately. But during the interim we'd switched to banshee so perhaps users didn't notice it. [Original Report] I tried to search for The Do in the search bar, but the space bar didn't write a space. Instead, it played the currently selected song (space is the shortcut for playing/pausing the song). I've just installed the last Hardy release candidate. ProblemType: Bug Architecture: i386 Date: Wed Apr 23 19:30:12 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/rhythmbox NonfreeKernelModules: nvidia Package: rhythmbox 0.11.5-0ubuntu6 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux 2.6.24-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082679] Re: brlapi.OperationError.__str__ return bytes
This should get fixed by the next brltty version, 4.5, to be released very soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1082679 Title: brlapi.OperationError.__str__ return bytes Status in “brltty” package in Ubuntu: New Bug description: brlapi seems to be not fully python3 compatible. If brlapi raises a brlapi.OperationError and I want to print this error I get an TypeError, because the __str__ method returns the message as bytes, not as string. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: python3-brlapi 4.4-5ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Sat Nov 24 15:51:20 2012 InstallationDate: Installed on 2011-05-13 (560 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MarkForUpload: True SourcePackage: brltty UpgradeStatus: Upgraded to quantal on 2012-10-19 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1082679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1099309] [NEW] [Quantal and Raring] Brltty native braille support doesn't work with Orca
Attila Hammer, le Mon 14 Jan 2013 07:22:17 -, a écrit : In Ubuntu Quantal and Ubuntu Raring if I enabling Orca with braille support, the Orca's debug.out file I see following traceback error message: BrlTTY seems to have disappeared: Traceback (most recent call last): File /usr/lib/python3/dist-packages/orca/braille.py, line 1720, in _brlAPIKeyReader key = _brlAPI.readKey(False) File brlapi.pyx, line 535, in brlapi.Connection.readKey (brlapi.auto.c:6558) brlapi.OperationError: unprintable OperationError object If I remember right an oldest I opened thread with Brltty mailing list, this problem related the Python3 Brltty bindings. The python3 binding issue brings the unprintable part, but most probably not the error which triggered it. Does the user which runs orca have access to /etc/brlapi.key? Is the /etc/brlapi.key file not empty? Is the brltty daemon running? Samuel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1099309 Title: [Quantal and Raring] Brltty native braille support doesn't work with Orca Status in “brltty” package in Ubuntu: New Bug description: Dear Developers, In Ubuntu Quantal and Ubuntu Raring if I enabling Orca with braille support, the Orca's debug.out file I see following traceback error message: BrlTTY seems to have disappeared: Traceback (most recent call last): File /usr/lib/python3/dist-packages/orca/braille.py, line 1720, in _brlAPIKeyReader key = _brlAPI.readKey(False) File brlapi.pyx, line 535, in brlapi.Connection.readKey (brlapi.auto.c:6558) brlapi.OperationError: unprintable OperationError object If I remember right an oldest I opened thread with Brltty mailing list, this problem related the Python3 Brltty bindings. I attaching the Orca debug.out file. Attila ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: brltty 4.4-6ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Mon Jan 14 08:15:16 2013 InstallationDate: Installed on 2013-01-11 (2 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130111) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1099309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
