[Bug 1885574] Re: Lenovo Ideapad S740 touchscreen is not working
I have a Lenovo Ideapad S740-15IRH and the touchscreen does not work in linux on any distro even with the latest kernel 5.14.14. Is it possible to fix this? ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885574 Title: Lenovo Ideapad S740 touchscreen is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939174] Re: GRUB2 can't boot Linux on HP Dragonfly G2
*** This bug is a duplicate of bug 1939988 *** https://bugs.launchpad.net/bugs/1939988 Okay wait a minute, it IS possible to install Ubuntu by writing the ISO to the bootable key with dd from a machine running Linux. I used dd like so: `sudo dd bs=4M if=/home/noctua/Downloads/ubuntu-21.10-desktop- amd64.iso of=/dev/sdb conv=fdatasync status=progress` and I was amazed that Ubuntu actually booted. It took some time to boot, but I was able to use the installer successfully and I can confirm Ubuntu 21.10 works fine on the Elite Dragonfly G2 (disable PSR using i915.enable_psr=0 in the GRUB config kernel boot parameters after installation to eliminate screen tear and lag). Definitely try doing that. It seems like the HP system firmware has a flaw with being unable to boot certain things. Given that the Fedora USB creator writes the raw ISO to the key, this might be why a Fedora USB key works. I still think this is a flaw that needs to be fixed, but at least there is a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939174 Title: GRUB2 can't boot Linux on HP Dragonfly G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1939174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939988] Re: GRUB2 can't boot Linux on HP Dragonfly G2
Okay wait a minute, it IS possible to install Ubuntu by writing the ISO to the bootable key with dd from a machine running Linux. I used dd like so: `sudo dd bs=4M if=/home/noctua/Downloads/ubuntu-21.10-desktop- amd64.iso of=/dev/sdb conv=fdatasync status=progress` and I was amazed that Ubuntu actually booted. It took some time to boot, but I was able to use the installer successfully and I can confirm Ubuntu 21.10 works fine on the Elite Dragonfly G2 (disable PSR using i915.enable_psr=0 in the GRUB config kernel boot parameters after installation to eliminate screen tear and lag). Definitely try doing that. It seems like the HP system firmware has a flaw with being unable to boot certain things. Given that the Fedora USB creator writes the raw ISO to the key, this might be why a Fedora USB key works. I still think this is a flaw that needs to be fixed, but at least there is a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939988 Title: GRUB2 can't boot Linux on HP Dragonfly G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1939988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939174] Re: GRUB2 can't boot Linux on HP Dragonfly G2
*** This bug is a duplicate of bug 1939988 *** https://bugs.launchpad.net/bugs/1939988 This issue affects me as well on the HP Elite Dragonfly G2. It's really awful, I can't even start the boot process on a Ubuntu live installer. It doesn't seem to matter how I format the USB drive either. I have Fedora 34 installed but I cannot boot Ubuntu 20.04, 20.10, 21.04, or 21.10 at all. When selecting an entry with GRUB on a Ubuntu live key, I just get a black screen with a blinking white cursor at the top. What could be the problem? I regret buying this machine immensely, it has issues already with charging and wifi. It seems that the firmware won't allow us to boot Ubuntu or Debian or really any non-Fedora/RHEL distribution. On Parted Magic, I get an "out of memory" error immediately and cannot boot the image. I think this is also what is happening with the Ubuntu live image. Is the firmware reporting available memory incorrectly when attempting to boot or blocking initramfs over a certain size? Is it possible to fix this? Honestly I'm so upset at HP for introducing firmware bugs like this. No one in their right mind would design system firmware like this to prevent the booting of Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939174 Title: GRUB2 can't boot Linux on HP Dragonfly G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1939174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939988] Re: GRUB2 can't boot Linux on HP Dragonfly G2
This issue affects me as well on the HP Elite Dragonfly G2. It's really awful, I can't even start the boot process on a Ubuntu live installer. It doesn't seem to matter how I format the USB drive either. I have Fedora 34 installed but I cannot boot Ubuntu 20.04, 20.10, 21.04, or 21.10 at all. When selecting an entry with GRUB on a Ubuntu live key, I just get a black screen with a blinking white cursor at the top. What could be the problem? I regret buying this machine immensely, it has issues already with charging and wifi. It seems that the firmware won't allow us to boot Ubuntu or Debian or really any non-Fedora/RHEL distribution. On Parted Magic, I get an "out of memory" error immediately and cannot boot the image. I think this is also what is happening with the Ubuntu live image. Is the firmware reporting available memory incorrectly when attempting to boot or blocking initramfs over a certain size? Is it possible to fix this? Honestly I'm so upset at HP for introducing firmware bugs like this. No one in their right mind would design system firmware like this to prevent the booting of Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939988 Title: GRUB2 can't boot Linux on HP Dragonfly G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1939988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822581] Re: HP 1030 G3 fn-keys not working
Same issue with the brightness keys on the HP Elite Dragonfly G2, even on kernel 5.13. Seems like a firmware bug, but may have something to do with the HP WMI keycode driver. Really annoying and not at all good for such an expensive product. This needs to be fixed, it affects most of HP's new business laptops. Could someone describe how to do the power reset please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841039] Re: Multiple keys have same keycode on HP ProBook 450 G6
I'm having the same issue with function keys for brightness on the HP Elite Dragonfly G2. F3 and F4 both map to muting the microphone. This is a firmware bug. It happens on the latest version of Ubuntu and on Fedora 34. Really, this needs to be fixed. If someone would take a look at the firmware, we could solve this issue for all affected HP business laptops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841039 Title: Multiple keys have same keycode on HP ProBook 450 G6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726548] Re: Windows resized after resume
This bug needs to be reopened, I have the same issue on Ubuntu 20.10 with a 4K laptop screen with 2x scaling. The same problem is found on Fedora 33. As @estebanium wrote, If the lid is closed to suspend, when the laptop is reopened, maximized windows are instead offscreen (only left half shows). Very annoying, the only solution is to manually suspend before closing the lid. This bug appears to be a Gnome/metacity problem and has persisted since 2017. Really needs a fix soon. ** Changed in: ubuntu-gnome-meta (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726548 Title: Windows resized after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876955] Re: On start Deluge shows the message "Only thin mode is available due to unknown import Error. To use Standalone mode, please see logs for error details."
Can confirm this exact thing happens to me on Ubuntu 20.04. I can't even run the Deluge application with this bug. This needs to be fixed ASAP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876955 Title: On start Deluge shows the message "Only thin mode is available due to unknown import Error. To use Standalone mode, please see logs for error details." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deluge/+bug/1876955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835644] Re: CRL files are not accessible for the Verify CRL options
Looking at the source code for nm-openvpn-service.c, before this bug was
introduced it doesn't appear that the crl-verify option was ever
implemented or used, as it is not found within the code. The only lines
that refer to crl-verify were introduced in Ubuntu 19.04, and consist of
the following:
tmp = nm_setting_vpn_get_data_item (s_vpn, NM_OPENVPN_KEY_CRL_VERIFY_FILE);
if (tmp)
args_add_strv (args, "--crl-verify", tmp);
else {
tmp = nm_setting_vpn_get_data_item (s_vpn,
NM_OPENVPN_KEY_CRL_VERIFY_DIR);
if (tmp)
args_add_strv (args, "--crl-verify", tmp, "dir");
}
Frankly I do not know how or why "/var/lib/openvpn/chroot/" gets
incorrectly prepended to the file path in the openvpn argument string,
but the crl-verify option clearly doesn't work (or may never have worked
after it was introduced). This needs fixing ASAP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835644
Title:
CRL files are not accessible for the Verify CRL options
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1835644/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835644] Re: CRL files are not accessible for the Verify CRL options
This is a serious problem compromising the security of OpenVPN on Linux. Every time I try to use crl-verify I get the following error: nm-openvpn[3957]: Options error: --crl-verify fails with '/var/lib/openvpn/chroot/[insert path to pem file selected here]': No such file or directory (errno=2) The network manager cannot find the specified .pem file because for some reason the path is being prepended with "/var/lib/openvpn/chroot/". This bug needs to be fixed ASAP, I had no idea this was an issue until "upgrading" to this broken version of the network manager in Ubuntu 20.04. This bug is completely unacceptable and frankly ridiculous in that it has not been fixed or addressed. Please fix this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835644 Title: CRL files are not accessible for the Verify CRL options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1835644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718931] Re: No VPN autoconnect
Well...it has been quite some time and this bug has received absolutely *zero* attention from the Gnome Shell Gitlab here https://gitlab.gnome.org/GNOME/gnome-shell/issues/123 escalated from the Gnome Bugzilla tracker after Gnome shell development moved to Gitlab. The issue is fully present in Ubuntu 18.04 AND in the newer version of the Gnome shell and NetworkManager in Fedora 28. Before v3.26.X, auto- connect worked fine through the NetworkManager in the Gnome environment. I'm afraid to report that months later, absolutely nothing has been done to address what should be a relatively high-priority bug in the Gnome Shell. If anyone has the capabilities to reach out farther than I already have, please do so. This critical bug has been sitting idle with no attention for months, and persists across newer versions of the Gnome shell, namely 3.28.X, seemingly independent of distribution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718931 Title: No VPN autoconnect To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1718931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718931] Re: No VPN autoconnect
Filed an upstream bug, at long last, in the Gnome bugtracker at https://bugzilla.gnome.org/show_bug.cgi?id=793977 ** Bug watch added: GNOME Bug Tracker #793977 https://bugzilla.gnome.org/show_bug.cgi?id=793977 ** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=793977 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718931 Title: No VPN autoconnect To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1718931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718931] Re: No VPN autoconnect
Okay, so...why isn't this a priority bugfix? I love gnome, don't get me wrong, but when I can't even autoconnect to my VPN like I did countless times in the past few years running Ubuntu on Unity without compromising the security of my system something is wrong. There needs to be an option - and a working one at that - for auto-connecting to a VPN through the Gnome NetworkManager GUI. The KDE folks fixed this ages ago with KWallet, I suspect this involves the Gnome-Keyring. This is a *very* annoying problem. Should I report the bug on the Gnome bugtracker? So frustrating when this is an extremely common problem with nobody actually looking into *why* it's happening or how to fix it. I'm afraid this one is beyond me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718931 Title: No VPN autoconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1718931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752767] [NEW] grub2 regression, simultaneous console and video graphical glitches with new patch
Public bug reported: Okay, so the following patch at http://launchpadlibrarian.net/356413428/grub2_2.02~beta3-4ubuntu7.1_2.02~beta3-4ubuntu7.2.diff.gz which basically amounts to changing a single line in /etc/grub.d/00_header TOTALLY breaks my menu selection graphics when I boot up. Every time a line changes, like as in scrolling the menu or watching the countdown timer, I can see the console mode GRUB line flashing black and white behind the video gfx mode screen. I believe this regression is caused entirely by Dann Frazier's idea for the grub patch: "Instead of switching from "console" to "gfxterm", let's output to both." *sigh* Removing the single change, the "--append" flag, in the file /etc/grub.d/00_header and regenerating the grub.cfg file completely solves the problem. What concerns me is that this patch somewhat breaks the average user's default grub gfx mode; it looks glitchy and horrible. I simply cannot tolerate this behavior on an incredibly simple boot selection menu, let alone on an actual grub theme, KDE-style. My machine is a very standard HP EliteDesk 800 G3 Mini Desktop, and I had no problems before with GRUB doing this horrible-looking pop-from-behind simultaneous video and console behavior. This tiny patch represents a misguided and frankly appalling regression. And yes, this applies upstream to Bionic Beaver (I tried the proposed package also) as well as the current version of the grub2 package on Artful Aardvark. Please fix before the Ubuntu LTS release ships with this glaring bug. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: regression-proposed regression-release regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752767 Title: grub2 regression, simultaneous console and video graphical glitches with new patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1752767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
@bagl0312 I agree, there really should be some kind of GUI default way to set negative DNS priority when setting up certain VPN connections. The average user shouldn't experience a nasty surprise when DNS leaks happen by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728143] Re: Screen freezes after waking from suspend with Gnome on Wayland
Okay, I will try this with a fresh install of Ubuntu 17.10 and provide the necessary logs soon. I should be able to use the provided script over ssh, thanks. The problem with GDM freezing on Wayland after system resume/wakeup has been occurring ever since I ran the beta builds of 17.10, but it's clearly not fixed. I've been relatively busy lately, my apologies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728143 Title: Screen freezes after waking from suspend with Gnome on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1728143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728145] [NEW] gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10
Public bug reported: When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu 17.10, gnome-terminal (v3.24.2 is the version in the 17.10 repositories) does not fill the screen at all when snapping the window to the right or left side. There are large gaps on the right and bottom edges of the terminal window in Wayland. On the same computer, with the same version of gnome-terminal in an Xorg gnome-session or Xorg ubuntu-session, the window fills screen space entirely and there is no problem. I am not using display scaling or hidpi features at all, my display resolution is set at default 1080p. This needs to be fixed or I'm ditching gnome- terminal. Expected behavior: gnome-terminal window should fill right/left of screen when snapped to corner in a Wayland session What happened instead: gnome-terminal window does not fill screen space when snapped to right or left edge of desktop on Wayland session, there are large gaps below and to the right of the snapped window on either side. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-terminal wayland ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Description changed: - When using a Wayland gnome-session or ubuntu-session in Ubuntu 17.10, - gnome-terminal (v3.24.2 is the version in the 17.10 repositories) does - not fill the screen at all when snapping the window to the right or left - side.There are large gaps on the right and bottom edges of the terminal - window in Wayland. On the same computer, with the same version of gnome- - terminal in an Xorg gnome-session or Xorg ubuntu-session, the window - fills screen space entirely and there is no problem. I am not using - display scaling or hidpi features at all, my display resolution is set - at default 1080p. This needs to be fixed or I'm ditching gnome-terminal. + When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu + 17.10, gnome-terminal (v3.24.2 is the version in the 17.10 repositories) + does not fill the screen at all when snapping the window to the right or + left side.There are large gaps on the right and bottom edges of the + terminal window in Wayland. On the same computer, with the same version + of gnome-terminal in an Xorg gnome-session or Xorg ubuntu-session, the + window fills screen space entirely and there is no problem. I am not + using display scaling or hidpi features at all, my display resolution is + set at default 1080p. This needs to be fixed or I'm ditching gnome- + terminal. Expected behavior: gnome-terminal window should fill right/left of screen when snapped to corner in a Wayland session What happened instead: gnome-terminal window does not fill screen space when snapped to right or left edge of desktop on Wayland session, there are large gaps below and to the right of the snapped window on either side. ** Description changed: When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu 17.10, gnome-terminal (v3.24.2 is the version in the 17.10 repositories) does not fill the screen at all when snapping the window to the right or - left side.There are large gaps on the right and bottom edges of the + left side. There are large gaps on the right and bottom edges of the terminal window in Wayland. On the same computer, with the same version of gnome-terminal in an Xorg gnome-session or Xorg ubuntu-session, the window fills screen space entirely and there is no problem. I am not using display scaling or hidpi features at all, my display resolution is set at default 1080p. This needs to be fixed or I'm ditching gnome- terminal. Expected behavior: gnome-terminal window should fill right/left of screen when snapped to corner in a Wayland session What happened instead: gnome-terminal window does not fill screen space when snapped to right or left edge of desktop on Wayland session, there are large gaps below and to the right of the snapped window on either side. ** Summary changed: - gnome-terminal does not fill screen when window snapping on Wayland + gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728145 Title: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1728145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728143] [NEW] Screen freezes after waking from suspend with Gnome on Wayland
Public bug reported: It appears that using Xorg instead of Wayland is the only way to fix this problem on Ubuntu 17.10. For some odd reason, whenever I wake my computer from suspend (especially after an extended period of time asleep) using Gnome in a Wayland session (gnome-session and stock ubuntu-session alike), my screen freezes completely on whatever was last there before suspending and I can't get any IO response at all. Nothing, the screen is totally frozen. I am also unable to exit into a recovery shell or kill GDM or gnome-session/ubuntu-session locally. I also can't seem to find any traces or indications for the freeze in the syslog, or maybe I'm just not sure where to look. I believe this is a problem with GDM on Wayland, not kernel related, as it happens on a totally stock install and when I use an upgraded/downgraded kernel. It literally necessitates restarting my computer. This problem is nonexistent when using Xorg instead of Wayland with GDM. Anyone else have this issue on Ubuntu 17.10 or figure out a solution better than simply switching to Xorg? I should clarify that I am not using nvidia drivers, I'm using Intel integrated graphics on a core-i7 5500U. Ubuntu 17.10 uses gnome-session v3.26.1. Expected behavior: When waking computer from suspend, expect GDM lock prompt and log back in. What happened instead: When waking computer from suspend, screen and IO is completely frozen, necessitating a force-shutdown. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: gdm gnome-17.10 gnome-session suspend-resume ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728143 Title: Screen freezes after waking from suspend with Gnome on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1728143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I'm not sure about split-horizon DNS, frankly I think that is a different bug entirely. However, I have had no problems with DNS leaks over my VPN connections whatsoever on Ubuntu 17.10. The bugfix I personally requested from the NM-devs and backported to Ubuntu 17.04 (running NetworkManager v1.4.x) was effectively just patching the negative dns-priority bug related to systemd-resolved. From 'man nm- settings': "Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used." This means that DNS servers configured for the non-VPN connection will be 'unseated' and ONLY the VPN-configured DNS servers are used. Ubuntu 17.10 is running NetworkManager v1.8.4, so Thomas Haller's merged bugfix is present and working. You MUST use the command: 'sudo nmcli connection modify ipv4.dns-priority -42' or similar to actually set negative DNS priority for the VPN connection. Restart the network manager with 'sudo service network-manager restart', then connect to the VPN. Examine the output of 'systemd-resolved --status' and use the 'Extended' test on dnsleaktest.com to verify that you are not leaking DNS queries. I use openvpn, but setting negative dns priority should work for preventing DNS leaks over regular VPN connections of all kinds as a kind of 'catch-all'. Auto-connecting to openvpn through the GUI is a little troublesome in 17.10, but this 'fix' worked for me: https://askubuntu.com/questions/967408/how-to-automatically-connect-to-vpn-in-ubuntu-17-10/967415#967415 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718931] Re: No VPN autoconnect
Literally just toggling that one option "Store password for all users" in the VPN settings fixes the problem entirely. Use "sudo service network-manager restart" and it connects flawlessly the first time. To avoid the error loop on bootup specifically, just uncheck the box "Make available to other users" on the primary connection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718931 Title: No VPN autoconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1718931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718931] Re: No VPN autoconnect
Yeah, I keep getting the "vpn-connection[...]: Failed to request VPN secrets #3: No agents were available for this request." error message in my syslog. I found, however, that THIS worked for me: All you have to do is go Dash->VPN->VPN Settings->connection_name_here->Identity->Password->"Store for all users" and bingo problem solved. If nm-connection-editor says that you can't save the connection (the save box is grayed out), then...just forget the network and set up the connection again (worked for me at least). Once you have checked said auto-connect box with nm-connection- editor and ensured that the VPN password is set to "Store for all users," both the primary connection AND the VPN will start successfully at the same time. See my post at https://askubuntu.com/questions/967408 /how-to-automatically-connect-to-vpn-in-ubuntu-17-10/967415#967415 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718931 Title: No VPN autoconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1718931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681295] Re: Problem in nm-openvpn-service.c, openvpn connection fails after key renegotiation because --auth-user-pass is passed with --auth-nocache.
Debian package for network-manager-openvpn-gnome built for Ubuntu 17.04 attached. ** Attachment added: "network-manager-openvpn-gnome_1.2.6-2ubuntu2_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+attachment/4953145/+files/network-manager-openvpn-gnome_1.2.6-2ubuntu2_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681295 Title: Problem in nm-openvpn-service.c, openvpn connection fails after key renegotiation because --auth-user-pass is passed with --auth-nocache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681295] Re: Problem in nm-openvpn-service.c, openvpn connection fails after key renegotiation because --auth-user-pass is passed with --auth-nocache.
Debian package for network-manager-openvpn built for Ubuntu 17.04 attached. ** Attachment added: "network-manager-openvpn_1.2.6-2ubuntu2_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+attachment/4953144/+files/network-manager-openvpn_1.2.6-2ubuntu2_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681295 Title: Problem in nm-openvpn-service.c, openvpn connection fails after key renegotiation because --auth-user-pass is passed with --auth-nocache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
@Stephan the Penguin god has not forsaken us, my friend :D So glad it works for you guys, thanks for the nice feedback! This issue bugged me so much I sorta made it my mission haha. It's fantastic I finally got this thing sorted out with some help from the Gnome NM devs :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Please test with the new patch or patched .deb and follow the steps to set negative ipv4 dns-priority. I (and lead NM-dev Thomas Haller himself) believe this resolves the bug. Thanks, and I hope this helps you all! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
After setting the ipv4.dns-priority of the VPN connection to a negative number and patching the source or installing the conveniently packaged .deb below, you should not experience DNS leaks over NM-VPN. (Output from extended test at https://dnsleaktest.com ) Test complete Query round Progress... Servers found 1 .. 1 2 .. 1 3 .. 1 4 .. 1 5 .. 1 6 .. 1 IP HostnameISP Country 173.239.226.69 ip-69-226-239-173.east.us.northamericancoax.com LogicWeb Inc United States To install the .deb package, simply use: cd ~/Downloads && sudo dpkg -i network-manager_1.4.4-1ubuntu4_amd64.deb NOTE: make sure apt does not replace the package with: sudo apt-mark hold network-manager Make sure to stop all network services and restart the network manager using: sudo service network-manager stop sudo service networking restart sudo service network-manager start To build the source and apply the patch yourself, use the following steps: sudo apt-get build-dep network-manager cd ~/Downloads && mkdir nm-patch && cd nm-patch apt-get source network-manager cd network-manager-1.4.4 cp ~/Downloads/systemd-resolved-dns-priority-fix.patch . patch -p1 < systemd-resolved-dns-priority-fix.patch rm systemd-resolved-dns-priority-fix.patch dpkg-buildpackage -us -uc -b (wait a while, it will take some time to compile) Then install the generated network-manager_1.4.4-1ubuntu .deb package using: cd ../ && sudo dpkg -i ** Attachment added: "network-manager_1.4.4-1ubuntu4_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4900613/+files/network-manager_1.4.4-1ubuntu4_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I have successfully backported Thomas Haller's excellent upstream solution as detailed in https://bugzilla.gnome.org/show_bug.cgi?id=783569 This took some time as things have changed quite a bit upstream, but the patch works on the current zesty 17.04 1.4.4-1ubuntu3.1 network-manager! This is a much better fix than the stopgap SetLinkDomains "." bus call based on link type I included in the previous patch. It should be reviewed for current application/submission to the package maintainers as it is basically a direct backport of Haller's fix merged upstream. NOTE: You MUST set the ipv4.dns-priority to a negative number for the network-manager to unseat DNS configurations for other non-VPN interfaces. This patch allows for correct behavior with negative ipv4 .dns-priority: "Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used." Usage of a negative dns-priority disables DNS configuration for all other interfaces, ensuring there are no DNS leaks over a VPN connection using systemd-resolved. Before Haller's bugfix, this feature did not work with systemd-resolved. To set the ipv4.dns-priority, open the VPN connection profile you have configured through NM like so: sudo nano /etc/NetworkManager/system-connections/ and adding the line (value of -42 recommended by Haller) "dns-priority=-42" so that the file contains something like: [ipv4] dns-priority=-42 dns-search= method=auto Alternatively, use the command sudo nmcli connection modify "" ipv4.dns-priority -42 And you should see that the config file for that connection contains the same line as shown above. After doing so and patching/installing the patched network manager, you should not experience DNS leaks. When I am connected to PIA's servers through network-manager-openvpn using the patched network manager and a negative ipv4.dns-priority set for my VPN connection, the output of systemd-resolved looks like this (notice that the Verizon ISP DNS server was 'unseated' and is absent for the primary wireless link wlo1): Global DNSSEC NTA: 10.in-addr.arpa ...(long list of NTAs omitted)... test Link 4 (tun0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 209.222.18.222 209.222.18.218 Link 2 (wlo1) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no If anyone is curious about support for the routing-only domain in NM, see the following bug https://bugzilla.gnome.org/show_bug.cgi?id=746422 which is about adding support for routing-only domains for systemd- resolved (still work in progress). ** Bug watch added: GNOME Bug Tracker #746422 https://bugzilla.gnome.org/show_bug.cgi?id=746422 ** Patch added: "systemd-resolved-dns-priority-fix.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4900587/+files/systemd-resolved-dns-priority-fix.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Hey all, so it seems like Thomas Haller at the bug thread https://bugzilla.gnome.org/show_bug.cgi?id=783569 may have actually fixed this issue upstream! Not sure how to backport the fix though, I tried and didn't have any luck, so this may be up to the package maintainers. I think this might actually be fixed though! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Unfortunately my patch is not a good solution for upstream application. I agree with what Beniamino Galvani mentioned, that "it is wrong to assume the connection is a VPN based on the link type, since you can have non-VPN tun/tap/gre/gretap connections as well, and they are affected by this patch." However, it seems that this issue with DNS leaks over NM-VPN connections and broken VPN split-horizon DNS using systemd-resolved still exists upstream and doesn't have a good fix. I think this issue needs some attention and work from the Gnome- NM/systemd/Canonical devs, I've reached my limit here. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Actually I take that back. The issue is not fixed by the commit referenced on https://bugzilla.gnome.org/show_bug.cgi?id=783569 as it is already present in the current version of the network-manager. So we still have a major problem folks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
My apologies, it seems like this issue could have already been addressed upstream. See https://bugzilla.gnome.org/show_bug.cgi?id=783569 Anyway, I'll see if I can backport the fix provided there and whether or not it works. Sorry guys :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I have upstreamed the patch at https://bugzilla.gnome.org/show_bug.cgi?id=783569 ! Hopefully this can be incorporated into future releases of network-manager :) ** Bug watch added: GNOME Bug Tracker #783569 https://bugzilla.gnome.org/show_bug.cgi?id=783569 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
No, it's not an upstream patch. My patch can be applied directly to the current source on 17.04 obtained using 'apt-get source network-manager', so that would be network-manager 1.4.4-1ubuntu3 from http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
In reference to John Bedford's comment: >bedfojo (commercial-johnbedford) wrote on 2017-06-06: #57 >Nicholas, thank you very much for your work on this patch. >It works correctly for me: no DNS leak detected by either https://ipleak.net >or >https://dnsleaktest.com for me, when both detected leaks in the unpatched >version. >Running Ubuntu-MATE 17.04. >Could we perhaps get this upstreamed into NM? >bedfojo (commercial-johnbedford) wrote on 2017-06-06: #58 >I should add that I'm using network-manager-openvpn and >network-manager-openvpn-gnome. I think it would be great if we could get this patch upstreamed into the network-manager! I've attached a finalized version of the patch with a more informative / verbose syslog message that also accounts for cisco gre/gretap connections not in #49. Please use this patch when building network-manager for Ubuntu 17.04. I will also attach a .deb build of network-manager for easy installation and testing for anyone interested. So far, this is known to solve dns leaks with network-manager-openvpn but could also solve dns leaks for other VPNs that use TUN, TAP, or Cisco GRE network interfaces through the network-manager. You should now see a message in your syslog when connecting that looks like the following: NetworkManager[32636]: [1496880041.6435] systemd-resolved[0x55cc602ce430]: Link #12 type is VPN TUN or TAP, fixing DNS leak... Make sure to stop apt from replacing the patched .deb using: sudo apt-mark hold network-manager To verify that you are using the 'routing-only domain', use the command systemd-resolve --status and look for the line "DNS Domain: ~." under the VPN link number. Alternatively, check that you are not experiencing DNS leaks using the 'extended test' on https://dnsleaktest.com/ Cheers :) ** Patch added: "resolved-vpn-dns-leak-fix.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4891740/+files/resolved-vpn-dns-leak-fix.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
** Attachment added: "patched network-manager .deb for easy testing on Ubuntu 17.04" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4891741/+files/network-manager_1.4.4-1ubuntu4_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
** Patch removed: "patch for network-manager source" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4889747/+files/resolved-vpn-dns-leak-fix.patch ** Patch removed: "possible cisco network-manager-openconnect-fix" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4890352/+files/resolved-vpn-dns-leak-fix.patch ** Attachment removed: "patched network manager .deb for easy fix installation on Ubuntu 17.04" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4889755/+files/network-manager_1.4.4-1ubuntu3_amd64.deb ** Attachment removed: "updated patched .deb packaged network-manager for easy testing" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4890421/+files/network-manager_1.4.4-1ubuntu3_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Huh, weird, yeah it's quite possible it's a different issue entirely, or a problem related to network-manager-openconnect. Because the routing- only domain is clearly listed as DNS Domain ~. so systemd-resolved should only send queries to the specified dns servers for the interface vpn0. Yeah...not sure sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Huh. No, actually my patch DID work. See the line under vpn0 that says DNS Domain: ~. So the correct bus call was made and all dns queries SHOULD be directed to the link-specified listed DNS servers. Your problem actually appears to be that there are no link-specified dns servers. See the line that says DNS Servers: Please try manually specifying the correct DNS servers in the network-manager-openconnect gui settings. That should fix your problem I believe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Tim, I have a question for you. When you connect through network-manager-openconnect-gnome, and type systemd-resolve --status, what is your link name called? Something like 'tun0' or 'tap1' or the like? Because I've been looking around at the openconnect wiki at http://www.infradead.org/openconnect/building.html, and it seems like openconnect requires tun/tap drivers. So theoretically, it should have worked with the original patch containing just the conditional expression: if (link_type == NM_LINK_TYPE_TUN || link_type == NM_LINK_TYPE_TAP) As in, this should evaluate to true as the link should be of type tun or tap. It seems like the updated patch containing the conditional expression if (link_type == NM_LINK_TYPE_TUN || link_type == NM_LINK_TYPE_TAP || link_type == NM_LINK_TYPE_GRE || link_type == NM_LINK_TYPE_GRETAP) might, however, help address users of network-manager-vpnc/network-manager-vpnc-gnome. If anyone uses network-manager-vpnc/network-manager-vpnc-gnome, let me know if the newer patch containing the cases for NM_LINK_TYPE_GRE and NM_LINK_TYPE_GRETAP fixes DNS leaks for you on a Cisco PPTP/IPsec VPN. I am unable to test this out as I don't have access to any such Cisco VPN services. Anyway, if the network manager doesn't correctly register the openconnect interface as being link type TUN or TAP, I don't really know how to fix it as that could be a problem on network-manager- openconnect's end or the result of some way it doesn't properly notify the network manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Jordi, Sure thing, glad I could help. :) I wonder if somebody can figure out how to help Tim with network-manager-openconnect. I tried adding two more conditions for cisco vpn gre connections but apparently it didn't work or those aren't the kind of links used. Not sure how to address that because the innards of network-manager and how it interacts with plugins is fairly complex, but maybe someone could modify the patch to account for that. For anyone just using network-manager-openvpn, the first patch and .deb uploaded are all that is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Sorry to here that, I'm frankly not sure what to do about that then :/ At the very least the original patch fixes stuff for openvpn, which is good. Perhaps someone else could figure out the cisco openconnect thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Anyone using Cisco PPTP/IPsec/openconnect VPN, please test the network manager with the aforementioned patch or with the updated built .deb provided here. The updated patch should address more types of VPN links. Thanks! ** Attachment added: "updated patched .deb packaged network-manager for easy testing" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4890421/+files/network-manager_1.4.4-1ubuntu3_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Tim Shannon, from the comment about network-manager-openconnect-gnome, please use this updated patch to build the network manager. I added conditions for the cisco GRE and GRETAP link types, see https://en.wikipedia.org/wiki/Generic_Routing_Encapsulation and http://www.cisco.com/c/en/us/td/docs/security/security_management/cisco_security_manager/security_manager/4-4/user/guide/CSMUserGuide_wrapper/vpgredm.html#69194 so I think this might fix the issue connecting through network-manager-openconnect-gnome Please build the network-manager with the following patch and see if DNS leaks are fixed over cisco openconnect VPN links. Thanks! ** Patch added: "possible cisco network-manager-openconnect-fix" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4890352/+files/resolved-vpn-dns-leak-fix.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Yeah, apologies as I'm not sure what link type that openconnect uses / how to identify an openconnect link. It would be a simple matter to add a conditional for that in the file I patched, please try that. For now my patch only addresses openvpn tap or tun links, but I'm sure it could be expanded if possible. Anyone using network-manager-openvpn please test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
>From the Debian man pages, it seems like this is not in fact a problem of systemd itself, as it allows for domain routing exclusively for dns servers on a single interface using the routing-only domain. My patch effectively just tells the NetworkManager to make a systemd bus call for the routing-only domain when the connection is a vpn tun or tap link. In fact, this feature of systemd, the routing-only domain, is a marked improvement from the glibc API, which has no equivalent concept of dns servers limited to a system link. The SetLinkDomains method of the systemd-resolved API allows for this behavior. >From SYSTEMD.NETWORK(5): "The "routing-only" domain "~." (the tilde indicating definition of a routing domain, the dot referring to the DNS root domain which is the implied suffix of all valid DNS names) has special effect. It causes all DNS traffic which does not match another configured domain routing entry to be routed to DNS servers specified for this interface. This setting is useful to prefer a certain set of DNS servers if a link on which they are connected is available. This setting is read by systemd-resolved.service(8). "Search domains" correspond to the domain and search entries in resolv.conf(5). Domain name routing has no equivalent in the traditional glibc API, which has no concept of domain name servers limited to a specific link." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685391] Re: DNS leak in Xubuntu 17.04
*** This bug is a duplicate of bug 1624317 *** https://bugs.launchpad.net/bugs/1624317 For a Network Manager GUI fix, please see my patch towards the bottom of the bug report https://bugs.launchpad.net/bugs/1624317 No more DNS leaks through the openvpn network-manager gui! Please let me know if this works for you, cheers :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685391 Title: DNS leak in Xubuntu 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1685391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I can confirm this works for multiple vpn connections and after wakeup from system suspend on Ubuntu 17.04. I encourage you to install the patched .deb or follow the instructions to build it from source and see for yourself. I'm honestly so glad this fixes dns leaks for using openvpn through the network manager gui on Ubuntu that I'm switching my primary machine to 17.04. :) Please let me know if this resolves your problems with DNS leaks using a vpn via the network manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
The actual patch is attached above and can be applied to the source code which you can build yourself. But for your convenience, I have attached the .deb file below: ** Attachment added: "patched network manager .deb for easy fix installation on Ubuntu 17.04" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4889755/+files/network-manager_1.4.4-1ubuntu3_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Please note that this patch and fix only works for Ubuntu 17.04 which relies on systemd-resolved as a DNS/DNSSEC stub resolver, as well as an LLMNR resolver. You also need to be using a network-manager plugin like network-manager-openvpn-gnome. Install and configure an openvpn connection after going 'sudo apt-get install network-manager- openvpn-gnome', importing a config file, connecting (if possible), and observing the fact that there are DNS leaks (queries WILL be routed to your ISP) with online tools like those at https://dnsleaktest.com. Otherwise, just know that systemd-resolved naturally leaks DNS queries over all configured domains on all interfaces by design unless a specific system bus call is made. In this case, the SetLinkDomains(in i ifindex, in a(sb) domains) method, if passed the interface index followed by an array containing the "routing-only" domain "~." (see https://manpages.debian.org/testing/systemd/systemd.network.5.en.html) and the boolean true. But enough with the technical details, lets move on to the fix! First, make sure you have all necessary packages to build the network manager, install with: sudo apt update sudo apt-get build-dep network-manager cd ~/Documents mkdir nm && cd nm apt-get source network-manager cd network-manager-1.4.4/ Copy the patch file into the network-manager-1.4.4 directory: cp ~/Downloads/resolved-vpn-dns-leak-fix.patch . Apply the patch with: patch -p1 < resolved-vpn-dns-leak-fix.patch Remove patch from source directory before compilation: rm resolved-vpn-dns-leak-fix.patch Compile and build .deb package for installation (this will take a while): dpkg-buildpackage -us -uc -b The compiled .debs should be in the parent directory you created nm: cd ../ First, stop all network services: sudo service network-manager stop sudo service networking stop Install just the patched network manager (the other .debs are not necessary): sudo dpkg -i network-manager_1.4.4-1ubuntu3_amd64.deb Bring network services back up: sudo service networking start sudo service network-manager start Connect to standard openvpn via network-manager-openvpn GUI (or other plugin) Search the syslog for something like: NetworkManager[876]: [1496716774.9849] systemd-resolved[0x55b0132ec2b0]: Link type is VPN TUN or TAP, fixing DNS leak... and verify that the VPN link (for example tun0) includes the descriptor: DNS Domain: ~. using the command: systemd-resolve --status When compiling network manager, several bogus links are created and will show up when you type 'systemd-resolve --status', don't worry they will disappear once you reboot. Then open your browser, navigate to https://dnsleaktest.com and select Extended test You should only see your VPN provider's DNS servers. For example, with PIA you should see something like: Test complete Query round Progress... Servers found 1 .. 1 2 .. 1 3 .. 1 4 .. 1 5 .. 1 6 .. 1 IP HostnameISP Country 173.239.220.5 ip-5-220-239-173.east.us.northamericancoax.com GoLightSpeed United States Now, to prevent Ubuntu apt from replacing your patched, VPN-DNS-leak- free version of network manager that relies on systemd-resolved, use the command: sudo apt-mark hold network-manager Thats all, you're done. Congrats, no DNS leaks on Ubuntu 17.04! I hope that I was able to make your life easier and more secure using openvpn or other vpn services through the built-in GUI for the Gnome NetworkManager on Ubuntu 17.04 :) (Side note: I am a college student and C/C++ dev who loves Ubuntu <3 Also, this took quite a bit of research on the GLib API, systemd-resolved API, and much much tracing using our good friend 'grep -r' for built in functions and enums of the Gnome network manager itself. No additional compiler warnings are generated, the patch conforms to the C90 standard, and the syntax style used throughout the network manager source code was maintained.) I will attach the small text patch generated using 'diff -u' along with the patched generated .deb file for your convenience. Cheers, and I hope this helps you all! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
** Patch added: "patch for network-manager source" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4889747/+files/resolved-vpn-dns-leak-fix.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652525] Re: DNS leak in ubuntu 16.10
Sadly, the option block-outside-dns is only supported on Windows clients. Which is a real shame, because systemd-resolved is leaking DNS queries everywhere by design. This is a problem with the hardcoded design of the gnome network manager integrating (or rather...not integrating) with systemd-resolved. I attempted to understand GIO proxy bus calls but honestly patching the network manager is beyond my capabilities. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652525 Title: DNS leak in ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1652525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694561] Re: kernel panic attempting to boot kernel 4.12-rc3
I am unable to run apport-collect running 4.12-rc3, because I cannot actually boot my computer (an immediate kernel panic occurs, as evidenced by adding the output from earlyprintk=efi), so I'm marking this bug as confirmed. Please also see relevant discussion about this issue on the Linux Kernel mailing list: http://lkml.iu.edu/hypermail/linux/kernel/1705.3/04549.html ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694561 Title: kernel panic attempting to boot kernel 4.12-rc3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694561] [NEW] kernel panic attempting to boot kernel 4.12-rc3
Public bug reported: I have an HP Spectre x360 Convertible laptop with an Intel 5500U SoC. In short, I am completely unable to boot kernel 4.12-rc3, even though I could boot from 4.12-rc2 perfectly fine. The loading screen does not appear at all, instead GRUB remains stuck on "Loading initial ramdisk ...". Please help. I don't know how to identify what is wrong because I am completely unable to boot the OS to begin with. Needless to say, this is a major problem. Here is my hardware: H/W path Device Class Description system HP Spectre x360 Convertible (N5R94UA) /0bus802D /0/0 memory 64KiB BIOS /0/10 memory 32KiB L1 cache /0/11 memory 32KiB L1 cache /0/12 memory 256KiB L2 cache /0/13 memory 4MiB L3 cache /0/14 processor Intel(R) Core(TM) i7-5500U CPU @ 2.40GH /0/16 memory 8GiB System Memory /0/16/0 memory 4GiB Row of chips Synchronous 1600 MHz /0/16/1 memory 4GiB Row of chips Synchronous 1600 MHz /0/100bridge Broadwell-U Host Bridge -OPI /0/100/2 displayBroadwell-U Integrated Graphics /0/100/3 multimedia Broadwell-U Audio Controller /0/100/14 busWildcat Point-LP USB xHCI Controller /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/1 input USB Receiver /0/100/14/0/3 multimedia HP Truevision Full HD /0/100/14/0/4 input Touchscreen /0/100/14/0/5 input ITE Device(8350) /0/100/14/0/7 communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/16 communication Wildcat Point-LP MEI Controller #1 /0/100/1c bridge Wildcat Point-LP PCI Express Root Port /0/100/1c/0 genericRTS5227 PCI Express Card Reader /0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port /0/100/1c.2/0 wlo1 networkWireless 7265 /0/100/1f bridge Wildcat Point-LP LPC Controller /0/100/1f.2 storageWildcat Point-LP SATA Controller [AHCI /0/100/1f.3 busWildcat Point-LP SMBus Controller /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 512GB SAMSUNG MZNTE512 /0/1/0.0.0/1 /dev/sda1 volume 449MiB Windows NTFS volume /0/1/0.0.0/2 /dev/sda2 volume 99MiB Windows FAT volume /0/1/0.0.0/3 /dev/sda3 volume 15MiB reserved partition /0/1/0.0.0/4 /dev/sda4 volume 15EiB Windows FAT volume /0/1/0.0.0/5 /dev/sda5 volume 838MiB Windows NTFS volume /0/1/0.0.0/6 /dev/sda6 volume 146GiB Windows NTFS volume /0/1/0.0.0/7 /dev/sda7 volume 89GiB EXT4 volume /0/1/0.0.0/8 /dev/sda8 volume 8099MiB Linux swap volume /1power PK03056XL ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694561 Title: kernel panic attempting to boot kernel 4.12-rc3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694561] Re: kernel panic attempting to boot kernel 4.12-rc3
It appears a kernel panic is happening immediately while attempting to boot 4.12-rc3, it doesn't happen on 4.12-rc2. Adding earlyprintk=efi to the grub command line options, I get the following message (which explains why the bootloader stops at 'loading initial ramdisk...'): This was meticulously copied from a photo of a GRUB screen, this change is undoubtedly the culprit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/arch/x86/mm/pat.c?id=v4.12-rc3=v4.12-rc2 (direct commit at) https://github.com/torvalds/linux/commit/cbed27cdf0e3f7ea3b2259e86b9e34df02be3fe4 [0.00] Kernel panic - not syncing: x86/PAT: PAT enabled, but not supported by secondary CPU [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.12.0-041200rc3-generic #201705282131 [0.00] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [0.00] Call Trace: [0.00] dump_stack+0x63/0x8d [0.00] panic+0xe4/0x22d [0.00] pat_init+0x13d/0x140 [0.00] generic_set_all+0x1ab/0x300 [0.00] mtrr_bp_init+0x1e5/0x227 [0.00] setup_arch+0x53a/0xca8 [0.00] ? printk+0x52/0x6e [0.00] ? early_idt_handler_array+0x120/0x120 [0.00] start_kernel+0xb7/0x46c [0.00] ? early_idt_handler_array+0x120/0x120 [0.00] x86_64_start_reservations+0x29/0x2b [0.00] x86_64_start_kernel+0x154/0x177 [0.00] secondary_startup_64+0x9f/0x9f [0.00] ---[ end Kernel panic - not syncing: x86/PAT: PAT enabled, but not supported by secondary CPU [0.00] This change causes a kernel panic on my Intel 5500U processor, I literally cannot boot my computer. This commit results in a serious regression for multicore Intel CPUs, 4.12-rc3 and drm-tip result in an immediate kernel panic attempting to boot. This is unacceptable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694561 Title: kernel panic attempting to boot kernel 4.12-rc3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
Seems this was resolved in 4.12-rc2, mounting ntfs-3g volumes is fine,
doesn't generate a kernel warning! It was fixed in fs/fuse/inode.c at
https://github.com/torvalds/linux/commit/69c8ebf83213e6165b13d94ec599b861467ee2dc
with
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 5a1b58f..65c8837 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -975,8 +975,15 @@ static int fuse_bdi_init(struct fuse_conn *fc, struct
super_block *sb)
int err;
char *suffix = "";
- if (sb->s_bdev)
+ if (sb->s_bdev) {
suffix = "-fuseblk";
+ /*
+* sb->s_bdi points to blkdev's bdi however we want to redirect
+* it to our private bdi...
+*/
+ bdi_put(sb->s_bdi);
+ sb->s_bdi = _backing_dev_info;
+ }
err = super_setup_bdi_name(sb, "%u:%u%s", MAJOR(fc->dev),
MINOR(fc->dev), suffix);
if (err)
** No longer affects: fuse (Ubuntu)
** No longer affects: ntfs-3g (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692143
Title:
fs changes in kernel 4.12 break mount of ntfs-3g, possible data
corruption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
This was fixed in 4.12-rc2! ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
Okay, so the warning is clearly being generated by the WARN_ON function in fs/super.c. I realize I could disable the warning, but that sounds like a bad idea. One question though, why would we be verifying if sb->s_bdi is equal to the address of some "struct backing_dev_info noop_backing_dev_info" from either the files /include/linux/backing-dev.h or /mm/backing-dev.c (Found references to definition of this struct in these two file using the power of grep -rl) in fs/super.c on line 1281, when we reassign it anyway to a local variable bdi right after? In other words, IS there something going wrong here, or is this warning insignificant and should be removed? 1281: WARN_ON(sb->s_bdi != _backing_dev_info); 1282: sb->s_bdi = bdi; Also see bug report I filed about this problem at https://bugzilla.kernel.org/show_bug.cgi?id=195809 ** Bug watch added: Linux Kernel Bug Tracker #195809 https://bugzilla.kernel.org/show_bug.cgi?id=195809 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1692143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879845/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1692143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879867/+files/version.log ** Also affects: ntfs-3g (Ubuntu) Importance: Undecided Status: New ** Also affects: fuse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1692143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879846/+files/lspci-vvnn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1692143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879847/+files/uname-a.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1692143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692143] [NEW] fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
Public bug reported: Mounting any ntfs partition or ntfs-formatted external drive in kernel 4.12 results in a critical kernel warning. Possible data corruption could happen, as the drive must be forcibly unmounted. The kernel warning appears in the syslog literally every single time, this is a very reproducible bug. The same warning/stack trace all pointing to the function super_setup_bdi_name in /linux/fs/super.c:1281 along with related calls to fuse functions appears in Ubuntu 16.04 LTS, Ubuntu 16.10. and Ubuntu 17.04. Here I will only include the information relevant to my installation of 16.04.2 LTS. This seems rather critical, as ntfs is one of the only suitable formats supported by (and shareable between) Windows and Linux, and I worry that possible data corruption could be happening. [9.574893] [ cut here ] [9.574898] WARNING: CPU: 0 PID: 608 at /home/kernel/COD/linux/fs/super.c:1281 super_setup_bdi_name+0xcf/0xe0 [9.574899] Modules linked in: hp_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul snd_soc_rt298 crc32_pclmul ghash_clmulni_intel pcbc iwlmvm snd_hda_codec_hdmi mac80211 snd_hda_intel snd_hda_codec snd_soc_rt286 snd_hda_core snd_soc_ssm4567 aesni_intel snd_soc_rl6347a snd_hwdep iwlwifi aes_x86_64 crypto_simd snd_soc_core rtsx_pci_ms cfg80211 glue_helper memstick snd_compress elan_i2c snd_pcm_dmaengine ac97_bus cryptd intel_cstate intel_rapl_perf snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq uvcvideo joydev videobuf2_vmalloc input_leds videobuf2_memops btusb hid_sensor_incl_3d videobuf2_v4l2 hid_sensor_rotation btrtl videobuf2_core btbcm btintel hid_sensor_gyro_3d hid_sensor_accel_3d videodev hid_sensor_magn_3d hid_sensor_trigger [9.574937] bluetooth industrialio_triggered_buffer hid_sensor_iio_common hid_multitouch media lpc_ich ecdh_generic snd_seq_device snd_timer snd mei_me soundcore shpchp mei hp_accel lis3lv02d snd_soc_sst_acpi dw_dmac hp_wireless snd_soc_sst_match input_polldev 8250_dw spi_pxa2xx_platform dw_dmac_core i2c_designware_platform mac_hid i2c_designware_core intel_vbtn sparse_keymap acpi_als acpi_pad kfifo_buf industrialio parport_pc ppdev lp parport autofs4 hid_logitech_hidpp hid_sensor_custom hid_sensor_hub hid_logitech_dj usbhid i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm psmouse libahci rtsx_pci wmi video sdhci_acpi i2c_hid sdhci hid [9.574972] CPU: 0 PID: 608 Comm: mount.ntfs-3g Not tainted 4.12.0-041200rc1-generic #201705131731 [9.574972] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [9.574974] task: 9cef7d14c380 task.stack: aff881488000 [9.574976] RIP: 0010:super_setup_bdi_name+0xcf/0xe0 [9.574977] RSP: 0018:aff88148bc50 EFLAGS: 00010283 [9.574978] RAX: RBX: 9cef7b3d2400 RCX: 0002 [9.574979] RDX: 0001 RSI: fe01 RDI: ad7d81bb [9.574980] RBP: aff88148bcd0 R08: 9cef8233c6f8 R09: [9.574981] R10: f28cc8f45c00 R11: R12: 9cef7d277000 [9.574982] R13: ae2d914c R14: aff88148bce0 R15: 9cef7b2c3200 [9.574983] FS: 7f2025fa8700() GS:9cef8ec0() knlGS: [9.574984] CS: 0010 DS: ES: CR0: 80050033 [9.574985] CR2: 5617f917e058 CR3: 00024258e000 CR4: 003406f0 [9.574986] Call Trace: [9.574990] ? kmem_cache_alloc_trace+0x181/0x190 [9.574993] fuse_fill_super+0x3b3/0x6a0 [9.574995] ? vsnprintf+0x24b/0x4d0 [9.574997] ? snprintf+0x45/0x70 [9.574998] mount_bdev+0x178/0x1b0 [9.575000] ? mount_bdev+0x178/0x1b0 [9.575001] ? fuse_get_root_inode+0x70/0x70 [9.575003] fuse_mount_blk+0x15/0x20 [9.575005] mount_fs+0x38/0x140 [9.575008] vfs_kern_mount+0x67/0x110 [9.575009] do_mount+0x1e1/0xca0 [9.575011] ? __check_object_size+0xb3/0x190 [9.575013] ? _copy_from_user+0x21/0x70 [9.575015] ? kmem_cache_alloc_trace+0x142/0x190 [9.575016] SyS_mount+0x83/0xd0 [9.575019] entry_SYSCALL_64_fastpath+0x1e/0xa9 [9.575020] RIP: 0033:0x7f2025679faa [9.575021] RSP: 002b:7fffa89e0358 EFLAGS: 0246 ORIG_RAX: 00a5 [9.575023] RAX: ffda RBX: RCX: 7f2025679faa [9.575024] RDX: 5633569a95a0 RSI: 5633569a8430 RDI: 5633569a8760 [9.575025] RBP: 7fffa89df0f0 R08: 5633569a8620 R09: 0028 [9.575026] R10: 000e R11: 0246 R12: 5633569a8430 [9.575026] R13: 5633560b287f R14: 7fffa89df238 R15: 0001 [9.575028] Code: a0 65 48 33 0c 25 28 00 00 00 75 2a 48 83 c4 58 5b 41 5a 41 5c 41 5d 41 5e 5d c3 48 89 df 89 45 84 e8 f6 10 f9 ff 8b 45 84 eb d2 <0f> ff eb c6 b8 f4 ff ff ff eb c7 e8 01 d5 e3 ff 90 0f 1f
[Bug 1681295] Re: Problem in nm-openvpn-service.c, openvpn connection fails after key renegotiation because --auth-user-pass is passed with --auth-nocache.
Thanks for the confirmation Will, glad to see that it works. And yeah I think this bug should be marked urgent because without the patch, my vpn connection drops in the same manner every ten minutes or so. The rationale behind not passing auth-nocache seems pretty clear to me based on the openvpn man pages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681295 Title: Problem in nm-openvpn-service.c, openvpn connection fails after key renegotiation because --auth-user-pass is passed with --auth-nocache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681295] Re: Problem in nm-openvpn-service.c, openvpn connection fails after key renegotiation because --auth-user-pass is passed with --auth-nocache.
** Summary changed: - Problem in network-manager-openvpn, openvpn fails during and after downloads. + Problem in nm-openvpn-service.c, openvpn connection fails after key renegotiation because --auth-user-pass is passed with --auth-nocache. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681295 Title: Problem in nm-openvpn-service.c, openvpn connection fails after key renegotiation because --auth-user-pass is passed with --auth-nocache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681295] Re: Problem in network-manager-openvpn, openvpn fails during and after downloads.
** Description changed: So I've been using OpenVPN through the network-manager-openvpn package integrated into the network manager GUI. I experienced an odd problem where consistently, during or after downloading (in this case, I tested by just downloading the kernel tarball from kernel.org repeatedly, which is around 90MB) Every single time, without fail, the openvpn client would fail and my connection would go dead. To reconnect, I would have to manually restart the network manager. Now, I played around with .conf files and the CLI openvpn client and noticed EXACTLY the same behavior happening. I eventually arrived to the conclusion that the flag or option "auth-nocache" would cause a connection reset after or during downloads and streaming. I then got to reading the openvpn man pages and I stumbled across this message (you can easily find it by going 'man openvpn | grep nocache') about the guaranteed failure of key renegotiation if auth-user-pass and auth-nocache were used together: " Further, using --daemon together with --auth-user-pass (entered - on console) and --auth-nocache will fail as soon as key renego‐ - tiation (and reauthentication) occurs." + on console) and --auth-nocache will fail as soon as key renego‐ + tiation (and reauthentication) occurs." When I removed auth-user-pass from my .conf files, the problem went away. Then I wondered. Now what if...network-manager-openvpn was actually passing both flags to openvpn? Then I downloaded the source tarball and found that indeed, this exact thing is happening on a SINGLE line. See line 1380 of network-manager-openvpn-1.1.93/src/nm-openvpn-service.c "add_openvpn_arg (args, "--auth-nocache");" So I decided to comment out that single line. I then rebuilt the - packages network-manager-openvpn and network-manager-openvpn using + packages network-manager-openvpn and network-manager-openvpn-gnome using 'dpkg-buildpackage -us -uc -nc', installed them, and tested downloading the source kernel repeatedly to see if the connection would hold. It does! Literally commenting out ONE line fixed weeks worth of extreme annoyance repeatedly reconnecting to my vpn. This issue is rather annoying and needs to be fixed so openvpn doesn't keep cutting out. I've attached a patch for the source. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681295 Title: Problem in network-manager-openvpn, openvpn fails during and after downloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636395] Re: dnsmasq not working with OpenVPN
Okay so I have found the issue pertaining to dns resolution on Ubuntu 16.04.2! There is a critical bug in the package dnsmasq-base here: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776 The fix hasn't yet been applied to the current version of dnsmasq-base. This time I have all the dependencies on 1.2.6 at their newest version and installing the patched .deb version provided by Harald Rudell fixes DNS name resolution on wakeup/suspend and with restart of the network manager, all while cooperating with openvpn. I hope this helps anyone on 16.04.2 LTS! wget https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+attachment/4780245/+files /dnsmasq-base_2.76-4ubuntu1FIX1639776ubuntu1_amd64.deb sudo dpkg -i dnsmasq-base_2.76-4ubuntu1FIX1639776ubuntu1_amd64.deb This appears to have actually worked, and is much better than using dnscrypt-proxy (which I have found to be incredibly slow) or holding back a bunch of packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636395 Title: dnsmasq not working with OpenVPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1636395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681295] Re: Problem in network-manager-openvpn, openvpn fails during and after downloads.
Additional generated built patched package network-manager-openvpn-gnome ** Attachment added: "network-manager-openvpn-gnome_1.1.93-1ubuntu1.1_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+attachment/4859325/+files/network-manager-openvpn-gnome_1.1.93-1ubuntu1.1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681295 Title: Problem in network-manager-openvpn, openvpn fails during and after downloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681295] Re: Problem in network-manager-openvpn, openvpn fails during and after downloads.
Built patched package. ** Attachment added: "network-manager-openvpn_1.1.93-1ubuntu1.1_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+attachment/4859324/+files/network-manager-openvpn_1.1.93-1ubuntu1.1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681295 Title: Problem in network-manager-openvpn, openvpn fails during and after downloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681295] [NEW] Problem in network-manager-openvpn, openvpn fails during and after downloads.
Public bug reported: So I've been using OpenVPN through the network-manager-openvpn package integrated into the network manager GUI. I experienced an odd problem where consistently, during or after downloading (in this case, I tested by just downloading the kernel tarball from kernel.org repeatedly, which is around 90MB) Every single time, without fail, the openvpn client would fail and my connection would go dead. To reconnect, I would have to manually restart the network manager. Now, I played around with .conf files and the CLI openvpn client and noticed EXACTLY the same behavior happening. I eventually arrived to the conclusion that the flag or option "auth-nocache" would cause a connection reset after or during downloads and streaming. I then got to reading the openvpn man pages and I stumbled across this message (you can easily find it by going 'man openvpn | grep nocache') about the guaranteed failure of key renegotiation if auth-user-pass and auth-nocache were used together: " Further, using --daemon together with --auth-user-pass (entered on console) and --auth-nocache will fail as soon as key renego‐ tiation (and reauthentication) occurs." When I removed auth-user-pass from my .conf files, the problem went away. Then I wondered. Now what if...network-manager-openvpn was actually passing both flags to openvpn? Then I downloaded the source tarball and found that indeed, this exact thing is happening on a SINGLE line. See line 1380 of network-manager-openvpn-1.1.93/src/nm-openvpn-service.c "add_openvpn_arg (args, "--auth-nocache");" So I decided to comment out that single line. I then rebuilt the packages network-manager-openvpn and network-manager-openvpn using 'dpkg-buildpackage -us -uc -nc', installed them, and tested downloading the source kernel repeatedly to see if the connection would hold. It does! Literally commenting out ONE line fixed weeks worth of extreme annoyance repeatedly reconnecting to my vpn. This issue is rather annoying and needs to be fixed so openvpn doesn't keep cutting out. I've attached a patch for the source. ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: network-manager network-manager-openvpn openvpn ** Patch added: "The following patch removes the single offending line which causes this issue." https://bugs.launchpad.net/bugs/1681295/+attachment/4859305/+files/nm-openvpn-service-fix.patch ** Also affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** No longer affects: network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681295 Title: Problem in network-manager-openvpn, openvpn fails during and after downloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 Okay so I have found the issue pertaining to dns resolution on Ubuntu 16.04.2! There is a critical bug in the package dnsmasq-base here: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776 The fix hasn't yet been applied to the current version of dnsmasq-base. This time I have all the dependencies on 1.2.6 at their newest version and installing the patched .deb version provided by Harald Rudell fixes DNS name resolution on wakeup/suspend and with restart of the network manager, all while cooperating with openvpn. I hope this helps anyone on 16.04.2 LTS! wget https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+attachment/4780245/+files/dnsmasq-base_2.76-4ubuntu1FIX1639776ubuntu1_amd64.deb sudo dpkg -i dnsmasq-base_2.76-4ubuntu1FIX1639776ubuntu1_amd64.deb This appears to have actually worked, and is much better than using dnscrypt-proxy (which I have found to be incredibly slow) or holding back a bunch of packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677175] Re: network-manager 1.2.6 won't connect to vpn and displays false connected message
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1677175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
Well, scratch that hope and consider me mistaken about Goth Queen's workaround. It appears that manually setting a fixed DNS server DOES allow for successful reconnect when the network manager is restarted (whereas before it wouldn't reconnect period), but just like this bug https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241 name resolution (not using the dnscrypt-proxy service, just a fixed DNS address) fails after waking up from suspend for some frustrating, arcane reason. I have downgraded the following packages: (credit to Kostadin Stoilov) sudo apt install network-manager=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm-glib-vpn1=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm-glib4=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm0=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm-util2=1.2.2-0ubuntu0.16.04.4 sudo apt install resolvconf=1.78ubuntu2 and held them in place with 'sudo apt-mark hold' for the time being, as there appears to be a critical flaw in the updated versions of network- manager and possibly resolv-conf and dnsmasq. I suppose we just have to wait until something is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
Oops, Goth Queen actually provided a solution earlier, it was just difficult for me to understand at the time. Enter whatever fixed DNS server you want and set 'Automatic (DHCP) addresses only' under IPv4 Settings in network-manager for the default network connection. So just manually entering in your VPN's DNS server (for PIA it's 209.222.18.222) or installing dnscrypt-proxy and choosing 127.0.0.2 as the server both work. This seems an adequate workaround for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
Okay so since resolvconf and dmasq are not cooperating, I have resorted to using dnscrypt-proxy. Credit to QkiZ, the dnscrypt-proxy service works EVERY TIME and ignores the (completely broken) DNS resolution of dnsmasq and resolvconf. Even with the newest version of network-manager (1.2.6) on 16.04 LTS and all its dependencies: network-manager libnm-glib-vpn1 libnm-glib4 libnm0 libnm-util2 No more DNS resolution issues! To apply this workaround (which actually also offers some security benefits against DNS leakage), use: sudo apt install dnscrypt-proxy In the network manager, select "Edit Connections", select the primary (non-VPN) network you use, click on the "IPv4 Settings" tab, change the "Method" tab to "Automatic (DHCP) addresses only", then add 127.0.0.2 to the "DNS servers:" box. Save your changes, then restart the connection by disabling and enabling networking. Now go to https://www.opendns.com/welcome/ and you should see a nice check mark. Now, your network connection and VPN should work (meaning DNS resolution won't break on you) every single time you wake up from suspend or use sudo service network-manager restart And if for some odd reason it's slow just restart the network manager repeatedly by aliasing that to something like alias nm-restart='sudo service network-manager restart' in your ~/.bash_aliases file. I know, annoying but at least DNS resolution actually works and the computer doesn't have to be literally restarted to connect to the internet. This isn't intended to be a fix, just a possible alternative for those of us who experience total DNS resolution failure using a vpn on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636395] Re: dnsmasq not working with OpenVPN
Credit to QkiZ, the dnscrypt-proxy service works EVERY TIME and ignores the (completely broken) DNS resolution of dnsmasq and resolvconf. Even with the newest version of network-manager (1.2.6) on 16.04 LTS and all its dependencies: network-manager libnm-glib-vpn1 libnm-glib4 libnm0 libnm-util2 No more DNS resolution issues! To apply this workaround (which actually also offers some security benefits against DNS leakage), use: sudo apt install dnscrypt-proxy In the network manager, select "Edit Connections", select the primary (non-VPN) network you use, click on the "IPv4 Settings" tab, change the "Method" tab to "Automatic (DHCP) addresses only", then add 127.0.0.2 to the "DNS servers:" box. Save your changes, then restart the connection by disabling and enabling networking. Now go to https://www.opendns.com/welcome/ and you should see a nice check mark. Now, your network connection and VPN should work (meaning DNS resolution won't break on you) every single time you wake up from suspend or use sudo service network-manager restart Good stuff! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636395 Title: dnsmasq not working with OpenVPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1636395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
I have downgraded both the network-manager and resolvconf package but I still experience complete DNS resolution failure randomly, where restarting the network manager has no effect and I cannot connect to the internet. The only way to get DNS working again is to completely reboot the computer, which is a massive pain and shouldn't happen. I need openvpn to connect to my university's ssh server at home. LTS was working totally fine for me for months but now I have run into this massively annoying issue. Killing the dnsmasq process has no effect for me. Downgrading the two packages makes it so that my vpn connection *sometimes* works but without fail, I eventually have to force restart my computer to connect to the internet at all. This is intolerable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677175] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1677175/+attachment/4850128/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677175] Re: network-manager 1.2.6 won't connect to vpn and displays false connected message
apport information ** Tags added: apport-collected xenial ** Description changed: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2017-03-19 (10 days ago) + InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) + Package: network-manager 1.2.2-0ubuntu0.16.04.4 + PackageArchitecture: amd64 + Tags: xenial + Uname: Linux 4.9.16 x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1677175/+attachment/4850127/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677175] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1677175/+attachment/4850129/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677175] [NEW] network-manager 1.2.6 won't connect to vpn and displays false connected message
Public bug reported: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: network-manager openvpn vpn ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
Yes, this problem most definitely occurs with the Yakkety proposed kernel, I tried using the most recent build of 16.10 that comes with 4.8, and the graphical problems persist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627408 Title: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
All kernels after 4.7.4 have this exact same issue with Broadwell integrated graphics, including the official 4.8 release and the previous rc builds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627408 Title: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
** Description changed: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. + + I am running Ubuntu 16.04.1 LTS on an HP Spectre x360 4102dx with an Intel + Broadwell 5500U core i7 processor with integrated intel Broadwell GT2 graphics ** Description changed: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. I am running Ubuntu 16.04.1 LTS on an HP Spectre x360 4102dx with an Intel Broadwell 5500U core i7 processor with integrated intel Broadwell GT2 graphics + + Here is my system configuration: + + H/W path Device Class Description + + system HP Spectre x360 Convertible (N5R94UA#AB + /0bus802D + /0/0 memory 64KiB BIOS + /0/10 memory 32KiB L1 cache + /0/11 memory 32KiB L1 cache + /0/12 memory 256KiB L2 cache + /0/13 memory 4MiB L3 cache + /0/14 processor Intel(R) Core(TM) i7-5500U CPU @ 2.40GH + /0/16 memory 8GiB System Memory + /0/16/0 memory 4GiB Row of chips Synchronous 1600 MHz + /0/16/1 memory 4GiB Row of chips Synchronous 1600 MHz + /0/100bridge Broadwell-U Host Bridge -OPI + /0/100/2 displayBroadwell-U Integrated Graphics + /0/100/3 multimedia Broadwell-U Audio Controller + /0/100/14 busWildcat Point-LP USB xHCI Controller + /0/100/14/0usb2 busxHCI Host Controller + /0/100/14/1usb1 busxHCI Host Controller + /0/100/14/1/1 input USB Receiver + /0/100/14/1/3 multimedia HP Truevision Full HD + /0/100/14/1/4 input Touchscreen + /0/100/14/1/5 input ITE Device(8350) + /0/100/14/1/7 communication Bluetooth wireless interface + /0/100/16 communication Wildcat Point-LP MEI Controller #1 + /0/100/1b multimedia Wildcat Point-LP High Definition Audio + /0/100/1c bridge Wildcat Point-LP PCI Express Root Port + /0/100/1c/0 genericRTS5227 PCI Express Card Reader + /0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port + /0/100/1c.2/0 wlo1 networkWireless 7265 + /0/100/1f bridge Wildcat Point-LP LPC Controller + /0/100/1f.2 storageWildcat Point-LP SATA Controller [AHCI + /0/100/1f.3 busWildcat Point-LP SMBus Controller + /0/1 scsi0 storage + /0/1/0.0.0 /dev/sda disk 512GB SAMSUNG MZNTE512 + /0/1/0.0.0/1 /dev/sda1 volume 449MiB Windows NTFS volume + /0/1/0.0.0/2 /dev/sda2 volume 98MiB Windows FAT volume + /0/1/0.0.0/3 /dev/sda3 volume 15MiB reserved partition + /0/1/0.0.0/4 /dev/sda4 volume 15EiB Windows FAT volume + /0/1/0.0.0/5 /dev/sda5 volume 807MiB Windows NTFS volume + /0/1/0.0.0/6 /dev/sda6 volume 97GiB Windows NTFS volume + /0/1/0.0.0/7 /dev/sda7 volume 89GiB EXT4 volume + /0/1/0.0.0/8 /dev/sda8 volume 8098MiB Linux swap volume + /1
[Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
I was unable to use apport-collect but I believe the information I have provided is sufficient. I am running Ubuntu 16.04.1 LTS with kernel v4.7.5-generic on a x64 HP Spectre x360 with Broadwell GT2 5500 integrated graphics. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627408 Title: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627408] [NEW] Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
Public bug reported: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627408 Title: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618286] [NEW] Critical security flaw: Missing crl-verify openvpn option
*** This bug is a security vulnerability *** Public security bug reported: Many VPN providers will give a Certificate Revocation List crl.pem file in their OpenVPN packages. The CRL list is becoming increasingly important after the Heartbleed bug was exposed, leaving many servers vulnerable to attack by unauthorized certificates. Is there any way to manually pass the option 'crl-verify crl.pem' to openvpn by editing a file somewhere? I'm having a difficult time understanding how the network-manager-openvpn client actually works, and what arguments it can actually receive, given that it doesn't 'truly' import .ovpn configuration files. I also have little clue where the configurations are written in the file system as there are no manual pages and no debugging/terminal output for the network-manager-openvpn client. I can't even find the godforsaken binaries after installing the package. It would be much better if one could literally just pass it a .ovpn file, but seeing as that's not possible, I must request that the crl-verify option is added in the near future so that my system is not vulnerable to attacks using unauthorized certificates. ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: crl openvpn ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618286 Title: Critical security flaw: Missing crl-verify openvpn option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1618286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
