[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

2021-06-29 Thread GeekSmith
@ddstreet Thank you! It has been a long time coming, so I'm glad to see this fixed. -- 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/1853164 Title: systemd:

[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

2021-06-29 Thread GeekSmith
@thayne-u They don't care. There is ample reason to implement a fix for this, but they refuse to do what's best for users because they don't want us to run any software that doesn't start with "systemd". This is a very simple bug with a very simple fix, but they refuse to fix their defects. I've

[Touch-packages] [Bug 1838838] Re: username is not saved in openconnect connection dialog

2020-06-11 Thread GeekSmith
Here's a workaround from the RedHat folks. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2105 nmcli con mod VPNNAME vpn.secrets 'form:main:username=USERNAME','save_passwords=yes' ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2105

[Touch-packages] [Bug 1838838] Re: username is not saved in openconnect connection dialog

2020-06-11 Thread GeekSmith
Still present after upgrading 19.10 -> 20.04. -- 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/1838838 Title: username is not saved in openconnect connection dialog

[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

2020-01-08 Thread GeekSmith
If you are affected by this bug, please comment on the bug above. It has been open since August 2019. -- 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/1609700 Title:

[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

2020-01-08 Thread GeekSmith
Sebastien Bacher - please see https://bugs.launchpad.net/ubuntu/+source /network-manager-openconnect/+bug/1838838 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu.

[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

2019-12-31 Thread GeekSmith
This bug was reported to have resurfaced exactly 5 months ago, confirmed by several other community members here. When will the status be updated to reflect this and the bug be put on track for resolution? -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

2019-12-04 Thread GeekSmith
Not deprecated unless it happened very quietly. -- 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/1609700 Title: username is not saved in openconnect connection

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2019-10-15 Thread GeekSmith
kalvdans -- they don't get it. Inflexibility for inflexibility's sake is the new goal. My proposed fix is very simple and safe, but because it allows flexibility it's not going to be accepted. Feel free to edit the broken script in the package to enable your setup to work properly. I've done this

[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

2019-07-30 Thread GeekSmith
This bug resurfaced in Ubuntu 19.04 and persists in 19.10. I installed a fresh copy of both, installed network-manager-openconnect and network- manager-openconnect-gnome, and connected to the company VPN. The password is saved but the username is not saved and it must be manually entered. I

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2018-04-11 Thread GeekSmith
To distill this down to its most basic form, let's try this. When resolvconf or resolved is installed but disabled, its DHCP hook script still executes and potentially interferes with the proper operation of other hook scripts. My patch ensures that these hook scripts only run when the

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2018-04-11 Thread GeekSmith
What I'm trying to achieve is this: use resolvconf instead of resolved in Ubuntu 17.10. There is a bug when one tries to do so. This is a fresh install on a laptop using the desktop installation DVD. resolv.conf points to /run/resolvconf/resolv.conf and is managed by resolvconf. I have

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2018-01-25 Thread GeekSmith
> Flexibility for flexibility's sake is not a goal of Ubuntu. H...flexibility for the sake of making a system work seems like a good goal. As a user of Linux for 18 years, and one that has used Ubuntu since its very first release, I can say with confidence that Linux is absolutely about

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2018-01-25 Thread GeekSmith
Is the use of resolvconf and ifupdown without resolved an unsupported configuration in 17.10? Is resolved the only supported DNS configuration management system in Ubuntu 17.10? There are many users who value the control and flexibility of pre-resolved systems and do not want a local caching

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2018-01-25 Thread GeekSmith
The hasty push to replace resolvconf with resolved is having disastrous consequences. User experience and system stability should be valued over forced migration to an unproven, poorly tested, and in many cases unwanted new system. Name resolution is one of the fundamental building blocks of a

[Touch-packages] [Bug 1745463] [NEW] Disabling systemd-resolved breaks dhclient resolvconf integration

2018-01-25 Thread GeekSmith
Public bug reported: To reproduce, mask resolved: sudo systemctl mask systemd-resolved.service ...then disable network-manager for ifupdown interfaces: $cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile dns=default rc-manager=resolvconf [ifupdown]