[Bug 1851675] Re: python-augeas may fail to load libaugeas0 in postinst script
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 may fail to load libaugeas0 in postinst script ** Package changed: dpkg (Ubuntu) => python-augeas (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851675 Title: python-augeas may fail to load libaugeas0 in postinst script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-augeas/+bug/1851675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851675] Re: dpkg fails to properly invoke ldconfig
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851675 Title: dpkg fails to properly invoke ldconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1851675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851675] Re: dpkg fails to properly invoke ldconfig
** 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 instance, the attached minimal package has `Depends:
python-augeas`, and tries to do “from augeas import Augeas” in a script invoked
from the postinst hook. (It does nothing else.)
2. Make sure the dependent library is not yet installed. In this example:
libaugeas0, which is a dependency of python-augeas.
3. apt-get install the package. For the attached exmple, you can use `dpkg
-i`, followed by `apt-get -f install`.
Result:
Setting up the-package (1.2.3ubuntu1-2-1) ...
Traceback (most recent call last):
File "/usr/lib/the-package/setup-package.py", line 3, in
from augeas import Augeas
File "/usr/lib/python2.7/dist-packages/augeas.py", line 78, in
class Augeas(object):
File "/usr/lib/python2.7/dist-packages/augeas.py", line 82, in Augeas
_libaugeas = _dlopen("augeas")
File "/usr/lib/python2.7/dist-packages/augeas.py", line 75, in _dlopen
raise ImportError("Unable to import lib%s!" % args[0])
ImportError: Unable to import libaugeas!
dpkg: error processing package the-package (--configure):
installed the-package package post-installation script subprocess returned
error exit status 1
Simply running apt-get -f install afterwards will succeed and run the
postinst script.
- The cause of this problem seems to be that any invocations of `ldconfig`
during the installation of the dependent libraries, do nothing at all.
- When adding `ldconfig -p >/tmp/ldconfig-output` to the postinst hook, one can
see that neither libaugeas0 nor any other libraries that were just installed,
are in the ldconfig cache at the moment the script is invoked.
+ The cause of this problem seems to be either that any invocations of
+ `ldconfig` during the installation of the dependent libraries, do
+ nothing at all, or rather that `ldconfig` is not invoked when it should
+ be.
+
+ When adding `ldconfig -p >/tmp/ldconfig-output` to the postinst hook,
+ one can see that neither libaugeas0 nor any other libraries that were
+ just installed, are in the ldconfig cache at the moment the script is
+ invoked.
Even when trying to perform an ugly workaround by adding an explicit
`ldconfig` invocation in the postinst script before running the python script,
it still fails.
Very curiously, calling `ldconfig -v >/dev/null` instead, somehow makes
ldconfig work. This is probably because ldconfig calls are actively blocked in
maintainer scripts, but adding the argument and redirect circumvents this
block...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851675
Title:
dpkg fails to properly invoke ldconfig
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1851675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851675] Re: dpkg fails to properly invoke ldconfig
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 trigger loops. One of the
triggers is ldconfig (see /var/lib/dpkg/info/libc-bin.triggers). It
seems that the changes have caused certain triggers to be postponed too
much. If a package states it depends (directly or indirectly) on a
library, one expects that this library is not just unpacked, but also
available at the moment the package enters its setup phase.
We have also tried to move python-augeas to Pre-Depends: instead in the
hopes of causing the ldconfig to be triggered before the postinst is
invoked, but this makes no difference.
** 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 instance, the attached minimal package has `Depends:
python-augeas`, and tries to do “from augeas import Augeas” in a script invoked
from the postinst hook. (It does nothing else.)
2. Make sure the dependent library is not yet installed. In this example:
libaugeas0, which is a dependency of python-augeas.
3. apt-get install the package. For the attached exmple, you can use `dpkg
-i`, followed by `apt-get -f install`.
Result:
Setting up the-package (1.2.3ubuntu1-2-1) ...
Traceback (most recent call last):
- File "/usr/lib/the-package/setup-package.py", line 3, in
- from augeas import Augeas
- File "/usr/lib/python2.7/dist-packages/augeas.py", line 78, in
- class Augeas(object):
- File "/usr/lib/python2.7/dist-packages/augeas.py", line 82, in Augeas
- _libaugeas = _dlopen("augeas")
- File "/usr/lib/python2.7/dist-packages/augeas.py", line 75, in _dlopen
- raise ImportError("Unable to import lib%s!" % args[0])
+ File "/usr/lib/the-package/setup-package.py", line 3, in
+ from augeas import Augeas
+ File "/usr/lib/python2.7/dist-packages/augeas.py", line 78, in
+ class Augeas(object):
+ File "/usr/lib/python2.7/dist-packages/augeas.py", line 82, in Augeas
+ _libaugeas = _dlopen("augeas")
+ File "/usr/lib/python2.7/dist-packages/augeas.py", line 75, in _dlopen
+ raise ImportError("Unable to import lib%s!" % args[0])
ImportError: Unable to import libaugeas!
dpkg: error processing package the-package (--configure):
- installed the-package package post-installation script subprocess returned
error exit status 1
+ installed the-package package post-installation script subprocess returned
error exit status 1
-
- Simply running apt-get -f install afterwards will succeed and run the
postinst script.
+ Simply running apt-get -f install afterwards will succeed and run the
+ postinst script.
The cause of this problem seems to be that any invocations of `ldconfig`
during the installation of the dependent libraries, do nothing at all.
When adding `ldconfig -p >/tmp/ldconfig-output` to the postinst hook, one can
see that neither libaugeas0 nor any other libraries that were just installed,
are in the ldconfig cache at the moment the script is invoked.
- Even when adding an explicit `ldconfig` in the postinst script before running
the python script, it still fails.
- Very curiously, calling `ldconfig -v >/dev/null` instead, somehow makes
ldconfig work. This seems to indicate that there is some problem with I/O
redirection, but for some reason the `-v` is also essential.
+
+ Even when trying to perform an ugly workaround by adding an explicit
`ldconfig` invocation in the postinst script before running the python script,
it still fails.
+ Very curiously, calling `ldconfig -v >/dev/null` instead, somehow makes
ldconfig work. This is probably because ldconfig calls are actively blocked in
maintainer scripts, but adding the argument and redirect circumvents this
block...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851675
Title:
dpkg fails to properly invoke ldconfig
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1851675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851675] [NEW] dpkg fails to properly invoke ldconfig
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 minimal package has `Depends:
python-augeas`, and tries to do “from augeas import Augeas” in a script invoked
from the postinst hook. (It does nothing else.)
2. Make sure the dependent library is not yet installed. In this example:
libaugeas0, which is a dependency of python-augeas.
3. apt-get install the package. For the attached exmple, you can use `dpkg -i`,
followed by `apt-get -f install`.
Result:
Setting up the-package (1.2.3ubuntu1-2-1) ...
Traceback (most recent call last):
File "/usr/lib/the-package/setup-package.py", line 3, in
from augeas import Augeas
File "/usr/lib/python2.7/dist-packages/augeas.py", line 78, in
class Augeas(object):
File "/usr/lib/python2.7/dist-packages/augeas.py", line 82, in Augeas
_libaugeas = _dlopen("augeas")
File "/usr/lib/python2.7/dist-packages/augeas.py", line 75, in _dlopen
raise ImportError("Unable to import lib%s!" % args[0])
ImportError: Unable to import libaugeas!
dpkg: error processing package the-package (--configure):
installed the-package package post-installation script subprocess returned
error exit status 1
Simply running apt-get -f install afterwards will succeed and run the postinst
script.
The cause of this problem seems to be that any invocations of `ldconfig` during
the installation of the dependent libraries, do nothing at all.
When adding `ldconfig -p >/tmp/ldconfig-output` to the postinst hook, one can
see that neither libaugeas0 nor any other libraries that were just installed,
are in the ldconfig cache at the moment the script is invoked.
Even when adding an explicit `ldconfig` in the postinst script before running
the python script, it still fails.
Very curiously, calling `ldconfig -v >/dev/null` instead, somehow makes
ldconfig work. This seems to indicate that there is some problem with I/O
redirection, but for some reason the `-v` is also essential.
** Affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Minimal example package that demonstrates the problem"
https://bugs.launchpad.net/bugs/1851675/+attachment/5303512/+files/the-package_1.2.3ubuntu1-2-1_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851675
Title:
dpkg fails to properly invoke ldconfig
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1851675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602809] Re: add Mouse Click Debounce Feature?
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 who didn't win the ‘perfect mouse’ lottery, but also for those with certain disabilities. If debounce is implemented for keyboards, then it only makes sense to implement it for any other input device with hardware buttons as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/602809 Title: add Mouse Click Debounce Feature? To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/602809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243642] Re: .Xmodmap not automatically loaded on start
@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 applications. So, I added a delay to my script, only to notice that this same something still overrides the keymap at semi-random moments. I think I'll try that hacky script from comment #6, which I was about to write by myself until I found this bug report… -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243642 Title: .Xmodmap not automatically loaded on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871133] Re: Volume Step not changeable in Unity and GNOME desktops
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 (which would require a step no larger than 2dB) and those who want to use it as a mute button (see Bug #551725). Unfortunately this compromise benefits nobody, because it falls in between the only two sensible use cases. The slider behavior in Xenial is worse. The amplitude follows what appears to be a quadratic function. This feels like someone lacking proper knowledge about audio had a go at fixing the previous volume slider that, being a bad compromise, didn't work for anyone. Step size varies depending on the slider position. I use sensitive earphones that are already quite loud with the slider near the leftmost position, where step sizes are about 8dB, which is awful. Anyone touching code that involves audio, should perhaps first read my rant about software volume controls: http://www.dr-lex.be/info-stuff/volumecontrols.html The position of the slider should map linearly to dB values, or in other words the volume multiplication factor must be an exponential function of slider position. It _will_ be unavoidable that for some users the slider will either have a ‘dead zone’ or a ‘too loud’ zone, because the maximum loudness of connected loudspeakers or headphones can vary wildly. Any interface that changes the volume by discrete increments like volume keys or the scroll wheel, must use fixed dB steps, in other words a fixed multiplication factor for linear amplitude. A good size for this step is 2 dB. To cater for those who only want to use the volume keys or scroll wheel to quickly make huge volume adjustments, the step size should indeed be configurable as this bug suggests. A drop-down menu with values of 1dB, 2dB, 3dB, and 6dB would be sufficient. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871133 Title: Volume Step not changeable in Unity and GNOME desktops To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
