Sorry for bad handling. #4 is attachment belonging to #5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1826639
Title:
wpasupplicant: unknown keys in no-mac-addr-change.conf
Suggested workaround:
1. Copy file /lib/NetworkManager/conf.d/no-mac-addr-change.conf to dir
/etc/NetworkManager/conf.d/
2. Edit file /etc/NetworkManager/conf.d/no-mac-addr-change.conf: Move 2
lines with cloned-mac-address to new chapter [connection-mac-addr-
change-wifi], cf. attachment.
--
** Attachment added: "no-mac-addr-change.conf"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+attachment/5352633/+files/no-mac-addr-change.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
Public bug reported:
I tried on Ubuntu 18.04 "sudo add-apt-repository ppa:mozillateam/ppa"
and got error:
Error: retrieving gpg key timed out.
I suspect: PGP/GPG-Keyserver interface was changed recently. add-apt-
repository doesn't work any more.
** Affects: apt (Ubuntu)
Importance:
Public bug reported:
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
ureadahead.service. Sometimes udisks2.service fails too.
$ uname -a
Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5
In contrast to #5 and not knowing any better interface, I expect
'lsb_release' to tell you if system uses HWE or not.
This can triggered by installiation of packet 'linux-image-generic-
hwe.16.04' or 'linux-image-lowlatency-hwe.16.04'.
These packets should
- either replace paket 'base-files'
HWE = hardware enablement stack
GA = ???
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1665653
Title:
lsb_release -d should show a hint if it uses HWE or not
Status in lsb
More experiments, results and proposed solution:
1) On a system with
whoopsie running
network-manager NOT running, but network interface initialized via
/etc/network/interfaces
dnsmask running with network-managers configuration for dnsmasq
IPv6 aktivated
I see the annoying repetive
I did some experiments on an Ubuntu GNOME 14.04 LTS desktop standard
installation. There are 4 (!) components involved in this annoying
traffic:
whoopsie
network manager
dnsmasq (started by network manager)
IPv6
The repeated DNS-requests for daisy.ubuntu.com stop when de-activating anyone
of
9 matches
Mail list logo
