[Desktop-packages] [Bug 1847651] Re: NetworkManager isn't pushing DNS server for openvpn connection to systemd-resolved
This is fixed in 20.04 -- 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/1847651 Title: NetworkManager isn't pushing DNS server for openvpn connection to systemd-resolved Status in network-manager package in Ubuntu: Confirmed Bug description: I imported an openvpn configuration with `nmcli c import type openvpn file config.ovpn`. After doing that, I edited the IPv4 and IPv6 settings for the VPN to turn off automatic DNS servers and specify an IPv4 DNS server IP address explicitly. I have /usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which contains: [main] # We need to specify "dns=systemd-resolved" as for the time being our # /etc/resolv.conf points to resolvconf's generated file instead of # systemd-resolved's, so the auto-detection does not work. dns=systemd-resolved Given all this, what I believe _should_ happen is when I start the VPN, /run/NetworkManager/no-stub-resolv.conf should be updated to list the DNS server I've specified first, AND NetworkManager should tell systemd-resolved to associate that DNS server with the tun0 network interface created for the VPN. The former happens, i.e., no-stub-resolv.conf is updated, but the latter doesn't, i.e., systemd-reoslve --status and resolvectl status both do not show the DNS server I've specified in the VPN settings. As a result, my DNS server is not getting used. I've hacked this all over the place and I can't figure out _any_ way, when using systemd-resolved mode in NetworkManager, to get it to use my VPN's DNS server when I enable the VPN. Surely this behavior is not expected? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 10 14:19:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-12 (28 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 10.204.0.1 dev wlp0s20f3 proto dhcp metric 600 10.204.0.0/21 dev wlp0s20f3 proto kernel scope link src 10.204.3.73 metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-09-20 (20 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1847651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878216] [NEW] NetworkManager Strongswan does not update systemd-resolved dns or lookup domain
Public bug reported: The configuration from an ipsec ikev2 server with push dns and default domain name does not update the systemd-resolved. Even manually adding the dns servers on the GUI does not update resolved. It works great with OpenVpn so I figure there is a problem with this package alone. Also maybe it's for another bug report, but it does not support EAP-TLS configuration. This happen on Ubuntu 20.04 with latest patches and updates. ** Affects: network-manager-strongswan (Ubuntu) Importance: Undecided Status: New ** Tags: dns network-manager strongswan ** Package changed: network-manager (Ubuntu) => network-manager- strongswan (Ubuntu) -- 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/1878216 Title: NetworkManager Strongswan does not update systemd-resolved dns or lookup domain Status in network-manager-strongswan package in Ubuntu: New Bug description: The configuration from an ipsec ikev2 server with push dns and default domain name does not update the systemd-resolved. Even manually adding the dns servers on the GUI does not update resolved. It works great with OpenVpn so I figure there is a problem with this package alone. Also maybe it's for another bug report, but it does not support EAP- TLS configuration. This happen on Ubuntu 20.04 with latest patches and updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-strongswan/+bug/1878216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
Works on Lenovo T450 i5-5300U -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Fix Committed Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
