[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

> Comment here only if you think the duplicate status is wrong. Or I won't. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

I had a lot of trouble with NetworkManager+OpenVPN on Ubuntu and discovered a couple of workarounds. If you're having trouble resolving internal domain names (like *.internal.company.com), you might want to try adding something like this to the [ipv4] section in /etc/NetworkManager/system-

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

@hckrmagoo I had this problem as well, try making NetworkManager run OpenVPN as root: https://askubuntu.com/a/906055/844205. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 1781091] Re: notify-send only works the first time

> for every notify-send call For every _failed_ notify-send call. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1781091 Title: notify-send only works the first time Status in

[Desktop-packages] [Bug 1781091] [NEW] notify-send only works the first time

Public bug reported: (I think this started happening after upgrading gnome-shell to 3.28.2-0ubuntu0.18.04.1 today.) Reproduce: * Run `notify-send ok ok`. Expected result: * A notification pops up for every execution of the command above. Actual result: * A notification might pop

[Desktop-packages] [Bug 1781091] Re: notify-send only works the first time

I installed a fresh Ubuntu on a VM, and the problem did go away. I'm sorry for misleading you. I found out that the problem goes away if I disable the third-party GSConnect extension (due to be included in the next Ubuntu, https://github.com/andyholmes/gnome-shell-extension- gsconnect) that talks

[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

I still don't get it. It's been unfixed in Bionic since forever. Do I need to enable -proposed do get the fix? I thought this was risky. It's really annoying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu.

[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

Any info on when's that going to be released? Can't find it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current

[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

I don't really get it, when's the fix going to be available for Bionic? I have -updates enabled, but the bug is still present on my system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu.