> This won't help anyone that has already received the broken update - I
think the advice there is to restart, or there is a workaround in the OP
here - but it should prevent any further occurrences.
Do note this is not a solution for those using non-Azure resolvers
provided via DHCP through their
Microsoft has created an incident for this.
https://azure.status.microsoft/en-us/status reports:
Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors
- Investigating
Starting at approximately 06:00 UTC on 30 Aug 2022, a number of
customers running Ubuntu 18.04 (bionic) VMs rece
We've just had the same problem, on multiple VMs running in Azure.
In the dpkg log we can see that systemd was indeed updated (times in
UTC):
2022-08-30 06:31:18 status unpacked udev:amd64 237-3ubuntu10.54
2022-08-30 06:31:18 status half-configured udev:amd64 237-3ubuntu10.54
2022-08-30 06:31:19
Public bug reported:
Two servers today that updated systemd to "systemd 237-3ubuntu10.54"
https://ubuntu.com/security/notices/USN-5583-1
could not resolve dns anymore.
no dns servers, normally set through dhcp.
Ubuntu 18.04
Temp fix.
1. Edit /etc/systemd/resolved.conf
1. Add/Uncomment # Fall
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2001-1228
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1358762
Title:
Included gzip 1.2.4 has several vulnerab
Fixed my dnsmasq systemd-resolve race with dnsmasq config.
/etc/dnsmasq.d/myconfig
#PES 20180808 dnsmasq and systemd-resolve conflict.
# dont use /etc/resolv.conf, go direct to systemd-resolve, only bind to lo
no-resolv
bind-interfaces
interface=lo
server=127.0.0.53
--
You received this bug not
Fixed my dnsmasq systemd-resolve race with dnsmasq config.
/etc/dnsmasq.d/myconfig
#PES 20180808 dnsmasq and systemd-resolve conflict.
# dont use /etc/resolv.conf, go direct to systemd-resolve, only bind to lo
no-resolv
bind-interfaces
interface=lo
server=127.0.0.53
--
You received this bug noti
Ubuntu 18.04.
edited $sudo vim /etc/resolv.conf
changed
nameserver 127.0.0.1
to
nameserver 127.0.0.53
CPU calmed down.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
I've ran into an issue when creating a large number of virtual functions
on a SR-IOV capable device.
ip link show reports a message truncated error:
ip link show > /dev/null
Message truncated
Message truncated
Message truncated
A likely cause might be that when called in a s
This problem stems from the inclusion of the fix for CVE-2015-5180. The
internal number for A + changed in glibc (from T_UNSPEC=62321 to
T_QUERY_A_AND_=439963904).
In TCPDump, we see queries going out for TYPE62321 (the former internal
number for A+).
I think busybox uses the old sym
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1664535
Title:
critical bug in top command package procps
Status in procps package in Ubuntu:
Fix Released
Status
Hi again,
I've done some digging and this is a known/fixed bug in procps version
3.3.10.
This is not backported to the latest 14.04.x in Ubuntu, and I believe it
to be a severe enough bug to warrant such efforts.
FYI:
http://www.freelists.org/post/procps/top-Escape-doesnt-abort-kill-
command,1
Public bug reported:
I think I've discovered a bug in the linux top command. (Ubuntu 14.04
tested only)
Steps to reproduce:
$ top
press k
it then prompts for PID or selects top process by default
press the esc key
press esc key again
Result:
it kills the process anyway
It's weird to me that
Public bug reported:
error occured while updating via sudo apt upgrade
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.8
ProcVersionSignature: Ubuntu 4.4.0-62.83-powerpc64-smp 4.4.40
Uname: Linux 4.4.0-62-powerpc64-smp ppc64
ApportVersion: 2.20.1-0ubuntu2.5
Permanent fix, avoid mirror in apt source file
#Replaced
deb mirror://mirrors.ubuntu.com/mirrors.txt yakkety main restricted
#with
deb http://nz.archive.ubuntu.com/ubuntu/ yakkety main restricted
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
synaptic pop-up error message.
Method mirror has died unexpectedly!Sub-process mirror received a
segmentation fault.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1613184
Tit
temporary workaround is to downgrade to 1.2
# dpkg -i /var/cache/apt/archives/apt-transport-
https_1.2.15ubuntu0.2_amd64.deb
repeat dpkg -i for
/var/cache/apt/archives/apt-transport-https_1.2.15ubuntu0.2_amd64.deb
/var/cache/apt/archives/apt-utils_1.2.15ubuntu0.2_amd64.deb
/var/cache/apt/archi
Work around for me, back to 1.2
# dpkg -i /var/cache/apt/archives/apt_1.2.15ubuntu0.2_amd64.deb
dpkg: warning: downgrading apt from 1.3.3 to 1.2.15ubuntu0.2
# dpkg -i /var/cache/apt/archives/apt-utils_1.2.15ubuntu0.2_amd64.deb
dpkg: warning: downgrading apt-utils from 1.3.3 to 1.2.15ubuntu0.2
Public bug reported:
package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status
1
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.1
ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2
exactly the same here on my compaq presario c500
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1594023
Title:
Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Sta
I had the problem now on Ubuntu 16.04, ModemManager running using one
cpu for 10minutes already, after a logout and login with no reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.lau
*** This bug is a duplicate of bug 1098362 ***
https://bugs.launchpad.net/bugs/1098362
I bumped into the fixed 10.42 subnet in Network Manager eth0 "shared to
other computers"
Is the subnet hard coded ? I could not find any config file that
contained the IP.
--
You received this bug notifi
Just using ssh and all the ecryptfs problems are gone.
I think ecrypfts should provide a better explanation, when it cant
access the keyring.
Kernel:
4.4.1-040401-generic #201601311534 SMP Sun Jan 31 20:36:43 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification becaus
Just hit it with mosh session.
"Unable to link the KEY_SPEC_USER_KEYRING into the
KEY_SPEC_SESSION_KEYRING; there is something wrong with your kernel
keyring. Did you build key retention support into your kernel?"
--
You received this bug notification because you are a member of Ubuntu
Touch see
The Ubuntu Wiki page at https://wiki.ubuntu.com/Power#settings seems to say
that if the mouse battery is low, then it gets the battery indicator. In my
opinion, this is fundamentally incorrect behaviour.
If the PC has a battery then it is likely to be a laptop and therefore it's
more important t
, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1397666
Title:
sshd does not properly initialize libgcrypt
Status in openssh package in Ubuntu:
Incomplete
Bug description:
The following warnings can be found in syslog:
pieter-local@test-02:~$ grep "please fi
, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1397663
Title:
sudo does not properly initialize libgcrypt
Status in sudo package in Ubuntu:
New
Bug description:
The following warnings can be found in syslog:
pieter-local@test-02:~$ grep "please fix the applic
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1397666
Title:
sshd does not properly initialize libgcrypt
Status in openssh package in Ubuntu:
Incomplete
Bug description:
The following warnings can be found in syslog:
pieter-local@test-02
to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1397666
Title:
sshd does not properly initialize libgcrypt
Status in openssh package in Ubuntu:
New
Bug description:
The following warnings can be found in syslog:
pieter-local@test-02:~$ grep "please fix the application"
subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1397663
Title:
sudo does not properly initialize libgcrypt
Status in sudo package in Ubuntu:
New
Bug description:
The following warnings can be found in syslog:
pieter-local@test-02:~$ grep "please fix the application" /var/
Public bug reported:
The following warnings can be found in syslog:
pieter-local@test-02:~$ grep "please fix the application" /var/log/syslog |grep
sshd
Nov 30 12:19:21 test-02 sshd[1226]: Libgcrypt warning: missing initialization -
please fix the application
Nov 30 12:20:06 test-02
Public bug reported:
The following warnings can be found in syslog:
pieter-local@test-02:~$ grep "please fix the application" /var/log/syslog |grep
sudo
Nov 30 12:20:20 test-02 sudo: Libgcrypt warning: missing initialization -
please fix the application
Nov 30 12:25:15 test-02 sudo:
The upgrade now worked for me too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1328264
Title:
packaging issues with the trusty Xstack in precise xserver-xorg-lts-
trusty
33 matches
Mail list logo
