*** This bug is a duplicate of bug 1842320 ***
https://bugs.launchpad.net/bugs/1842320
I am getting the same error and cannot even boot Ubuntu 22.04.1 from a
live USB. I am using an HP Elite Dragonfly G2 with 16GB of RAM. I get an
error: out of memory message then a kernel panic. Please fix th
I am getting this error and cannot even boot Ubuntu 22.04.1 from a live
USB. I am using an HP Elite Dragonfly G2 with 16GB of RAM. I get an
error: out of memory message then a kernel panic. Please fix this, I
would very much like to try running Ubuntu but I have to run Fedora 36
instead due to the
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 Ubun
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
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=7
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
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
ubunt
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 edge
@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 U
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
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
** 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** 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
Touch seeded packages, which is subscribed to n
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 go
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
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
>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-
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 i
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
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
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
Touch s
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 becau
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/opencon
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
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
** 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/+sourc
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 lea
** 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 Ub
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
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 notificati
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 m
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 m
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."
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 actual
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 muc
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.
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
Touch
@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
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
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
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
h
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 th
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
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https
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,
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
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
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
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1677175
Title:
network-manager 1.2.6 won't connect to vpn and displays false
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.launch
*** 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 f
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 repeatedl
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 d
51 matches
Mail list logo
