Public bug reported:
Description:Ubuntu 22.04.1 LTS
Release:22.04
lvm2:
Installed: 2.03.11-2.1ubuntu4
Candidate: 2.03.11-2.1ubuntu4
Version table:
*** 2.03.11-2.1ubuntu4 500
500 http://apt-mirror.us.archive.org/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/
** Changed in: unattended-upgrades (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1633098
Title:
override of AP
the linked comment seems to describe a different circumstance than the
comments in setup_apt_listchanges (which does not mention the pager
frontend). debian bug 579733 is also focused on mail behavior rather
than pager.
that said, i can confirm that u-u does NOT hang with the above patch
applied
Public bug reported:
unattended-upgrades overrides the setting of APT_LISTCHANGES_FRONTEND.
per the comments, this was done at a time when apt-listchanges would
"always send a mail if there is a mail address set in the config
regardless of the frontend used." this is no longer the case and this
(
** Description changed:
the sanity check of the TZ env variable implemented in
1.8.9p5-1ubuntu1.1 to address CVE-2014-9680 apparently has the side
effect of carrying forward the TZ variable despite explicit removal in
/etc/sudoers. 1.8.9p5-1ubuntu1 does not exhibit this behavior.
% fg
Public bug reported:
the sanity check of the TZ env variable implemented in
1.8.9p5-1ubuntu1.1 to address CVE-2014-9680 apparently has the side
effect of carrying forward the TZ variable despite explicit removal in
/etc/sudoers. 1.8.9p5-1ubuntu1 does not exhibit this behavior.
% fgrep env_ /etc/s
`mountall --verbose` log w/ip addr in fstab
** Attachment added: "mountall.log.ipaddr"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242077/+files/mountall.log.ipaddr
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
** Attachment added: ".var.log.upstart.mountall.log"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242076/+files/.var.log.upstart.mountall.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Attachment added: ".etc.network.interfaces"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242075/+files/.etc.network.interfaces
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in
i also attempted a boot w/the nfs server's ip address instead of
hostname (although technically i guess "nfs-home" is an alias). no
change, /home was still not mounted automatically on boot by mountall.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Public bug reported:
i'm uncertain exactly when this issue started as we use cfengine
(verifies all expected mounts in place, manually mounts those that are
not). from a note i have i believe it goes back as far as lucid.
the symptom is that an /etc/fstab entry for an nfs-mounted /home is not
mo
11 matches
Mail list logo