I would like to repeat that this is a regression in Ubuntu 22.04, it has
a fix released upstream and the patch applies cleanly if backported. So
it seems that this should be a low hanging fruit to fix and I would
really appreciate it if the fix could be shipped to Ubuntu 22.04. Thank
you very much
Thanks! Version 249.11-0ubuntu3.5 of systemd fixes this issue for me: I
rebooted the machine and the bind mount to the NFS mount was correctly
mounted automatically. Previously this had always failed.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You
A fix has been committed upstream now. Could this be backported to
Ubuntu?
I tested
https://gitlab.freedesktop.org/poppler/poppler/-/commit/a89c3c27e02e9c300aa667c966d91fdf787c7d0a
by cherry-picking it on top of poppler-22.02.0. Tt applies and compiles
cleanly and with it Evince on Ubuntu 22.04
The fix https://github.com/systemd/systemd/pull/24122 is now merged
upstream. The change should be easy to backport, is it possible that
this could be done for Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Somebody else has reported this upstream
(https://github.com/systemd/systemd/issues/24120) and a fix is being
developed as https://github.com/systemd/systemd/pull/24122.
** Bug watch added: github.com/systemd/systemd/issues #24120
https://github.com/systemd/systemd/issues/24120
** Also
I found out that the bug is actually in poppler and have reported a bug
upstream, where it is being worked on.
** Also affects: poppler (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/poppler/poppler/-/issues #1267
I agree that this is very inconvenient. For example, I have a system at
home that I leave unattended but I need it to reconnect automatically to
my wifi, because I need to access it from abroad. If there is a
disconnect and it can't reconnect immediately (e.g., because of a router
reboot), the
We experience this problem also.
$ ping -c 2 de.archive.ubuntu.com
PING ubuntu.mirror.tudos.de (141.30.13.20) 56(84) bytes of data.
64 bytes from c13020.dip.tu-dresden.de (141.30.13.20): icmp_seq=1 ttl=55
time=12.8 ms
64 bytes from c13020.dip.tu-dresden.de (141.30.13.20): icmp_seq=2 ttl=55
I cannot imagine how a missing password input field in the lock screen could be
related to an LDAP configuration issue on our side.
If the authentication would fail after entering the password, then yes, of
course this could be such a problem.
But a password field should always be shown by the
For auditing my PAM config, could you please tell me which PAM config the lock
screen uses
(i.e., which file in /etc/pam.d is used)?
So far I could not find any differences between them.
The LDAP config is in common-{auth,account}, which are included in most files
in this directory.
All these
We also have this problem on several machines, and I hope I can contribute to
getting it fixed.
Removing light-locker fixed the double unlock problem, but not this problem.
The machine is a fully up-to-date Ubuntu 14.04 with LDAP authentication.
The output of ls -l /sbin/unix_chkpwd is
11 matches
Mail list logo
