lightdm-gtk-greeter does not work fine... no visual countdown/other
display of the autologin timeout. See
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/902852/comments/31
XDM also does not allow to cancel autologin before the time elapses.
--
You received this bug notification because
Ubuntu 16.04 also impacted. First kill from k3b works ok, after changing
CD the second attempt crashes the GUI session.
Launch of gvfsd-cdda should be optional. Related to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544148
Hacked by removal of the unneeded daemon:
# pwd; ls -l gvfsd-cdda*
16.04.3 LTS Pidgin 2.10.12 (libpurple 2.10.12) also impacted.
The notes above consider this situation normal, but it is not. There is
no reason for the app to skip collecting the spawned processes after
failed DNS or connection attempt.
https://developer.pidgin.im/ticket/15617 is still in new
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
Ubuntu 16.04 also impacted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/841672
Title:
ssh-add does not always unlock ssh keys
To manage notifications about this bug go to:
Not sure whether kill -9 is the best approach to stop the daemon. It
could be given a chance to clean up the pid files.
This looks to me more like an enhancement, are these also tracked as
launchpad bugs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
16.04. /etc/fstab contains
UUID=9bb5096d-7c9b-4a53-b298-7974b9cd6a74 /mnt/WD4 ext4
noauto,nofail,errors=remount-ro 0 0
Upon plugging the disk, following gets logged:
[190158.370855] sdd: sdd1
[190158.371844] sd 7:0:0:0: [sdd] Attached SCSI disk
[190158.649144] EXT4-fs (sdd1): warning:
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
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
Bugs, which is
Public bug reported:
It is impossible to determine whether exportfs command failed or
succeeded based on the exit status:
root@ver:~# exportfs asdf ; echo $?
exportfs: Invalid exporting option: asdf
0
user@ver:~$ exportfs ; echo $?
exportfs: could not open /var/lib/nfs/.etab.lock for locking:
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547297
Title:
No
Personally, I am not waiting for fix in xenial anymore. The storage is
now mounted to client directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766126
Title:
exportfs always returns success
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:
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
I am also experiencing it in 20.04, but I do not think it is a match
with this bug. I have never noticed it on 16.04 on the same HW for 5
years. Since upgrade it happens from time to time. NVidia binary drivers
in use, both before and now.
--
You received this bug notification because you are a
See comment of August 26, 2019 at 12:13 pm at
https://ryan.buterbaugh.org/better-qmail-on-ubuntu/ by Ryan Buterbaugh:
I believe this is a bug with runit – the /var/lib/supervise directory is
no longer being created as part of the package install. There are two
options here:
Install
Thank you for looking into the issue.
Let me first test current versions of squid against my router. If that
works I shall dig into the ubuntu code. Already tried to enable wccp
debug in squid but it did not help much. Ended up running a standalone
wccp client as a workaround.
Where is the patch
Public bug reported:
WCCP peering between squid and CIsco IOS 15.8(3)M2 stopped as of
Start-Date: 2021-10-07 06:27:37
Commandline: /usr/bin/unattended-upgrade
Upgrade: squid-common:amd64 (3.5.27-1ubuntu1.11, 3.5.27-1ubuntu1.12)
1) The release of Ubuntu you are using: 18.04
2) The version of
Upstream bug https://bugs.squid-cache.org/show_bug.cgi?id=5179
** Bug watch added: Squid Bugzilla #5179
http://bugs.squid-cache.org/show_bug.cgi?id=5179
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: squid3 (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Changed in: squid3 (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952158
4.13-10ubuntu5 in 21.10 and 5.2-1ubuntu1 in jammy are failing as well,
with debug log different when compared to version 3 involved here:
2021/12/05 19:58:41.705 kid1| 80,6| wccp2.cc(1580) wccp2HereIam: wccp2HereIam:
Called
2021/12/05 19:58:41.705 kid1| 80,5| wccp2.cc(1599) wccp2HereIam:
Version 1.0 released Feb 17, 2023 https://github.com/smtpd/qpsmtpd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709078
Title:
qpsmtpd is out of date
To manage notifications about this bug go to:
24 matches
Mail list logo
