>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
I can confirm the same issue on Debian: upgrading from version 0.105-20
to version 0.105-21 brings the same issue.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-1116
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This is most probably due to the introduction of Fix-CVE-2018-1116
-Trusting-client-supplied-UID.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1782320
Title:
Yes, disabling that patch fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1782320
Title:
Braille display inoperable in GUI since polkit-update
Status
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
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.
*** 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
As mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146 , Ubuntu probably wants to apply the attached patch.
** Attachment added: "proposed fix"
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch
--
You received
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:
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
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
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
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
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
14 matches
Mail list logo
