[12:52] <Rick____> Hello, just a heads up for a potential bug in 16.04, not sure if its been raised already.
[12:56] <Rick____> so I said that I would report my findings after having a chat here yesterday, oerheks gave me some tips.   Basically using 16.04 using Network Manager gui to connect to vpn would yield a DNS leak. However doing the manual command sudo openvpn --config 'configname.ovpn'  would work fine with no dns leak.  I tried commenting out #auto in /etc/NetworkManager/NetworkManger.conf -- didn't work, still leaked.  Then tried somethign el
[12:56] <Rick____> in /etc/default/openvpn
[12:56] <Rick____> --- still leaked
[12:56] <Rick____>  only sudo openvpn --config 'configname.ovpn'  would work
[12:56] <Rick____> I even tried importing the config via command line for Network Manager and that still leaked...
[12:57] <Rick____> (I also put     script-security 2             up /etc/openvpn/update-resolv-conf        down /etc/openvpn/update-resolv-conf      in my .ovpn file)
[12:57] <Rick____> that worked fine with sudo openvpn --config 'configfile.ovpn'
[12:57] <Rick____> is there a bug known in network manager for 16.04???
[13:02] <Rick____> (btw it works fine in 14.04 --no leak through gui network manager)
[17:29] <pabelanger> greetings, I was looking for some help to get https://bugs.launchpad.net/mailman/+bug/1251495 for trusty-updates. It fixes a serious properly that leaves mailman broken when upgrading from precise
[17:29] <pabelanger> this has been fixed in xenial+ but still affects trusty
[18:01] <dudeji> what are total number of usual process on ubuntu 14.04 ?
[18:02] <dudeji> cpu 4core 8gb ram
[18:03] <dude> Hello
[18:05] <dude> anybody here ?
[18:06] <dude> i'm trying to fix my first bug, can anyone help ?
[18:53] <dude> hello