Mathieu Trudel-Lapierre writes:
> AFAIK at the moment there isn't proper WPA Enterprise support (well,
> most TLS methods appears to be missing kernel patches). Let's please be
> careful about changing the default wireless daemon to iwd, there's a
> couple of moving parts there, it's not just abo
Will Cooke <1800...@bugs.launchpad.net> writes:
> Just so I understand, did you try and rebuild n-m with iwd enabled, or
> did you try and enable it at run time?
The latter.
--
James
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
Public bug reported:
I configured network manager to use iwd, unfortunately it doesn't work:
Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.4358] device
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed',
sys-iface-state: 'external')
Oct 25 15:12:23 malefic Network
More of the log:
https://pastebin.canonical.com/p/dQb39VRFZw/
This is network-manager 1.12.4-1ubuntu1 on 18.10 with iwd 0.8-2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad
Sorry but that argument is illogical. The only retention period that
would ensure that you always have the boot time kernel messages is
'infinity' and that's not a reasonable option for obvious reasons (c.f.
LP #1618188).
** Changed in: systemd (Ubuntu)
Status: Won't Fix => New
--
You re
Right, so this is lxc 1.x vs. lxd. Y'all should be using lxd, not lxc
1.x.
--
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/1582394
Title:
[16.04, lxc] Failed to reset devi
Per stgraber, squashfuse is currently going through MIR, once it's in
main, snapd will be updated to depend on it, making this work out of the
box.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bug
If you ensure your container (and host kernel) are up-to-date and
install squashfuse in the container, this works.
--
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/1582394
Tit
I'm afraid this didn't work for me. I installed network-manager
1.2.2-0ubuntu0.16.04.3 from xenial-proposed, ran 'systemctl restart
NetworkManager' as root and reconnected to the VPN and I see the same
behaviour (i.e. I get DNS resolution failure for non-VPN domains). I
am on wifi only and both v
cyphermox asked me for receipts!
http://people.canonical.com/~james/nm-settings/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1603898
Title:
DNS resolution fa
I can still reproduce this and I've double checked that my IPv4 and v6
settings are identical in terms of both the 'Method' filed (set to
'Automatic VPN' for both) and that both are set to accept all routes
from the VPN server.
Logs are here: https://pastebin.canonical.com/164434/
--
You receive
Good guess; that's exactly right.
| james@ornery:~$ dig +short @127.0.1.1 osmium-host.ppa
| 10.222.37.176
| james@ornery:~$ dig +short @127.0.1.1 www.openbsd.org
| james@ornery:~$
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
https://pastebin.canonical.com/161179/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1603898
Title:
DNS resolution fails when using VPN and routing all traffic ov
Public bug reported:
When using our company VPN, the Network Manager configured dnsmasq
ends up in a weird state where its unable to answer queries because
it's (incorrectly) sending them to 127.0.0.1:53 where nothing is
listening.
| root@ornery:~# nmcli con show 'Canonical UK - All Traffic' | gr
ChristianEhrhardt <715...@bugs.launchpad.net> writes:
> Also the question at Canonical Sysadmins: Any plans/progress on enabling
> the other[013].ubuntu.pool.ntp.org as well?
We don't own or control $ANYTHING.pool.ntp.org AFAIK
--
James
--
You received this bug notification because you are a
Serge, why do we offer people something which is such a landmine?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1520225
Title:
lxc-stop powered off a server
Status in lxc pa
Public bug reported:
I'm running wpa-supplicant with the following profile in complain mode:
http://paste.ubuntu.com/13011146/
After upgrading from vivid to wiley I get lots of notifications like
this in syslog:
[256841.262100] audit: type=1107 audit(1446223151.195:18142): pid=822
uid=103 auid
I'm still seeing this with Ubuntu 14.10:
3381 james 20 0 825M 219M 11672 S 0.5 2.8 1h10:23
/usr/lib/unity/unity-panel-service
I've attached /proc/`pidof unity-panel-service`/maps
** Attachment added: "/proc/`pidof unity-panel-service`/maps"
https://bugs.launchpad.net/ubuntu/+
"Theodore Ts'o" writes:
> If you try to use more than 95% of the storage, performance will
> generally suffer -- badly.
Sorry, but why is that? And do you mean read performance, write
performance or both? And is that a factor of the type of storage
(e.g. spinning disk vs. SSD)?
> In addition
Public bug reported:
mke2fs (and it's ext3 and ext4 analogs) still default to reserving 5%
of the filesystem for root. With the size of modern disks and arrays
this isn't a terribly sensible default, e.g. if I have a 10Tb array,
mke2fs will reserve 500Gb for root.
Obviously this is both tunable
20 matches
Mail list logo
