[Touch-packages] [Bug 1815275] Re: logind fails to detect amdgpu external displays as external.

2019-02-09 Thread Mercury
Marking as invalid because this isn't actually what's going on. The xrandr name isn't used, the sysfs/udev node name is, and that is correct. Something else is triggering the behavior, but that will need to be tracked in it's own bug. Sorry for the noise. ** Changed in: systemd (Ubuntu)

[Touch-packages] [Bug 1815275] [NEW] logind fails to detect amdgpu external displays as external.

2019-02-09 Thread Mercury
Public bug reported: So, with a Dell Precision 7530 outfitted with an AMD GPU, I can run into issues relating to systemd not detecting that my laptop is docked. This results in my booting the system, getting the login prompt on my external displays, logging in, and having the system immediately s

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-04-05 Thread Mercury
Ryan, The problem is not that a recent change in resolvconf caused a regression. The problem with resolvconf is that the upgrade to network-manager exposed an existing bug in resolvconf. This happens because the new version of network-manager now tells resolvconf that it must only use a specific

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-03-30 Thread Mercury
After two and a half weeks, can we please get a build of resolvconf with http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b applied pushed out? We don't even need the full new release of resolvconf, we just need the documented bug (https://bugzil

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-03-13 Thread Mercury
So, this managed to break at least my VPN setup quite well. See #1672491 with the details, but the short version is that 'specify egress interface for each dnsmasq upstream server' breaks things in two cases. The first could be argued to be a bug on the VPN client side, though a behavior change o

[Touch-packages] [Bug 1672491] Re: New NetworkManager breaks VPN DNS.

2017-03-13 Thread Mercury
Alright, this is due to a change to 1.2.4: commit 2f12f485607590d6415cf5fb81ad4db5b04615cd Author: Beniamino Galvani Date: Wed May 11 18:43:41 2016 +0200 dns: specify egress interface for each dnsmasq upstream server Currently we don't specify to dnsmasq which interface must be u

[Touch-packages] [Bug 1672491] [NEW] New NetworkManager breaks VPN DNS.

2017-03-13 Thread Mercury
Public bug reported: Alright, this is going to be a frustrating bug for everyone involved I expect, but here goes. On Ubuntu 16.04, using a non-released VPN client (making this _much_ harder for anyone to reproduce), upgrading the network-manager packages from 1.2.2-0ubuntu0.16.04.3 to 1.2.6-0ubu