[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2017-06-28 Thread Vincent Gerris 
@Silas 
Linux users are patient indeed and they are certainly not waiting for useless 
comments like yours.
If you want to contribute, educate yourself and try to help out. Ranting does 
contribute NOTHING.
So if you really love Linux, think about that.
Try to follow the rules regarding the bug report and contribute where you can 
and people will like it.

Nobody asked you to use Ubuntu, if you're happy with windows 10 (which probably 
nobody else here is) then use it and be happy, why post here?
Don't forget Linux is a community effort and the ways to fix certain problems 
is difficult.
However, making an effort to get it to work will teach you and will get you 
appreciation from others.

As bagl0312 commented already, your point is not even viable, because the issue 
was fixed in 17.04 by a patch.
If you google the issue for older versions, you will probably land on a page 
that describes how to fix that too:
https://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns
 and see work arounds in this thread, so your comment is really just bad timing.

Please think twice before you post something and read the rules.
Thanks to the relentless efforts of the community, this is fixed and work is 
going on to get this in the main version(s).

-- 
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/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-05-04 Thread Vincent Gerris 
You can still add the vpn nameserver to /etc/resolv.conf . Epic blunder by
both systemd-resolv maintainer and Ubuntu packagers for stacking a broken
configuration together for at the 3rd release. Does anyone know how to
escalate this?

On May 4, 2017 19:04, "Winckler"  wrote:

> It's a really ugly workaround, but I'm using iptables to block
> connections to my ISP's DNS. I manually create and remove iptables rules
> using a script but at least this allows me to work remotely. I hope this
> get fix soon.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1624317
>
> Title:
>   systemd-resolved breaks VPN with split-horizon DNS
>
> Status in systemd:
>   New
> Status in systemd package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I use a VPN configured with network-manager-openconnect-gnome in which
>   a split-horizon DNS setup assigns different addresses to some names
>   inside the remote network than the addresses seen for those names from
>   outside the remote network.  However, systemd-resolved often decides
>   to ignore the VPN’s DNS servers and use the local network’s DNS
>   servers to resolve names (whether in the remote domain or not),
>   breaking the split-horizon DNS.
>
>   This related bug, reported by Lennart Poettering himself, was closed
> with the current Fedora release at the time reaching EOL:
>   https://bugzilla.redhat.com/show_bug.cgi?id=1151544
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-04-28 Thread Vincent Gerris 
indeed, this is COMPLETELY broken on 17.04. It seems systemd-resolved is
the only thing being used. My DNS resolving over anyconnect
(openconnect) does not work AT ALL anymore. I don't know which brilliant
mind decided to change things like that, knowing there are so many bugs
open.

any work arounds known are greatly appreciated (disabling systemd-
resolved did not help)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1650929] [NEW] DNS resolving fails after adding usb wifi dongle

2016-12-18 Thread Vincent Gerris 
Public bug reported:

I noticed when a USB wifi dongle is plugged in and I disconnect the
builtin one (Ubuntu 16.10), that resolving of DNS didn't work anymore.

I could ping for example google.nl on IP, but not resolve the name.

After some searching I found the issue seems to be caused by dnsmasq or
systemd-resolved, the first being the most likely.

I disabled dnsmasq in NetworkManager and restarted it and stopped
dnsmasq and everything works as expected.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.6-byt-freeze-fix x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Dec 18 19:16:30 2016
InstallationDate: Installed on 2016-12-11 (7 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dnsmasq (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1650929

Title:
  DNS resolving fails after adding usb wifi dongle

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  I noticed when a USB wifi dongle is plugged in and I disconnect the
  builtin one (Ubuntu 16.10), that resolving of DNS didn't work anymore.

  I could ping for example google.nl on IP, but not resolve the name.

  After some searching I found the issue seems to be caused by dnsmasq
  or systemd-resolved, the first being the most likely.

  I disabled dnsmasq in NetworkManager and restarted it and stopped
  dnsmasq and everything works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.6-byt-freeze-fix x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec 18 19:16:30 2016
  InstallationDate: Installed on 2016-12-11 (7 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1650929/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2016-12-18 Thread Vincent Gerris 
@Martin Pitt : why did you mark this as resolved ??

This is a huge issue and restarting systemd-resolved did NOT fix my problem.
Also, we should not have workarounds, we should have an Ubuntu desktop that:
 - works out of the box at installation: both 16.04 AND 16.10
 - works BEFORE and AFTER an UPGRADE of 16.04
 - works without any manual work arounds or hacks

So PLEASE, come up with an actual solution that fixes this shit.
I honestly find it difficult to express how pissed off I am about the bugs 
because they affect both home and enterprise users.

Here is an overview with a discussion:
http://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns/861991#861991

I propose to either:
 - disable all services that break normal, expected behviour: so out with 
systemd-resolvd if that fixes it
 - fix issues with dnsmasq and/or disable that too by default in NetworkManager

Let's try to fix this in a proper way, and have non-technical users not
deal with these issues.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1636375] Re: systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf

2016-12-18 Thread Vincent Gerris 
Again Martin, this is NOT a solution.
A fix would be something that avoids the problem from emerging in the first 
place.
If stopping systemd-resolvd is a solution, that let's make sure it is NOT 
enabled nor installed in 17.04 by default and let's FIX it to be the same in 
16.10 if possible.

Thank you

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1636375

Title:
  systemd-resolved does not allow you to connect using subdomains using
  search domains which are in /etc/resolv.conf

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  systemd-resolved doesn't seem to allow you to use subdomains when
  connecting to hosts in domains that are part of /etc/resolv.conf

  e.g.

  16:01|scrosby@stewie: ~$ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver W.X.Y.Z
  nameserver A.B.C.D
  nameserver 127.0.0.53
  search blah1 blah2 blah3 blah4 blah5

  with systemd-resolved running

  16:05|scrosby@stewie: ~$ ping foo.bar
  ping: foo.bar: Name or service not known

  without systemd-resolved running

  16:05|scrosby@stewie: ~$ ping foo.bar
  PING foo.bar.blah3 (E.F.G.H) 56(84) bytes of data.
  64 bytes from foo.bar.blah3 (E.F.G.H): icmp_seq=1 ttl=52 time=1.68 ms
  64 bytes from foo.bar.blah3 (E.F.G.H): icmp_seq=2 ttl=52 time=1.09 ms

  It does seem like looking up hosts without a . in their name does use
  the search domains in resolv.conf though

  16:05|scrosby@stewie: ~$ ping foo2
  PING foo2.blah3 (I.J.K.L) 56(84) bytes of data.
  64 bytes from foo2.blah3 (I.J.K.L): icmp_seq=1 ttl=52 time=1.34 ms
  64 bytes from foo2.blah3 (I.J.K.L): icmp_seq=2 ttl=52 time=1.29 ms

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Oct 25 16:13:38 2016
  InstallationDate: Installed on 2016-06-08 (139 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex 990
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=67011022-ac91-464f-ab8f-c97c6cb5a439 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-24 (0 days ago)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.asset.tag: UOM97917
  dmi.board.name: 0VNP2H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: UOM97917
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd08/26/2015:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0VNP2H:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1636375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2016-12-15 Thread Vincent Gerris 
Since this number comes before the other, if it were a duplicate, it would be 
the other way around.
While maybe related it is another bug related to ipv6 as far as I can read.

The pile of crap coming from changes in networkmanager, vpn, dnsmasq or
wherever they come from is horrible : I have never had so many things
breaking over a release and never so vital.

While I am not happy with the content and tend to disagree, please
follow the suggestion of post 50. Let's try to be as specific as
possible and file the bugs like that. Thank you

-- 
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/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1535058] Re: applications close instantly when launched from the launcher or dash

2016-12-11 Thread Vincent Gerris 
I am running 16.10 with budgie installed. Installing unity8 gave me the 
crashing apps issue.
Tried to :
sudo systemctl enable cgmanager
(it was already running)
sudo apt-get install libpam-cgfs
it was already installed 
and 
sudo apt-get install libpam-cgm
that was not installed.

I still have the problem with apps crashing, except for libertine

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1535058

Title:
  applications close instantly when launched from the launcher or dash

Status in Canonical System Image:
  Confirmed
Status in cgmanager package in Ubuntu:
  Incomplete
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  xenial
  applications close instantly when launched from the launcher or dash
  but... if i launch the apps from a VT (for ex firefox using Xmir or gedit 
native --), the app loads ok.

  what close instantly means.. it opens the window and then it closes
  instantly in ~0.3s

  ---

  This has been traced to two causes:
  pam was not installed, it is now a dependency of ubuntu-app-launch or can be 
installed directly
  $ sudo apt-get install libpam-cgfs

  and cgmanager is not enabled by default on systems that were upgraded
  and not clean installs. To enable it

  $ sudo systemctl enable cgmanager

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1535058/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-20 Thread Vincent Gerris 
I noticed a few days back after a failed update that I had cups as a broken 
package.
I uninstalled and some other packages were removed, then I reinstalled.
That seemed to work. I don't know what I lost and while reporting I got a 
notification that my conf file was edited.
Can't remember ever changing anything.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2016-10-28 Thread Vincent Gerris 
@https://launchpad.net/~cyphermox Mathieu, why are you marking this as 
Incomplete?
Can you be specific in what kind of information you need to consider it 
complete, instead of pointing people to a DNS admin, who may not be interested 
in filing a bug?

Some people clearly described how the behaviour changed from 14.04 and I can 
confirm this.
The current setup is nowhere near a working solution that a normal user that 
gets VPN connection info can work with.
That hurts business users and pisses developers and users off that even want to 
make an attempt to make it work.

The net is flooded with issues regarding VPN and DNS, it would be great if you 
can point us to the right steps and information to supply to actually get this 
working like say the cisco AnyConnect secure mobility client.
With the exact same VPN server, I can use that tool on Mac OS X without ANY 
configuration and it "Just works".

I would say the goal is to have it working like that for everybody using 
network manager.
Let's talk defaults, settings and requirements and I'll try to get the server 
info or anything else that is needed.

-- 
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/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1328260] Re: mighty mouse bluetooth not pairing

2016-04-19 Thread Vincent Gerris 
A decent OS would just pair with a mouse and implement the workaround or
structurally fix the bug. The bug is confirmed, so it's up to someone to
fix it. Complain at the mouse vendor or at the developer and pick your
hardware carefully and Linux is fun and nice.

I reported this bug almost 2 years ago on an LTS release, I would have hoped 
for a fix by now.
Instead I have a laptop that freezes now on the new soon to be released LTS.
Had to rant a bit because I have had that a lot in the past. I don't see why a 
command line action is acceptable,for Linux to be great, these things should 
just work.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1328260

Title:
  mighty mouse bluetooth not pairing

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Using the default GUI, I cannot pair my Apple Mighty Mouse.
  The mouse is detected, but when trying to pair, nothing happens and it is 
impossible to connect.

  It seems there should be an agent running to handle the pairing/pin stuff, I 
found that here:
  
http://askubuntu.com/questions/453655/ubuntu-14-04-bluetooth-magic-mouse-doesnt-pair-no-agent-available

  It might be an issue with more devices, I did not test it.

  So the fix:
  In a terminal as a normal user do:
  bluez-simple-agent
  then use pin  (worked in my case).

  Description:  Ubuntu 14.04 LTS
  Release:  14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1328260/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"

2015-12-02 Thread Vincent Gerris 
Funny thing I noticed is that if I close the lid again and open it
again, it does work again

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1422143

Title:
  No wifi connection after suspend with systemd due to missing "wpa_cli
  suspend"

Status in One Hundred Papercuts:
  Confirmed
Status in NetworkManager:
  Unknown
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Wily:
  Fix Committed
Status in wpa source package in Xenial:
  Fix Released

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  SRU INFORMATION
  ===
  In some of these cases this bug can be worked around by calling "wpa_cli 
suspend/resume" before/after suspend, like we used to do with the old pm-utils 
quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects 
particular hardware, and thus this needs to be tested by affected reporters, 
there is no general reproducer for arbitrary systems.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"

2015-12-02 Thread Vincent Gerris 
Same issue for me on Lenovo Yoga 2 11 running Ubuntu 15.04 and systemd .
01:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1422143

Title:
  No wifi connection after suspend with systemd due to missing "wpa_cli
  suspend"

Status in One Hundred Papercuts:
  Confirmed
Status in NetworkManager:
  Unknown
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Wily:
  Fix Committed
Status in wpa source package in Xenial:
  Fix Released

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  SRU INFORMATION
  ===
  In some of these cases this bug can be worked around by calling "wpa_cli 
suspend/resume" before/after suspend, like we used to do with the old pm-utils 
quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects 
particular hardware, and thus this needs to be tested by affected reporters, 
there is no general reproducer for arbitrary systems.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1426930] Re: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-11-01 Thread Vincent Gerris 
same issue for me on 14.04 normal update to vivid.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1426930

Title:
  package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I am new and I do not fully understand the technical issues but this
  occurred while I was repairing my GRUB. Thank You!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fontconfig 2.11.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Sun Mar  1 09:20:08 2015
  DuplicateSignature: package:fontconfig:2.11.1-0ubuntu6:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-01-19 (40 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1426930/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1370245] Re: wpa_supplicant version 2.2 available

2015-08-25 Thread Vincent Gerris 
just wanted to note that 2.4 seems broken, at least in Fedora for some setups 
of wireless networks:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1473088
a fix in 14.04 seems reasonable, maybe by upgrading to 2.3 if possible.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1370245

Title:
  wpa_supplicant version 2.2 available

Status in wpa package in Ubuntu:
  Fix Released
Status in wpasupplicant package in Ubuntu:
  Won't Fix

Bug description:
  Currently version 2.1 is still the version slated to be shipped with
  utopic. It seems from http://w1.fi/wpa_supplicant/ that wpa_supplicant
  version 2.2 was released in 2014-06. Is it possible for 2.2 to be
  packaged?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1370245/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1287827] Re: wifi not configurable in network-manager showing disabled by hardware switch

2014-10-12 Thread Vincent Gerris 
Mathieu, while it may not be an issue with NetworkManager, this is still an 
issue.
Should this bug be reported against another package?
If anyone knows, please assign it accordingly. (I would gladly do it myself, 
but I am unsure on how to proceed and would still like this to be fixed for the 
future)
Thank you

-- 
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/1287827

Title:
  wifi not configurable in network-manager showing disabled by hardware
  switch

Status in “network-manager” package in Ubuntu:
  Invalid

Bug description:
  Network manager shows Wifi is disabled by hardware switch. It worked jut 
after install but not anymore after.
  I read somewhere I can use wicd and that does work.
  iwlist wlan0 scan worked also before installing that.
  Seems like a bug in network-manager to me.
  It would be nice if NM does whatever wicd does to enable the wifi card.
  I have nog physical button for wif and wifi is enabled in the UEFI firmware.

  output of rfkill list:
  ubuntu@ubuntu-Lenovo-Yoga-2-11:~$ sudo rfkill list
  0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: yes
  1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: yes
  3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  4: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no
  15: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  ubuntu@ubuntu-Lenovo-Yoga-2-11:~$

  ubuntu@ubuntu-Lenovo-Yoga-2-11:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  ubuntu@ubuntu-Lenovo-Yoga-2-11:~$ apt-cache policy network-manager
  network-manager:
Installed: 0.9.8.8-0ubuntu4
Candidate: 0.9.8.8-0ubuntu4
Version table:
   *** 0.9.8.8-0ubuntu4 0
  500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ubuntu@ubuntu-Lenovo-Yoga-2-11:~$ apt-cache policy network-manager-gnome
  network-manager-gnome:
Installed: 0.9.8.4-1ubuntu3
Candidate: 0.9.8.4-1ubuntu3
Version table:
   *** 0.9.8.4-1ubuntu3 0
  500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  4 18:39:18 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-03-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140303)
  IpRoute:
   default via 192.168.1.1 dev wlan0 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.115
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-03-04T14:08:55.818581
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   thuis-17338c5c-1ba4-4ed4-ac63-bf2ab23734e2   
802-11-wireless   0never  yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   unavailable   
/org/freedesktop/NetworkManager/Devices/1
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8disconnectedenabled   disabled
disabled   enabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1287827/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp