After upgrade to Ubuntu version 20.4 the issue with the idle status
reporting by lightdm-greeter remains. This continues to have idle
setting of logind.conf ignored:
https://www.freedesktop.org/software/systemd/man/logind.conf.html
> Note that this requires that user sessions correctly report the
Lightdm shall never suspend the system itself. Instead it should
properly report idle status to systemd where a decision can be taken by
checking all relevant services, sessions and inhibitors.
In the past I have reported that idle suspend does not work while showing login
screen:
https://bugs.la
Is GDM3 multiseat aware? It is desirable to enable autologin for
selected seats only and need to specify different user per seat.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpa
Reached to this bug because of a similar issue we were able to resolve
using information here.
In 18.10, at least in our case, the RESUME variable is set with
partition device name, not UUID. Yet the identification failed, because
the device is not a link and readlink ${resume} returns nothing (or
Now found this bug, I think it is the lightdm who is not reporting idle
status to the system. See
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606 for a
script I run via cron every 15 minutes that overrides active status of
login screens or closing sessions. It also takes care of comm
I run the attached workaround script every 15 minutes from cron.
** Attachment added: "idlecheck.pl"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606/+attachment/5042477/+files/idlecheck.pl
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Public bug reported:
Ubuntu 16.04.3 LTS, multiseat setup.
systemd: Installed: 229-4ubuntu21
lightdm: Installed: 1.18.3-0ubuntu1.1
logind.conf:IdleAction=suspend
logind.conf:IdleActionSec=300
Using multiseat, it is not possible to have gnome settings controlling
idle suspend, as it would ignore
Ubuntu 16.04 also impacted
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/841672
Title:
ssh-add does not always unlock ssh keys
Status in openssh package in Ubuntu:
Con
If the current user is admin, the dialog shall prompt for his password directly.
A list of admin users makes sense only if the current user is not admin.
In Ubuntu 16.04, after adding second administrative user there is a
drop-down but password entry is disabled before selecting the other
admin an
9 matches
Mail list logo