Renamed the issue to “python-augeas may fail to load libaugeas0 in
postinst script” because that proves to be the actual issue as shown in
the Debian bug report: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=944364
** Summary changed:
- dpkg fails to properly invoke ldconfig
+ python-augeas
This bug has now been filed upstream: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=944364
** Bug watch added: Debian Bug tracker #944364
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944364
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
Seen on: Ubuntu 18.04.3 LTS
dpkg version: 1.19.0.5ubuntu2.3 (also in 1.19.0.5ubuntu2.2)
Regression compared to dpkg 1.19.0.5ubuntu2.1
To reproduce this:
1. You need a package that depends on a library for running a script in its
postinst hook. For
After some further investigation, this problem is probably not Ubuntu-specific
but originated in upstream Debian and was cherry-picked as part of these
changes:
http://launchpadlibrarian.net/43334/dpkg_1.19.0.5ubuntu2.1_1.19.0.5ubuntu2.2.diff.gz
These changes include attempts to avoid
Public bug reported:
Seen on: Ubuntu 18.04.3 LTS
dpkg version: 1.19.0.5ubuntu2.3 (also in 1.19.0.5ubuntu2.2)
Regression compared to dpkg 1.19.0.5ubuntu2.1
To reproduce this:
1. You need a package that depends on a library for running a script in its
postinst hook. For instance, the attached
I also started noticing this recently. I tried a different mouse and it had the
same problem. I expected to have at least some way to tweak a low-level config
file to increase the debounce interval, but apparently it isn't implemented to
begin with.
I reckon this isn't only annoying for people
@Nick: it is based on Debian all right. Only they added stuff on top that
overrides pre-existing things. I'm in exactly the same boat as you.
Xmodmap still works and it can be run from the startup applications, but
something else overrides the keymap immediately after executing the startup
I also started experiencing this problem on 16.04, right after I had
enabled “turn screen off when inactive” in the system settings. I have
two identical Iiyama monitors, one of which is attached to the DVI port
of the integrated Intel graphics, the other to the HDMI port.
--
You received this
Still not fixed in 16.04. I just upgraded from Debian wheezy where one
nudge of the scroll wheel changed the alsamixer control by a consistent
5dB. This was bad already, because 5dB is too coarse. It feels like a
compromise between those who want to use the scroll wheel for fine
volume adjustments
