[Touch-packages] [Bug 1411490] Re: package libnss3:amd64 2:3.17.1-0ubuntu0.14.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

[Launchpad Bug Tracker]

[Expired for nss (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nss (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libnss3:amd64 2:3.17.1-0ubuntu0.14.04.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in nss package in Ubuntu:
  Expired

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libnss3:amd64 2:3.17.1-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Jan 16 00:39:18 2015
  DuplicateSignature: package:libnss3:amd64:2:3.17.1-0ubuntu0.14.04.2:package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-12-10 (36 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: nss
  Title: package libnss3:amd64 2:3.17.1-0ubuntu0.14.04.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1411490/+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 1676259] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[John Campbell]

Public bug reported:

Upgrade to 4.4.0-66-generic failed with message about hal in fontconfig

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri Mar 24 12:42:19 2017
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2010-12-23 (2285 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Upgrade to 4.4.0-66-generic failed with message about hal in
  fontconfig

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Mar 24 12:42:19 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2010-12-23 (2285 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1676259/+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 1676259] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Upgrade to 4.4.0-66-generic failed with message about hal in
  fontconfig

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Mar 24 12:42:19 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2010-12-23 (2285 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1676259/+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 1575779] Re: hostnamectl fails under lxd unpriv container

[Wesley Wiedenmeier]

** Merge proposal unlinked:
   
https://code.launchpad.net/~wesley-wiedenmeier/cloud-init/+git/cloud-init/+merge/321029

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

Title:
  hostnamectl fails under lxd unpriv container

Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  1.  % lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2.  % apt-cache policy apparmor
  apparmor:
Installed: 2.10.95-0ubuntu2
Candidate: 2.10.95-0ubuntu2
Version table:
   *** 2.10.95-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  % apt-cache policy lxd
  lxd:
Installed: 2.0.0-0ubuntu4
Candidate: 2.0.0-0ubuntu4
Version table:
   *** 2.0.0-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. lxc launch ubuntu-daily:xenial x1
  lxc exec x1 /bin/bash

  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  
  4. hostnamectl status hangs indefinitely

  On the host, there are some audit messages for each invocation of
  hostnamectl

  [411617.032274] audit: type=1400 audit(1461695563.731:100):
  apparmor="DENIED" operation="file_lock" profile="lxd-
  x1_" pid=17100 comm="(ostnamed)" family="unix"
  sock_type="dgram" protocol=0 addr=none

  It's related to socket activation.  One can workaround this by running
  systemd-hostnamed in the background first

  root@x1:~# /lib/systemd/systemd-hostnamed & 
  [1] 2462
  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Apr 27 11:19:27 2016
  InstallationDate: Installed on 2016-01-01 (117 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+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 1575779] Re: hostnamectl fails under lxd unpriv container

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~wesley-wiedenmeier/cloud-init/+git/cloud-init/+merge/321029

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

Title:
  hostnamectl fails under lxd unpriv container

Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  1.  % lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2.  % apt-cache policy apparmor
  apparmor:
Installed: 2.10.95-0ubuntu2
Candidate: 2.10.95-0ubuntu2
Version table:
   *** 2.10.95-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  % apt-cache policy lxd
  lxd:
Installed: 2.0.0-0ubuntu4
Candidate: 2.0.0-0ubuntu4
Version table:
   *** 2.0.0-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. lxc launch ubuntu-daily:xenial x1
  lxc exec x1 /bin/bash

  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  
  4. hostnamectl status hangs indefinitely

  On the host, there are some audit messages for each invocation of
  hostnamectl

  [411617.032274] audit: type=1400 audit(1461695563.731:100):
  apparmor="DENIED" operation="file_lock" profile="lxd-
  x1_" pid=17100 comm="(ostnamed)" family="unix"
  sock_type="dgram" protocol=0 addr=none

  It's related to socket activation.  One can workaround this by running
  systemd-hostnamed in the background first

  root@x1:~# /lib/systemd/systemd-hostnamed & 
  [1] 2462
  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Apr 27 11:19:27 2016
  InstallationDate: Installed on 2016-01-01 (117 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+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 1675692] Re: App drawer often refuses/ignores drag gestures

[Daniel van Vugt]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  App drawer often refuses/ignores drag gestures

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  If I click on the app drawer and try to drag it, it will often refuse
  to do anything.

  The issue it seems is a kind of hysteresis: If your drag is even
  slightly diagonal then it will be rejected and do nothing. The app
  drawer apparently only supports perfect vertical or horizontal drags,
  but this is not user friendly since humans will rarely drag perfectly
  vertically or horizontally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675692/+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 1658921] Re: NetworkManager does not manage wired connection

[Paul Smith]

Just want to point out that "chroot installs" or netboot installs are
NOT the only places this breaks.  I did a a straightforward upgrade (via
do-release-upgrade) from Ubuntu GNOME 16.04.n (latest packages
installed) to Ubuntu GNOME 16.10, on a standard desktop system where the
wired network was managed by NM before.

After the upgrade, no wired interface was available.

Luckily my desktop also has a wireless interface (which I never used
before); that still worked so I could continue to search for help: it
took two days on and off but I finally found this bug (I was searching
NetworkManager documentation and looking through nmcli output,
journalctl output, etc. but there is nothing shown anywhere about this;
most likely NM should be modified so that it prints something useful to
the logs if it skips interfaces due to the unmanaged-devices setting).

The solution above (replacing with an empty file) then running "sudo
killall -HUP NetworkManager" caused my wired connection to immediately
reappear and connect.

In any event, this change is kind of a disaster; regardless of the
intentions behind it the results are far too disruptive and the reasons
for the problem and the solution are far too obscure and difficult for
the average desktop user to be expected to figure out.

This change should be reverted until some alternative solution that is
more carefully targeted to only impact the correct set of systems can be
devised and implemented.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+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 1675692] Re: App drawer often refuses/ignores drag gestures

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity8 (Ubuntu)
   Status: New => Confirmed

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

Title:
  App drawer often refuses/ignores drag gestures

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  If I click on the app drawer and try to drag it, it will often refuse
  to do anything.

  The issue it seems is a kind of hysteresis: If your drag is even
  slightly diagonal then it will be rejected and do nothing. The app
  drawer apparently only supports perfect vertical or horizontal drags,
  but this is not user friendly since humans will rarely drag perfectly
  vertically or horizontally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675692/+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 1676000] Re: SDL apps open a second black window ("OpenGL test")

[Daniel van Vugt]

Same bug in neverputt. Looks like the SDL/Unity8 issues mentioned in
comment #5.

** Summary changed:

- neverball opens a second black window, maximizing the window crashes unity8
+ SDL apps open a second black window ("OpenGL test")

** Summary changed:

- SDL apps open a second black window ("OpenGL test")
+ SDL apps open a second black window titled "OpenGL test"

** Summary changed:

- SDL apps open a second black window titled "OpenGL test"
+ SDL apps open a second black window titled "OpenGL test" or "Mir surface"

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

Title:
  SDL apps open a second black window titled "OpenGL test" or "Mir
  surface"

Status in Canonical System Image:
  Confirmed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 Unity8

  neverball opens a second black window, maximizing the window crashes
  unity8

  start neverball without Xmir (it's an SDL2 app i think)
  you'll now see a black window behind the neverball window titled "OpenGL 
test" (see screenshot), now try to maximize that black window, here it just 
crashes unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676000/+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 1676000] Re: neverball opens a second black window, maximizing the window crashes unity8

[Daniel van Vugt]

The unity8 crash in "what(): map::at" is pretty common but I'm not sure
if we have one or more remaining causes of that. See bug 1668466, bug
1672012

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

Title:
  neverball opens a second black window, maximizing the window crashes
  unity8

Status in Canonical System Image:
  Confirmed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 Unity8

  neverball opens a second black window, maximizing the window crashes
  unity8

  start neverball without Xmir (it's an SDL2 app i think)
  you'll now see a black window behind the neverball window titled "OpenGL 
test" (see screenshot), now try to maximize that black window, here it just 
crashes unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676000/+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 1676000] Re: neverball opens a second black window, maximizing the window crashes unity8

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libsdl2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  neverball opens a second black window, maximizing the window crashes
  unity8

Status in Canonical System Image:
  Confirmed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 Unity8

  neverball opens a second black window, maximizing the window crashes
  unity8

  start neverball without Xmir (it's an SDL2 app i think)
  you'll now see a black window behind the neverball window titled "OpenGL 
test" (see screenshot), now try to maximize that black window, here it just 
crashes unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676000/+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 1676000] Re: neverball opens a second black window, maximizing the window crashes unity8

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: qtmir (Ubuntu)
   Status: New => Confirmed

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

Title:
  neverball opens a second black window, maximizing the window crashes
  unity8

Status in Canonical System Image:
  Confirmed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 Unity8

  neverball opens a second black window, maximizing the window crashes
  unity8

  start neverball without Xmir (it's an SDL2 app i think)
  you'll now see a black window behind the neverball window titled "OpenGL 
test" (see screenshot), now try to maximize that black window, here it just 
crashes unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676000/+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 1676000] Re: neverball opens a second black window, maximizing the window crashes unity8

[Daniel van Vugt]

Also, bug confirmed. Unity8 fails to launch Neverball from the app drawer but I 
can get it running from ssh:
   neverball -- --desktop_file_hint=unity8
and now I can see this bug.

However, I also know that SDL likes to probe the server with some early
connections so this might be a duplicate of bug 1577641 if SDL is
leaking a duplicate MirConnection. Fixing either SDL or Unity8 (bug
1577641) should do the trick.

** Tags added: unity8-desktop

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

Title:
  neverball opens a second black window, maximizing the window crashes
  unity8

Status in Canonical System Image:
  Confirmed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 Unity8

  neverball opens a second black window, maximizing the window crashes
  unity8

  start neverball without Xmir (it's an SDL2 app i think)
  you'll now see a black window behind the neverball window titled "OpenGL 
test" (see screenshot), now try to maximize that black window, here it just 
crashes unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676000/+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 1676000] Re: neverball opens a second black window, maximizing the window crashes unity8

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity8 (Ubuntu)
   Status: New => Confirmed

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

Title:
  neverball opens a second black window, maximizing the window crashes
  unity8

Status in Canonical System Image:
  Confirmed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 Unity8

  neverball opens a second black window, maximizing the window crashes
  unity8

  start neverball without Xmir (it's an SDL2 app i think)
  you'll now see a black window behind the neverball window titled "OpenGL 
test" (see screenshot), now try to maximize that black window, here it just 
crashes unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676000/+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 1676000] Re: neverball opens a second black window, maximizing the window crashes unity8

[Daniel van Vugt]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  neverball opens a second black window, maximizing the window crashes
  unity8

Status in Canonical System Image:
  Confirmed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 Unity8

  neverball opens a second black window, maximizing the window crashes
  unity8

  start neverball without Xmir (it's an SDL2 app i think)
  you'll now see a black window behind the neverball window titled "OpenGL 
test" (see screenshot), now try to maximize that black window, here it just 
crashes unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676000/+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 1676000] Re: neverball opens a second black window, maximizing the window crashes unity8

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: qtubuntu (Ubuntu)
   Status: New => Confirmed

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

Title:
  neverball opens a second black window, maximizing the window crashes
  unity8

Status in Canonical System Image:
  Confirmed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 Unity8

  neverball opens a second black window, maximizing the window crashes
  unity8

  start neverball without Xmir (it's an SDL2 app i think)
  you'll now see a black window behind the neverball window titled "OpenGL 
test" (see screenshot), now try to maximize that black window, here it just 
crashes unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676000/+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 1676016] Re: Overflow menus don't work

[Daniel van Vugt]

** Tags added: unity8-desktop

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

Title:
  Overflow menus don't work

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 17.04 unity8

  the menu doesn't work if the window is smaller
  launch kate (without Xmir), resize the window until the menu is wider than 
the window (you'll see a down arrow that will expand the menu if pressed) see 
screenshot
  now try to open the expanded menu/submenus see screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676016/+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 1676011] Re: [unity8] minimize/unminimize animation is not pointing to the app in the launcher

[Daniel van Vugt]

*** This bug is a duplicate of bug 1603295 ***
https://bugs.launchpad.net/bugs/1603295

** This bug has been marked a duplicate of bug 1603295
   Minimise animation goes to/from the middle of the launcher instead of the 
icon location

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

Title:
  [unity8] minimize/unminimize animation is not pointing to the app in
  the launcher

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8

  [unity8] minimize/unminimize animation is not pointing to the app in
  the launcher

  when you minimize/unminimize and app it just resizes and moves the
  window to a fixed location. in unity8 the UX is much better/more
  descriptive, it actually resizes the window towards the actuall app
  icon in the launcher.

  minimize/maximize apps in both u7/u8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676011/+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 1676004] Re: tiled - enabling hardware accelerated drawing spawns new windows/instances forever

[Daniel van Vugt]

** Tags added: unity8-desktop

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

Title:
  tiled - enabling hardware accelerated drawing spawns new
  windows/instances forever

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8

  tiled - enabling hardware accelerated drawing spawns new windows/instances 
forever
  if you don't have tiled install (it's a qt5 app) "apt install tiled"
  launch tiled without Xmir
  from Preferences enable Hardware accelerated drawing (OpenGL) see screenshot
  should now start to spawn multiple instances/windows for ever. if it doesn't 
click on new project (should be the same)

  in unity7 seems to work fine

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676004/+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 1577641] Re: Unity8 creates a blank black window for windowless apps

[Daniel van Vugt]

See also (?) bug 1676000

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

Title:
  Unity8 creates a blank black window for windowless apps

Status in Canonical System Image:
  Won't Fix
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Unity8 creates a blank black window for windowless apps.

  Windowless apps are closer thank you think:   Xmir -rootless
  is one such example while no X apps have started yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1577641/+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 1675802] Re: Empty spaces in some (titlebar integrated) menus

[Daniel van Vugt]

** Summary changed:

- empty spaces in some menus
+ Empty spaces in some (titlebar integrated) menus

** Tags added: unity8-desktop

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

Title:
  Empty spaces in some (titlebar integrated) menus

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity 8

  empty spaces in some menus, see the attached screenshots (unity8/unity7). 
there is tiled a qt5 app running without Xmir but i've seen the same in other 
qt5 apps (to install tiled, apt install tiled)
  affected is File \ Recent Files (menu), you'll see a big empty space

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675802/+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 1666363] Re: Windows behind are missing during un-maximize animation

[Daniel van Vugt]

** Changed in: canonical-devices-system-image
Milestone: None => u8c-z

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Changed in: canonical-devices-system-image
   Status: Triaged => In Progress

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

Title:
  Windows behind are missing during un-maximize animation

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Windows behind are missing during an un-maximize animation. They don't
  appear until the animation completes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666363/+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 1675809] Re: [unity8] Launcher menu doesn't handle large lists very well

[Daniel van Vugt]

** Tags added: unity8-desktop

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

Title:
  [unity8] Launcher menu doesn't handle large lists very well

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 17.04 Unity8

  [unity8] Launcher menu doesn't handle large lists very well
  see screenshot, i have large number of tiled instances opened but i can only 
partially see or click on them because a part of the menu is off screen i think

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675809/+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 1675828] Re: [unity8] maximize/unmaximize doesn't show the opened apps, only shows the background while animating

[Daniel van Vugt]

*** This bug is a duplicate of bug 1666363 ***
https://bugs.launchpad.net/bugs/1666363

** This bug has been marked a duplicate of bug 1666363
   Windows behind are missing during un-maximize animation

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

Title:
  [unity8] maximize/unmaximize doesn't show the opened apps, only shows
  the background while animating

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  ubuntu 17.04 unity8

  [unity8] maximize/unmaximize doesn't show the opened apps, only shows
  the background while animating

  launch some random apps, maximize/unmaximize one app, while the window
  is resizing the apps behind are not visible, only the wallpaper until
  the animations stops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675828/+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 1675688] Re: Legacy app icons look poor/broken inside a rounded grey square

[Daniel van Vugt]

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Legacy app icons look poor/broken inside a rounded grey square

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Legacy app icons look poor/broken inside a rounded grey square (in the
  app drawer).

  We would achieve a much nicer appearance without the rounded grey
  squares at all. Not only that, but we'd then have a visual distinction
  between legacy app icons and "modern" Ubuntu Touch apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675688/+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 1675696] Re: Poor visual quality: Text in titlebars and panel is too large for the panel height (or titlebar too small for the text height)

[Daniel van Vugt]

I think a good rule of thumb is to ensure for any text label/area the
text height is only 50% of the area's height.

So:
  top 25% blank
  middle 50% text
  bottom 25% blank and/or descenders

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

Title:
  Poor visual quality: Text in titlebars and panel is too large for the
  panel height (or titlebar too small for the text height)

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Poor visual quality in Unity8: Text in titlebars and panel is too
  large for the panel height (or titlebar too small for the text height)

  If you look at Unity7 and other desktops you will see they achieve a
  nicer appearance by leaving more space above and below the text.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675696/+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 1675572] Re: GUI of desktop apps are too big on high-dpi screens

[Daniel van Vugt]

** Changed in: canonical-devices-system-image
   Status: New => In Progress

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Changed in: canonical-devices-system-image
Milestone: None => u8c-z

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

Title:
  GUI of desktop apps are too big on high-dpi screens

Status in Canonical System Image:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  On a 13" 1080p display, fonts and UI in general is too big when
  running desktop Qt-based apps like konsole, QtCreator and Kate.

  Strangely, hardcoding logical dpi to 96 in qtubuntu fixes it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675572/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Daniel van Vugt]

We could theoretically make the one USC instance appear (differently) on
multiple VTs. In tinkering with Mir's VT code I came to realize that VTs
are truly a virtual concept. If you ignore the existence of VTs then you
can still forcefully start up your system compositor on the screen.
Cooperating with the notion of a current VT is just being a good
citizen.

That said, if we're going to support an arbitrary number of users then
giving each one a different VT does not scale. USC should have a switch-
session key combo of its own (similar to the existing Ctrl-Alt-Fn).

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

Title:
  Second unity8 user session hangs with a black screen

Status in Canonical System Image:
  In Progress
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1675138] Re: Please transition to Boost 1.62

[Daniel van Vugt]

Ignore comment #16 as it's not relevant to this bug. The fix for this
bug is NOT in Mir 0.26 or Ubuntu branches.

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

Title:
  Please transition to Boost 1.62

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  New
Status in mir package in Ubuntu:
  Triaged

Bug description:
  There is an ongoing transition to Boost 1.62 and mir is one of the last 
affected packages:
  http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1675138/+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 1676249] [NEW] Guest session shouldn't require auth for wifi

[Doug McMahon]

Public bug reported:

Likely not network-manager but it's affected & got to start somewhere.
Test case:
Boot up to greeter & login to guest session.
Click on network indicator, choose wifi network used by main user

What happens:
Password to network must be entered, then a keyring must be created.

What should happen:
Upon logging in wifi should be enabled with no guest user interaction needed.

This is the correct current behavior in 14.04.x. 16.04.x is broken in
this regard, at least for many users/user's hardware.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sun Mar 26 22:02:49 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-03-26 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170326)
IpRoute:
 default via 192.168.1.1 dev wlp8s0 proto static metric 600 
 169.254.0.0/16 dev wlp8s0 scope link metric 1000 
 192.168.1.0/24 dev wlp8s0 proto kernel scope link src 192.168.1.6 metric 600
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
 06F21A  957649c7-c710-4d40-9aed-b33776d3c84d  802-11-wireless  
1490580159  Sun 26 Mar 2017 10:02:39 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/7 
 Wired connection 1  64e15934-77b8-36e1-961a-5065243bc6ca  802-3-ethernet   
1490579550  Sun 26 Mar 2017 09:52:30 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
06F21A  957649c7-c710-4d40-9aed-b33776d3c84d  
/org/freedesktop/NetworkManager/ActiveConnection/7 
 enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  Guest session shouldn't require auth for wifi

Status in network-manager package in Ubuntu:
  New

Bug description:
  Likely not network-manager but it's affected & got to start somewhere.
  Test case:
  Boot up to greeter & login to guest session.
  Click on network indicator, choose wifi network used by main user

  What happens:
  Password to network must be entered, then a keyring must be created.

  What should happen:
  Upon logging in wifi should be enabled with no guest user interaction needed.

  This is the correct current behavior in 14.04.x. 16.04.x is broken in
  this regard, at least for many users/user's hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Mar 26 22:02:49 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-03-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170326)
  IpRoute:
   default via 192.168.1.1 dev wlp8s0 proto static metric 600 
   169.254.0.0/16 dev wlp8s0 scope link metric 1000 
   192.168.1.0/24 dev wlp8s0 proto kernel scope link src 192.168.1.6 metric 600
  Netwo

[Touch-packages] [Bug 1661498] Re: [regression] Segfault on detect_fd_leaks during acceptance tests (in DisplayConfiguration/{DisplayFormatSetting, DisplaySubpixelSetting})

[Daniel van Vugt]

** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mir (Ubuntu)
   Status: New => Fix Released

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

** Changed in: mir (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [regression] Segfault on detect_fd_leaks during acceptance tests (in
  DisplayConfiguration/{DisplayFormatSetting,DisplaySubpixelSetting})

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I've seen this quite often in a silo... Not so often in CI.

  8: [ RUN ] 
DisplayConfiguration/DisplayFormatSetting.can_get_all_output_format/3
  8: [2017-02-03 01:05:22.479325] mirserver: Starting
  8: [2017-02-03 01:05:22.479397] mirserver: Selected driver: mir:stub-graphics 
(version 0.26.1)
  8: [2017-02-03 01:05:22.489793] mirserver: Using software cursor
  8: [2017-02-03 01:05:22.492185] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.1)
  8: [2017-02-03 01:05:22.492233] mirserver: Mir version 0.26.1
  8: [2017-02-03 01:05:22.492401] mirserver: Initial display configuration:
  8: [2017-02-03 01:05:22.492420] mirserver: Output 1: VGA connected, used
  8: [2017-02-03 01:05:22.492430] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.492436] mirserver: Power is on
  8: [2017-02-03 01:05:22.492444] mirserver: Current mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.492451] mirserver: Preferred mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.492457] mirserver: Orientation normal
  8: [2017-02-03 01:05:22.492463] mirserver: Logical size 4x3
  8: [2017-02-03 01:05:22.492468] mirserver: Logical position +0+0
  8: [2017-02-03 01:05:22.492474] mirserver: Output 2: VGA disconnected
  8: [2017-02-03 01:05:22.492480] mirserver: Output 3: VGA connected, unused
  8: [2017-02-03 01:05:22.492486] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.492491] mirserver: Power is off
  8: [2017-02-03 01:05:22.511553] mirserver: New display configuration:
  8: [2017-02-03 01:05:22.511586] mirserver: Output 1: VGA connected, used
  8: [2017-02-03 01:05:22.511597] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.511603] mirserver: Power is on
  8: [2017-02-03 01:05:22.511611] mirserver: Current mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.511618] mirserver: Preferred mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.511624] mirserver: Orientation normal
  8: [2017-02-03 01:05:22.511629] mirserver: Logical size 4x3
  8: [2017-02-03 01:05:22.511635] mirserver: Logical position +0+0
  8: [2017-02-03 01:05:22.511661] mirserver: New base display configuration:
  8: [2017-02-03 01:05:22.526758] mirserver: Stopping
  8: /<>/mir-0.26.1+17.04.20170203/tools/detect_fd_leaks.bash: line 
84: 27470 Segmentation fault  (core dumped) $@ 2>&1
  8:  27471 Done| detect_fd_leaks
   8/20 Test  #8: mir_acceptance_tests ..***Failed  
 81.66 sec
  Running main() from main.cpp
  Note: Google Test filter = -:
  [==] Running 517 tests from 86 test cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661498/+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 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib

[Daniel van Vugt]

** Changed in: mir (Ubuntu)
   Status: In Progress => Triaged

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+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 1675138] Re: Please transition to Boost 1.62

[Daniel van Vugt]

** Changed in: mir (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: mir (Ubuntu)
 Assignee: Mattia Rizzolo (mapreri) => (unassigned)

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

Title:
  Please transition to Boost 1.62

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  New
Status in mir package in Ubuntu:
  Triaged

Bug description:
  There is an ongoing transition to Boost 1.62 and mir is one of the last 
affected packages:
  http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1675138/+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 1675692] Re: App drawer often refuses/ignores drag gestures

[Daniel van Vugt]

*"very poor right now"

** Changed in: canonical-devices-system-image
   Status: Incomplete => New

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => New

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

Title:
  App drawer often refuses/ignores drag gestures

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  If I click on the app drawer and try to drag it, it will often refuse
  to do anything.

  The issue it seems is a kind of hysteresis: If your drag is even
  slightly diagonal then it will be rejected and do nothing. The app
  drawer apparently only supports perfect vertical or horizontal drags,
  but this is not user friendly since humans will rarely drag perfectly
  vertically or horizontally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675692/+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 1675692] Re: App drawer often refuses/ignores drag gestures

[Daniel van Vugt]

Because:
  (1) My desktop does not have a touch screen and dragging with a mouse 
should(?) exhibit the same issues that touch users will experience when 
dragging with a finger; and
  (2) Mouse wheel scrolling is very poor right right: bug 1556795

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

Title:
  App drawer often refuses/ignores drag gestures

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  If I click on the app drawer and try to drag it, it will often refuse
  to do anything.

  The issue it seems is a kind of hysteresis: If your drag is even
  slightly diagonal then it will be rejected and do nothing. The app
  drawer apparently only supports perfect vertical or horizontal drags,
  but this is not user friendly since humans will rarely drag perfectly
  vertically or horizontally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675692/+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 1676240] [NEW] Intel Skylake HDMI No sound at all after monitor wake

[Nick Breen]

Public bug reported:

Reproduction:
1. Boot
2. Select HDMI from Sound Settings
3. [sounds play]
4. Monitor sleeps (PC does not)
5. Monitor wakes
6. No sound, HDMI is missing from Sound Settings
7. Re-plugging the HDMI cable restores the option, repeat from 2.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nick   2851 F pulseaudio
 /dev/snd/controlC1:  nick   2851 F pulseaudio
CurrentDesktop: Unity
Date: Mon Mar 27 13:26:19 2017
InstallationDate: Installed on 2016-10-28 (149 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [, Intel Skylake HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: KYSKLi70.86A.0041.2016.0817.1130
dmi.board.name: NUC6i7KYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H90766-405
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0041.2016.0817.1130:bd08/17/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Intel Skylake HDMI No sound at all after monitor wake

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Reproduction:
  1. Boot
  2. Select HDMI from Sound Settings
  3. [sounds play]
  4. Monitor sleeps (PC does not)
  5. Monitor wakes
  6. No sound, HDMI is missing from Sound Settings
  7. Re-plugging the HDMI cable restores the option, repeat from 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nick   2851 F pulseaudio
   /dev/snd/controlC1:  nick   2851 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 27 13:26:19 2017
  InstallationDate: Installed on 2016-10-28 (149 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [, Intel Skylake HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0041.2016.0817.1130
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0041.2016.0817.1130:bd08/17/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1676240/+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 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS

[michaelcole]

Is there a way to backport this to 16.04?  Thanks!

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

Title:
  Don't write search domains to resolv.conf in the case of split DNS

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  All VPN users meaning to use split-tunnelling in a situation where leaking 
DNS data to the internet about what might be behind their VPN is undesirable.

  [Test case]
  1) connect to VPN
  2) Use dig to request a name that should be on the VPN
  3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only 
gone through the VPN nameservers (only its request number should have increased 
by one)
  4) Use dig to request a name off-VPN, such as google.com.
  5) Verify (kill -USR1 again) that the request has caused the non-VPN 
nameserver request number to increase, and that the VPN number has not 
increased.

  It is easier to verify this when there is as little traffic as
  possible on the system, to avoid spurious DNS requests which would
  make it harder to validate the counters.

  [Regression potential]
  This change modifies the way in which DNS nameservers and search domains are 
passed to dnsmasq, as such, if a VPN is configured in a non-standard way and 
intended to be used to resolve all network requests (which is typically not the 
case for split-tunnelling) or if the public network is intended to always 
resolve all requests while the VPN still provides search domains, one might 
observe incorrect behavior.

  Possible failure cases would include failure to resolve names
  correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving
  to the incorrect values (if the wrong nameserver is used).

  ---

  Currently, NM will write all search domains to both any DNS-handling
  plugins running, and also to resolv.conf / resolvconf; in all cases.

  The issue is that doing so means that in the split-DNS case on VPNs,
  you might get a negative response from all nameservers, then a new
  request by glibc with the search tacked on, to nameservers again,
  which might cause DNS requests for "private" resources (say, on the
  VPN) to be sent to external, untrusted resolvers, or for DNS queries
  not meant for VPN nameservers to be sent through the VPN anyway.

  This is fixable in the case where we have a caching plugin running
  (such as dnsmasq). dnsmasq will already know about the search domains
  and use that to limit queries to the right nameservers when a VPN is
  running. Writing search domains to resolv.conf is unnecessary in this
  case.

  We should still write search domains if no caching gets done, as we
  then need to expect glibc to send requests as it otherwise would.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1673939] Re: Downloads (of any kind) don't work in Desktop

[Mayrinck]

Just installed all this, don't work... I noticed that uploads are not
possible as well, the last two lines of this output are attempts to
download and upload a file, respectively

** Attachment added: "output-2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1673939/+attachment/4846461/+files/output-2.txt

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

Title:
  Downloads (of any kind) don't work in Desktop

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  System: Ubuntu 16.04.2 LTS
  Package Version: 0.23+16.04.20161028-0ubuntu2

  I'm trying to use this browser as my default but it has a problem, no
  matter where on the web or what kind of file I am trying to download
  (images, packages, text files, etc...) nothing happens, no dialogs, no
  loading bars, nothing... As if there's a problem with all the
  websites, but the thing is actually in the browser... Also, nothing
  shows up in any of the directories related to the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1673939/+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 1562002] Re: Nautilus: lag after choosing action in top right menu

[Bug Watch Updater]

** Changed in: gtk
   Status: Unknown => Fix Released

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  Nautilus: lag after choosing action in top right menu

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Confirmed

Bug description:
  # Impact
  This is known to affect Nautilus, but can potentially affect other 
applications too (the upstream bug has an example test app attached).

  See also the duplicate bug 1644393, which is another appearance of the
  same bug but with other symptoms.

  # Proposed Fix
  The proposed fix is an upstream commit taken from gtk-3-20 branch:
  https://git.gnome.org/browse/gtk+/commit/?id=10c3a2483635d1c1

  # Test Case
  https://bugzilla.gnome.org/show_bug.cgi?id=769287#c0 has a test case.

  # Regression Potential
  The bug is fixed in GTK+ 3.20.9, so the fix was already present in the 
version that shipped with Yakkety. I am not aware of any regressions.

  -
  choosing action like New Tab, New Folder, Select Items Matching, will make 
nautilus lag (unresponsive)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 25 20:52:21 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+685+36'"
  InstallationDate: Installed on 2016-03-24 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1562002/+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 1676232] [NEW] No HDMI 5.1 profile listed for card, only 7.1

[Fred]

Public bug reported:

I have researched and requested help on Launchpad two times and not had any 
responses what do to next. There is no HDMI 5.1 profile available There is 7.1 
HDMI and it functions perfectly (sans missing channels on a 5.1 audio system). 
Please see below how the profile isn't detected and made available? Please 
direct me to a proper way to fix this. On a fresh install Ubuntu 16.04.2 LTS
Release:16.04


Thanks.

___1 card(s) available.
index: 0
name: 
driver: 
owner module: 6
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel"
alsa.long_card_name = "HDA Intel at 0xdf40 irq 33"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "293e"
device.product.name = "82801I (ICH9 Family) HD Audio Controller"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
input:analog-stereo: Analog Stereo Input (priority 60, 
available: unknown)
output:analog-stereo: Analog Stereo Output (priority 6000, 
available: unknown)
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex 
(priority 6060, available: unknown)
output:iec958-stereo: Digital Stereo (IEC958) Output (priority 
5500, available: unknown)
output:iec958-stereo+input:analog-stereo: Digital Stereo 
(IEC958) Output + Analog Stereo Input (priority 5560, available: unknown)
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5400, available: unknown)
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) 
Output + Analog Stereo Input (priority 5460, available: unknown)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 300, available: unknown)
output:hdmi-surround71+input:analog-stereo: Digital Surround 
7.1 (HDMI) Output + Analog Stereo Input (priority 360, available: unknown)
off: Off (priority 0, available: unknown)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D3p:   fhess  5316 F...m pulseaudio
 /dev/snd/controlC0:  fhess  5316 F pulseaudio
CurrentDesktop: GNOME
Date: Sun Mar 26 19:03:55 2017
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_Jack: Digital Out, HDMI
Symptom_Type: None of the above
Title: [HP Pavilion dv7 Notebook PC, Nvidia MCP77/78 HDMI, Digital Out, HDMI] 
Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/01/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 30F4
dmi.board.vendor: Compal
dmi.board.version: 99.75
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd10/01/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.13:rvnCompal:rn30F4:rvr99.75:cvnCompal:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: F.13
dmi.sys.vendor: Hewlett-Packard
modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-03-26T01:09:33.814682

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  No HDMI 5.1 profile listed for card, only 7.1

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have researched and requested help on Launchpad two times and not had any 
responses what do to next. There is no HDMI 5.1 profile available There is 7.1 
HDMI and it functions perfectly (sans missing channels on a 5.1 audio system). 
Please see below how the profile isn't detected and made available? Please 
direct me to a proper way to fix this. On a fresh install 

[Touch-packages] [Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Nathan Dorfman]

** No longer affects: network-manager (Ubuntu)

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

Title:
  journald forwards to syslog with facility=KERN on everything

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

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1613751/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

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

Title:
  Second unity8 user session hangs with a black screen

Status in Canonical System Image:
  In Progress
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1046129] Re: Use New Radio/Check Assets for Gtk-2.0 Theme Consistency

[Martin Wimpress]

** Also affects: ubuntu-mate-artwork (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-mate-artwork (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

Title:
  Use New Radio/Check Assets for Gtk-2.0 Theme Consistency

Status in Ubuntu theme:
  Fix Committed
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Add new radio and check assets for use with gtk-2.0 Ambiance/Radiance
  for theme consistency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1046129/+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 1676219] [NEW] package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/accounts/services/google-im.service', which

[blood-stone]

Public bug reported:

running upgrade

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: account-plugin-google 0.12+15.04.20150415.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Sun Mar 26 16:15:12 2017
DpkgHistoryLog:
 Start-Date: 2017-03-26  16:15:00
 Commandline: aptdaemon role='role-commit-packages' sender=':1.135'
 Upgrade: rhythmbox-plugins:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
gir1.2-gst-plugins-base-1.0:amd64 (1.6.0-1ubuntu1, 1.6.3-1ubuntu1), 
rhythmbox-plugin-magnatune:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox-data:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox-plugin-cdrecorder:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox-plugin-zeitgeist:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
gir1.2-gstreamer-1.0:amd64 (1.6.0-1, 1.6.3-1ubuntu1), 
account-plugin-google:amd64 (0.12+15.04.20150415.1-0ubuntu2, 
0.12+15.10.20150723-0ubuntu1), gir1.2-rb-3.0:amd64 (3.2.1-1ubuntu3, 
3.2.1-1ubuntu3.1), librhythmbox-core9:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1)
DpkgTerminalLog:
 Preparing to unpack 
.../account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb ...
 Unpacking account-plugin-google (0.12+15.10.20150723-0ubuntu1) over 
(0.12+15.04.20150415.1-0ubuntu2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
DuplicateSignature: 
package:account-plugin-google:0.12+15.04.20150415.1-0ubuntu2:trying to 
overwrite '/usr/share/accounts/services/google-im.service', which is also in 
package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
ErrorMessage: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
InstallationDate: Installed on 2015-02-28 (757 days ago)
InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu3
SourcePackage: account-plugins
Title: package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
UpgradeStatus: Upgraded to wily on 2016-06-11 (288 days ago)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict third-party-packages wily

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

Title:
  package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to
  install/upgrade: trying to overwrite '/usr/share/accounts/services
  /google-im.service', which is also in package kde-config-telepathy-
  accounts 4:15.08.2-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  running upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: account-plugin-google 0.12+15.04.20150415.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 26 16:15:12 2017
  DpkgHistoryLog:
   Start-Date: 2017-03-26  16:15:00
   Commandline: aptdaemon role='role-commit-packages' sender=':1.135'
   Upgrade: rhythmbox-plugins:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
gir1.2-gst-plugins-base-1.0:amd64 (1.6.0-1ubuntu1, 1.6.3-1ubuntu1), 
rhythmbox-plugin-magnatune:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox-data:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox-plugin-cdrecorder:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox-plugin-zeitgeist:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
gir1.2-gstreamer-1.0:amd64 (1.6.0-1, 1.6.3-1ubuntu1), 
account-plugin-google:amd64 (0.12+15.04.20150415.1-0ubuntu2, 
0.12+15.10.20150723-0ubuntu1), gir1.2-rb-3.0:amd64 (3.2.1-1ubuntu3, 
3.2.1-1ubuntu3.1), librhythmbox-core9:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1)
  DpkgTerminalLog:
   Preparing to unpack 
.../account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb ...
   Unpacking account-plugin-google (0.12+15.10.20150723-0ubuntu1) over 
(0.12+15.04.20150415.1-0ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
  DuplicateSignature: 

[Touch-packages] [Bug 1676219] Re: package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/accounts/services/google-im.service', which i

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to
  install/upgrade: trying to overwrite '/usr/share/accounts/services
  /google-im.service', which is also in package kde-config-telepathy-
  accounts 4:15.08.2-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  running upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: account-plugin-google 0.12+15.04.20150415.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 26 16:15:12 2017
  DpkgHistoryLog:
   Start-Date: 2017-03-26  16:15:00
   Commandline: aptdaemon role='role-commit-packages' sender=':1.135'
   Upgrade: rhythmbox-plugins:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
gir1.2-gst-plugins-base-1.0:amd64 (1.6.0-1ubuntu1, 1.6.3-1ubuntu1), 
rhythmbox-plugin-magnatune:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox-data:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox-plugin-cdrecorder:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
rhythmbox-plugin-zeitgeist:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), 
gir1.2-gstreamer-1.0:amd64 (1.6.0-1, 1.6.3-1ubuntu1), 
account-plugin-google:amd64 (0.12+15.04.20150415.1-0ubuntu2, 
0.12+15.10.20150723-0ubuntu1), gir1.2-rb-3.0:amd64 (3.2.1-1ubuntu3, 
3.2.1-1ubuntu3.1), librhythmbox-core9:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1)
  DpkgTerminalLog:
   Preparing to unpack 
.../account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb ...
   Unpacking account-plugin-google (0.12+15.10.20150723-0ubuntu1) over 
(0.12+15.04.20150415.1-0ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
  DuplicateSignature: 
package:account-plugin-google:0.12+15.04.20150415.1-0ubuntu2:trying to 
overwrite '/usr/share/accounts/services/google-im.service', which is also in 
package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
  InstallationDate: Installed on 2015-02-28 (757 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu3
  SourcePackage: account-plugins
  Title: package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.08.2-0ubuntu1
  UpgradeStatus: Upgraded to wily on 2016-06-11 (288 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1676219/+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 1353013] Re: Popping/Crackling sound when playing audio in Ubuntu 14.04

[mitchej123]

I found this issue a while ago and ended up going with the solution of
using the front audio jack which caused no issues...until the mini jack
got broken off inside and I was forced to use the rear jack again which
resurfaced the crackling issue.

The weird part is I completely disconnected the front audio jack
cabling, and yet it would still periodically crackle and attempt to
switch to the headphone jack.  The workaround I found was to force
disable the front jack using hdajackretask from alsa-tools-gui:
http://askubuntu.com/a/448138

Leaving this here in case anyone else finds it useful.

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

Title:
  Popping/Crackling sound when playing audio in Ubuntu 14.04

Status in nvidia-hdmi-pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When listening to audio (pandora internet radio, youtube, etc.), I get
  a repeated popping/crackling sound. When I look at the sound settings
  while this is happening, I see "Headphone Output" rapidly appearing
  and then disappearing in the "Play Sound Through" section. The
  appearance and disappearance of "Headphone Output" coincides with the
  popping and crackling of the sound.

  I am wondering if it has anything to do with the fact that my Nvidia
  card has a built-in HDMI card that might be interfering with my
  onboard sound:

  $ cat /proc/asound/cards
   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf722 irq 54
   1 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xf708 irq 55
  cat /proc/asound/modules
   0 snd_hda_intel
   1 snd_hda_intel

  Obviously blacklisting "snd_hda_intel" in
  /etc/modprobe.d/blacklist.conf won't work, because it then disables
  all sound (both onboard and nvidia are listed as snd_hda_intel).

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1856 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 10:17:34 2014
  InstallationDate: Installed on 2014-04-17 (109 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-205:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2014-08-04T12:00:53.999120
  mtime.conffile..etc.pulse.default.pa: 2014-08-04T12:18:08.532386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-hdmi-pulseaudio/+bug/1353013/+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 1676203] [NEW] Strange pixels after wakeup

[Kavenon]

Public bug reported:

After ubuntu wakeup I experience a lot of pixels on desktop and on every
context menu (after right click).

You can see the problem in the attached screenshoot.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Jest katalogiem: 
'/proc/driver/nvidia/gpus/:04:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Mar 26 19:55:41 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics [1043:1a6d]
   Subsystem: ASUSTeK Computer Inc. GK208M [GeForce 920M] [1043:1a6d]
InstallationDate: Installed on 2016-10-06 (170 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
LightdmLog: [+17450.89s] DEBUG: User /org/freedesktop/Accounts/User126 added
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 007: ID 13d3:3423 IMC Networks
 Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X555LJ
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555LJ.504
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555LJ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LJ.504:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X555LJ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Mar 26 07:58:24 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors: evdev: BluetoothMouse3600: Unable to open evdev device 
"/dev/input/event13".
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

** Attachment added: "Zrzut ekranu z 2017-03-25 18-15-01.png"
   
https://bugs.launchpad.net/bugs/1676203/+attachment/4846318/+files/Zrzut%20ekranu%20z%202017-03-25%2018-15-01.png

** Description changed:

  After ubuntu wakeup I experience a lot of pixels on desktop and on every
  context menu (after right click).
+ 
+ You can see the problem in the attached screenshoot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Jest katalogiem: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
-  GCC version:  gcc version 5.4.0 

[Touch-packages] [Bug 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Thomas Ward]

Sergio,

Also, I'm not 100% certain the other bug is not a dupe of this one,
because Yakkety.  Their workarounds of restarting dnsmasq, etc. still
didn't work on a 16.04 system (even restarting Network Manager didn't
help - dnsmasq was still dead for *everything*), and now I'm getting
issues where the domain is set proper with search domains, but I'm
'refused' from querying the domain assigned.

The DNS servers that *should* be assigned by the VPN are properly
handling the requests, so I don't know what's going on and will check
more later.  (Falling back to local `bind9` resolver in the mean time)

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

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675519/+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 1676199] [NEW] package gstreamer1.0-plugins-bad 1.8.3-1ubuntu0.2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcamerabin2.so', whi

[luis]

Public bug reported:

i want install kdnlive, but i dont know what happens !

ProblemType: Package
DistroRelease: Kali 2016.2
Package: gstreamer1.0-plugins-bad 1.8.3-1ubuntu0.2
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Mar 26 12:15:03 2017
ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcamerabin2.so', which is also in 
package gstreamer1.0-plugins-good:amd64 1.8.3-1ubuntu0.3
InstallationDate: Installed on 2016-12-02 (113 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.22kali1
 apt  1.2.19
SourcePackage: gst-plugins-bad1.0
Title: package gstreamer1.0-plugins-bad 1.8.3-1ubuntu0.2 failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcamerabin2.so', which is also in 
package gstreamer1.0-plugins-good:amd64 1.8.3-1ubuntu0.3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kali-rolling third-party-packages

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

Title:
  package gstreamer1.0-plugins-bad 1.8.3-1ubuntu0.2 failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-
  gnu/gstreamer-1.0/libgstcamerabin2.so', which is also in package
  gstreamer1.0-plugins-good:amd64 1.8.3-1ubuntu0.3

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  i want install kdnlive, but i dont know what happens !

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: gstreamer1.0-plugins-bad 1.8.3-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Mar 26 12:15:03 2017
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcamerabin2.so', which is also in 
package gstreamer1.0-plugins-good:amd64 1.8.3-1ubuntu0.3
  InstallationDate: Installed on 2016-12-02 (113 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.22kali1
   apt  1.2.19
  SourcePackage: gst-plugins-bad1.0
  Title: package gstreamer1.0-plugins-bad 1.8.3-1ubuntu0.2 failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcamerabin2.so', which is also in 
package gstreamer1.0-plugins-good:amd64 1.8.3-1ubuntu0.3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1676199/+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 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Thomas Ward]

Interesting, I can't reproduce with standard WPA2 wifi connections.

I wonder if it's specific to the combination of WPA2 Enterprise (with
custom DNS settings in the system) and then that being overridden by the
VPN and that causes some breakages.

I'll test in a few hours when I'm on such a network where I can test it.
(At my apartment, I have a WPA2 Enterprise network, but that seems to
properly show the right DNS and such... and I can't VPN to the apartment
when I'm *on* the Apartment's networking).

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

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675519/+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 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Thomas Ward]

Sergio,

No, however I would be happy to test later today.  The primary reason for my
having a backup local resolving bind9 was just for cases like this, but I'll 
test the DBUS method in a few hours and get back to 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/1675519

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675519/+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 1676192] [NEW] Wifi remains off after reboot

[lazarus01111]

Public bug reported:

I've created a bug report relating to this one days ago and had
forgotten to mention that my wifi is always off after any and every
reboot.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sun Mar 26 12:36:27 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-04-25 (335 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.1.1 dev wlp3s0 proto static metric 600 
 169.254.0.0/16 dev wlp3s0 scope link metric 1000 
 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.4 metric 600
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
C8A090  e897215f-3697-44f8-9676-c912b3554dad  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --  
----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  --  
----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  Wifi remains off after reboot

Status in network-manager package in Ubuntu:
  New

Bug description:
  I've created a bug report relating to this one days ago and had
  forgotten to mention that my wifi is always off after any and every
  reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Mar 26 12:36:27 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-25 (335 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.4 metric 600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
C8A090  e897215f-3697-44f8-9676-c912b3554dad  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: 

[Touch-packages] [Bug 1676179] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1676179/+attachment/4846194/+files/Stacktrace.txt

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

Title:
  webapp-container crashed with SIGABRT in __assert_fail_base()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  see -> https://bugs.launchpad.net/ubuntu/+source/webbrowser-
  app/+bug/1676176

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: webapp-container 0.23+17.04.20170321-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 26 10:59:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2017-03-22 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  ProcCmdline: webapp-container --app-id=ubuntu-amazon-default --webapp 
--enable-back-forward http://www.amazon.com/?tag=u1webapp-20
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f049e804729 "kref", file=file@entry=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=line@entry=727, 
function=function@entry=0x7f049e804750 "nouveau_pushbuf_data") at assert.c:92
   __GI___assert_fail (assertion=0x7f049e804729 "kref", file=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=727, function=0x7f049e804750 
"nouveau_pushbuf_data") at assert.c:101
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
  Title: webapp-container crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1676179/+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 1676179] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1676179/+attachment/4846196/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1676179/+attachment/4846185/+files/CoreDump.gz

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  webapp-container crashed with SIGABRT in __assert_fail_base()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  see -> https://bugs.launchpad.net/ubuntu/+source/webbrowser-
  app/+bug/1676176

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: webapp-container 0.23+17.04.20170321-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 26 10:59:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2017-03-22 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  ProcCmdline: webapp-container --app-id=ubuntu-amazon-default --webapp 
--enable-back-forward http://www.amazon.com/?tag=u1webapp-20
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f049e804729 "kref", file=file@entry=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=line@entry=727, 
function=function@entry=0x7f049e804750 "nouveau_pushbuf_data") at assert.c:92
   __GI___assert_fail (assertion=0x7f049e804729 "kref", file=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=727, function=0x7f049e804750 
"nouveau_pushbuf_data") at assert.c:101
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
  Title: webapp-container crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1676179/+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 1676179] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1676179/+attachment/4846195/+files/StacktraceSource.txt

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

Title:
  webapp-container crashed with SIGABRT in __assert_fail_base()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  see -> https://bugs.launchpad.net/ubuntu/+source/webbrowser-
  app/+bug/1676176

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: webapp-container 0.23+17.04.20170321-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 26 10:59:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2017-03-22 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  ProcCmdline: webapp-container --app-id=ubuntu-amazon-default --webapp 
--enable-back-forward http://www.amazon.com/?tag=u1webapp-20
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f049e804729 "kref", file=file@entry=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=line@entry=727, 
function=function@entry=0x7f049e804750 "nouveau_pushbuf_data") at assert.c:92
   __GI___assert_fail (assertion=0x7f049e804729 "kref", file=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=727, function=0x7f049e804750 
"nouveau_pushbuf_data") at assert.c:101
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
  Title: webapp-container crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1676179/+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 1676179]

[Apport retracing service]

StacktraceTop:
 __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f049e804729 "kref", file=file@entry=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=line@entry=727, 
function=function@entry=0x7f049e804750 <__PRETTY_FUNCTION__.6238> 
"nouveau_pushbuf_data") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f049e804729 "kref", 
file=file@entry=0x7f049e80470a "../../nouveau/pushbuf.c", line=line@entry=727, 
function=function@entry=0x7f049e804750 <__PRETTY_FUNCTION__.6238> 
"nouveau_pushbuf_data") at assert.c:101
 nouveau_pushbuf_data (push=push@entry=0x55937a841ef0, bo=0x55937a967530, 
offset=156540, length=1160) at ../../nouveau/pushbuf.c:727
 nouveau_pushbuf_data (push=push@entry=0x55937a841ef0, bo=bo@entry=0x0, 
offset=offset@entry=0, length=length@entry=0) at ../../nouveau/pushbuf.c:719
 pushbuf_submit (push=push@entry=0x55937a841ef0, chan=, 
chan=) at ../../nouveau/pushbuf.c:330

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

Title:
  webapp-container crashed with SIGABRT in __assert_fail_base()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  see -> https://bugs.launchpad.net/ubuntu/+source/webbrowser-
  app/+bug/1676176

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: webapp-container 0.23+17.04.20170321-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 26 10:59:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2017-03-22 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  ProcCmdline: webapp-container --app-id=ubuntu-amazon-default --webapp 
--enable-back-forward http://www.amazon.com/?tag=u1webapp-20
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f049e804729 "kref", file=file@entry=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=line@entry=727, 
function=function@entry=0x7f049e804750 "nouveau_pushbuf_data") at assert.c:92
   __GI___assert_fail (assertion=0x7f049e804729 "kref", file=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=727, function=0x7f049e804750 
"nouveau_pushbuf_data") at assert.c:101
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
  Title: webapp-container crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1676179/+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 1676176] Re: "problem in webapp container" ubuntu 17

[Op4]

and this for attached files -> https://bugs.launchpad.net/ubuntu/+source
/webbrowser-app/+bug/1676179

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

Title:
  "problem in webapp container" ubuntu 17

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  new build of ubuntu 17.04 -

  Linux David 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:28:34 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  running the Amazon webapp:

  ===
  Problem in webapp-container

  The problem cannot be reported

  You have some obsolete package versions installed. Please upgrade the
  following packages and check if the problem still occurs:

  gir1.2-glib-2.0, libcups, libegl1-mesa, libgbm1, libgirepositary-1.0-1, 
libgl1-mesa-dri, libgl1-mesa-glx, libglapi-mesa, libmirclient9, libmircommon7, 
libmircore1, libmirprotobuf3, libwayland-eg1-mesa
  ===

  got this error after installing 
  apt install snapd
  snap install hello-world
  apt-get --purge autoremove firefox
  apt-get install unity-tweak-tool 
  apt install unity-webapps-common

  then did a 
  apt update unity-webapps-common
  (long scroll with loys and lots of updates)
  completed successfully and without error (I assume)

  david@Merovingian:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  david@Merovingian:~$ apt-cache policy unity-webapps-common
  unity-webapps-common:
Installed: 2.4.17+15.10.20150616-0ubuntu2
Candidate: 2.4.17+15.10.20150616-0ubuntu2
Version table:
   *** 2.4.17+15.10.20150616-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  *expected* load of amazon site in browser
  *instead* loads momentarily and then fails with the following error

  david@Merovingian:~$ tail -f /var/log/syslog 
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Loading 
webview on /home/david/.local/share/ubuntu-amazon-default
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: Invalid 
webapp webapp definition: homepage not found or fails predicate isString
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: Could not 
open manifest file:  
"/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json"
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: 
QQmlExpression: Expression 
file:///usr/share/webbrowser-app/webcontainer/WebApp.qml:288:25 depends on 
non-NOTIFYable properties:
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: 
unity::action::qml::ActionManager::globalContext
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: qq= 
WebViewImplOxide_QMLTYPE_104(0x55937ac05180) 0x55937ad42ee0
  Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Start 
browsing
  Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Loaded 
18 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: 
[0326/105947.261983:ERROR:layer_tree_host_impl.cc(2174)] Forcing zero-copy tile 
initialization as worker context is missing
  Mar 26 10:59:49 Merovingian ubuntu-amazon-default.desktop[4179]: 
webapp-container: ../../nouveau/pushbuf.c:727: nouveau_pushbuf_data: Assertion 
`kref' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1676176/+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 1676179] [NEW] webapp-container crashed with SIGABRT in __assert_fail_base()

[Op4]

Public bug reported:

see -> https://bugs.launchpad.net/ubuntu/+source/webbrowser-
app/+bug/1676176

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: webapp-container 0.23+17.04.20170321-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Mar 26 10:59:49 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/webapp-container
InstallationDate: Installed on 2017-03-22 (4 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
ProcCmdline: webapp-container --app-id=ubuntu-amazon-default --webapp 
--enable-back-forward http://www.amazon.com/?tag=u1webapp-20
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: webbrowser-app
StacktraceTop:
 __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f049e804729 "kref", file=file@entry=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=line@entry=727, 
function=function@entry=0x7f049e804750 "nouveau_pushbuf_data") at assert.c:92
 __GI___assert_fail (assertion=0x7f049e804729 "kref", file=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=727, function=0x7f049e804750 
"nouveau_pushbuf_data") at assert.c:101
 nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
Title: webapp-container crashed with SIGABRT in __assert_fail_base()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: webbrowser-app (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash zesty

** Information type changed from Private to Public

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

Title:
  webapp-container crashed with SIGABRT in __assert_fail_base()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  see -> https://bugs.launchpad.net/ubuntu/+source/webbrowser-
  app/+bug/1676176

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: webapp-container 0.23+17.04.20170321-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 26 10:59:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2017-03-22 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  ProcCmdline: webapp-container --app-id=ubuntu-amazon-default --webapp 
--enable-back-forward http://www.amazon.com/?tag=u1webapp-20
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f049e804729 "kref", file=file@entry=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=line@entry=727, 
function=function@entry=0x7f049e804750 "nouveau_pushbuf_data") at assert.c:92
   __GI___assert_fail (assertion=0x7f049e804729 "kref", file=0x7f049e80470a 
"../../nouveau/pushbuf.c", line=727, function=0x7f049e804750 
"nouveau_pushbuf_data") at assert.c:101
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
  Title: webapp-container crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1676179/+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 1676176] Re: "problem in webapp container" ubuntu 17

[Op4]

https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1221086
also just occurred - not sure if related

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

Title:
  "problem in webapp container" ubuntu 17

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  new build of ubuntu 17.04 -

  Linux David 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:28:34 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  running the Amazon webapp:

  ===
  Problem in webapp-container

  The problem cannot be reported

  You have some obsolete package versions installed. Please upgrade the
  following packages and check if the problem still occurs:

  gir1.2-glib-2.0, libcups, libegl1-mesa, libgbm1, libgirepositary-1.0-1, 
libgl1-mesa-dri, libgl1-mesa-glx, libglapi-mesa, libmirclient9, libmircommon7, 
libmircore1, libmirprotobuf3, libwayland-eg1-mesa
  ===

  got this error after installing 
  apt install snapd
  snap install hello-world
  apt-get --purge autoremove firefox
  apt-get install unity-tweak-tool 
  apt install unity-webapps-common

  then did a 
  apt update unity-webapps-common
  (long scroll with loys and lots of updates)
  completed successfully and without error (I assume)

  david@Merovingian:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  david@Merovingian:~$ apt-cache policy unity-webapps-common
  unity-webapps-common:
Installed: 2.4.17+15.10.20150616-0ubuntu2
Candidate: 2.4.17+15.10.20150616-0ubuntu2
Version table:
   *** 2.4.17+15.10.20150616-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  *expected* load of amazon site in browser
  *instead* loads momentarily and then fails with the following error

  david@Merovingian:~$ tail -f /var/log/syslog 
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Loading 
webview on /home/david/.local/share/ubuntu-amazon-default
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: Invalid 
webapp webapp definition: homepage not found or fails predicate isString
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: Could not 
open manifest file:  
"/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json"
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: 
QQmlExpression: Expression 
file:///usr/share/webbrowser-app/webcontainer/WebApp.qml:288:25 depends on 
non-NOTIFYable properties:
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: 
unity::action::qml::ActionManager::globalContext
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: qq= 
WebViewImplOxide_QMLTYPE_104(0x55937ac05180) 0x55937ad42ee0
  Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Start 
browsing
  Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Loaded 
18 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: 
[0326/105947.261983:ERROR:layer_tree_host_impl.cc(2174)] Forcing zero-copy tile 
initialization as worker context is missing
  Mar 26 10:59:49 Merovingian ubuntu-amazon-default.desktop[4179]: 
webapp-container: ../../nouveau/pushbuf.c:727: nouveau_pushbuf_data: Assertion 
`kref' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1676176/+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 1676176] Re: "problem in webapp container" ubuntu 17

[Op4]

david@Merovingian:~$ unity-webapps-runner -ac

** (unity-webapps-runner:4789): WARNING **: Could not get a proper
accuracy from Geoclue (NONE)

** (unity-webapps-runner:4789): CRITICAL **:
open_webapp_with_container_with_url: assertion 'app_id != NULL' failed

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

Title:
  "problem in webapp container" ubuntu 17

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  new build of ubuntu 17.04 -

  Linux David 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:28:34 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  running the Amazon webapp:

  ===
  Problem in webapp-container

  The problem cannot be reported

  You have some obsolete package versions installed. Please upgrade the
  following packages and check if the problem still occurs:

  gir1.2-glib-2.0, libcups, libegl1-mesa, libgbm1, libgirepositary-1.0-1, 
libgl1-mesa-dri, libgl1-mesa-glx, libglapi-mesa, libmirclient9, libmircommon7, 
libmircore1, libmirprotobuf3, libwayland-eg1-mesa
  ===

  got this error after installing 
  apt install snapd
  snap install hello-world
  apt-get --purge autoremove firefox
  apt-get install unity-tweak-tool 
  apt install unity-webapps-common

  then did a 
  apt update unity-webapps-common
  (long scroll with loys and lots of updates)
  completed successfully and without error (I assume)

  david@Merovingian:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  david@Merovingian:~$ apt-cache policy unity-webapps-common
  unity-webapps-common:
Installed: 2.4.17+15.10.20150616-0ubuntu2
Candidate: 2.4.17+15.10.20150616-0ubuntu2
Version table:
   *** 2.4.17+15.10.20150616-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  *expected* load of amazon site in browser
  *instead* loads momentarily and then fails with the following error

  david@Merovingian:~$ tail -f /var/log/syslog 
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Loading 
webview on /home/david/.local/share/ubuntu-amazon-default
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: Invalid 
webapp webapp definition: homepage not found or fails predicate isString
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: Could not 
open manifest file:  
"/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json"
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: 
QQmlExpression: Expression 
file:///usr/share/webbrowser-app/webcontainer/WebApp.qml:288:25 depends on 
non-NOTIFYable properties:
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: 
unity::action::qml::ActionManager::globalContext
  Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: qq= 
WebViewImplOxide_QMLTYPE_104(0x55937ac05180) 0x55937ad42ee0
  Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Start 
browsing
  Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Loaded 
18 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: 
[0326/105947.261983:ERROR:layer_tree_host_impl.cc(2174)] Forcing zero-copy tile 
initialization as worker context is missing
  Mar 26 10:59:49 Merovingian ubuntu-amazon-default.desktop[4179]: 
webapp-container: ../../nouveau/pushbuf.c:727: nouveau_pushbuf_data: Assertion 
`kref' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1676176/+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 1676176] [NEW] "problem in webapp container" ubuntu 17

[Op4]

Public bug reported:

new build of ubuntu 17.04 -

Linux David 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:28:34 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

running the Amazon webapp:

===
Problem in webapp-container

The problem cannot be reported

You have some obsolete package versions installed. Please upgrade the
following packages and check if the problem still occurs:

gir1.2-glib-2.0, libcups, libegl1-mesa, libgbm1, libgirepositary-1.0-1, 
libgl1-mesa-dri, libgl1-mesa-glx, libglapi-mesa, libmirclient9, libmircommon7, 
libmircore1, libmirprotobuf3, libwayland-eg1-mesa
===

got this error after installing 
apt install snapd
snap install hello-world
apt-get --purge autoremove firefox
apt-get install unity-tweak-tool 
apt install unity-webapps-common

then did a 
apt update unity-webapps-common
(long scroll with loys and lots of updates)
completed successfully and without error (I assume)

david@Merovingian:~$ lsb_release -rd
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04

david@Merovingian:~$ apt-cache policy unity-webapps-common
unity-webapps-common:
  Installed: 2.4.17+15.10.20150616-0ubuntu2
  Candidate: 2.4.17+15.10.20150616-0ubuntu2
  Version table:
 *** 2.4.17+15.10.20150616-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu zesty/main i386 Packages
100 /var/lib/dpkg/status

*expected* load of amazon site in browser
*instead* loads momentarily and then fails with the following error

david@Merovingian:~$ tail -f /var/log/syslog 
Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Loading 
webview on /home/david/.local/share/ubuntu-amazon-default
Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: Invalid webapp 
webapp definition: homepage not found or fails predicate isString
Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: Could not open 
manifest file:  
"/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json"
Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: 
QQmlExpression: Expression 
file:///usr/share/webbrowser-app/webcontainer/WebApp.qml:288:25 depends on 
non-NOTIFYable properties:
Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: 
unity::action::qml::ActionManager::globalContext
Mar 26 10:59:46 Merovingian ubuntu-amazon-default.desktop[4179]: qq= 
WebViewImplOxide_QMLTYPE_104(0x55937ac05180) 0x55937ad42ee0
Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Start 
browsing
Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: qml: Loaded 18 
UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
Mar 26 10:59:47 Merovingian ubuntu-amazon-default.desktop[4179]: 
[0326/105947.261983:ERROR:layer_tree_host_impl.cc(2174)] Forcing zero-copy tile 
initialization as worker context is missing
Mar 26 10:59:49 Merovingian ubuntu-amazon-default.desktop[4179]: 
webapp-container: ../../nouveau/pushbuf.c:727: nouveau_pushbuf_data: Assertion 
`kref' failed.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  "problem in webapp container" ubuntu 17

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  new build of ubuntu 17.04 -

  Linux David 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:28:34 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  running the Amazon webapp:

  ===
  Problem in webapp-container

  The problem cannot be reported

  You have some obsolete package versions installed. Please upgrade the
  following packages and check if the problem still occurs:

  gir1.2-glib-2.0, libcups, libegl1-mesa, libgbm1, libgirepositary-1.0-1, 
libgl1-mesa-dri, libgl1-mesa-glx, libglapi-mesa, libmirclient9, libmircommon7, 
libmircore1, libmirprotobuf3, libwayland-eg1-mesa
  ===

  got this error after installing 
  apt install snapd
  snap install hello-world
  apt-get --purge autoremove firefox
  apt-get install unity-tweak-tool 
  apt install unity-webapps-common

  then did a 
  apt update unity-webapps-common
  (long scroll with loys and lots of updates)
  completed successfully and without error (I assume)

  david@Merovingian:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  david@Merovingian:~$ apt-cache policy unity-webapps-common
  unity-webapps-common:
Installed: 2.4.17+15.10.20150616-0ubuntu2
Candidate: 2.4.17+15.10.20150616-0ubuntu2
Version table:
   *** 2.4.17+15.10.20150616-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu zesty/main i386 Packages
   

[Touch-packages] [Bug 1676092] Re: Can't install audacious in Xenial depends not the right version

[Hans Joachim Desserud]

Thanks for taking your time to report this issue and help making Ubuntu
better.

I don't get an error message like this when attempting to install
audacious on Ubuntu 16.04.

>(is it the same version with a different name? )

It's two different versions. Though from what I can see
(https://launchpad.net/ubuntu/+source/gtk+2.0),  is version
"2.24.30-1ubuntu1.16.04.1" so far only available in the -proposed
archive. In other words, it hasn't gone through all the steps to be
pushed out as an official update. Have you installed packages from
-proposed? If that is the case, there might be additional rebuilds of
libraries like gtk2-engines-pixbuf needed before it can be released.
I've taken the liberty of marking gtk2.0 as also affected just in case.

Could you please add the whole error message you got when attempting to
install adacious?

** Tags added: xenial

** Also affects: gtk+2.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can't install audacious in Xenial depends not the right version

Status in audacious package in Ubuntu:
  New
Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  When trying to install Audacious I need to install it's dependancy
  gtk2-engines-pixbuf which can't be installed, because it needs
  "libgtk2.0-0 (= 2.24.30-1ubuntu1)" but " 2.24.30-1ubuntu1.16.04.1" is
  installed. (is it the same version with a different name? )

  Therefore, no Audacious… :-/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1676092/+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 1316873] Re: Left mouse button stops working

[Olaf Waszkewitz]

The latest Nvidia proprietary driver update in Ubuntu 16.04 (automated
updates) caused my left mouse button to fail after a while. I tried
several mice and USB ports, all the same. Login out and in a gain is a
remedy. Restart not necessary. It feels as this is a lightdm bug.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316873/+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 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Sergio Callegari]

Can we safely assume that bug 1675820 is a duplicate of this one?

In that case, dnsmasq seems to operate correctly. In fact, setting the
domain server with an explicit dbus command, that is

sudo qdbus --system org.freedesktop.NetworkManager.dnsmasq 
/uk/org/thekelleys/dnsmasq \
org.freedesktop.NetworkManager.dnsmasq.SetDomainServers "(" "8.8.8.8" ")"

makes the trick and gets name resolution operate correctly. It looks
like the fault is on network manager not passing the domain servers to
dnsmasq via dbus in the correct way (or at all).

Was a test of this sort practised in this case?

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

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675519/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Krzysztof]

*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921

I have lost 3 days to find out this solution. Fix it ASAP!

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1669643] Re: Wifi WPA2-PSK 4-Way Handshake Faliure

[Aron Xu]

** Package changed: network-manager (Ubuntu) => wpa (Ubuntu)

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

Title:
  Wifi WPA2-PSK 4-Way Handshake Faliure

Status in wpa package in Ubuntu:
  New

Bug description:
  After I upgraded to Ubuntu 17.04 yesterday, I started having this
  problem. My device will only connect to unsecured (public) WiFi
  networks. I tried booting into an older series kernel (4.8.0) and the
  issue persisted.

  I ran `sudo systemctl status network-manager` and got this:

  device (wlx501ac505fcbc): supplicant interface state: associating -> 4-way 
handshake
  sup-iface[0x55eb41e5bc20,wlx501ac505fcbc]: connection disconnected (reason 15)
  device (wlx501ac505fcbc): supplicant interface state: 4-way handshake -> 
disconnected
  device (wlx501ac505fcbc): Activation: (wifi) disconnected during association, 
asking for new key
  device (wlx501ac505fcbc): state change: config -> need-auth (reason 
'supplicant-disconnect') [50 60 8]
  device (wlx501ac505fcbc): supplicant interface state: disconnected -> inactive

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  2 20:55:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-04 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IpRoute:
   default via 192.168.42.129 dev enp0s20u2 proto static metric 100 
   169.254.0.0/16 dev enp0s20u2 scope link metric 1000 
   192.168.42.0/24 dev enp0s20u2 proto kernel scope link src 192.168.42.246 
metric 100
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   enp0s20u2  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/4  Wired connection 1  
474aac38-e4d8-4102-b2eb-c5cc6bdb17aa  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   AC:37:43:7C:B4:57  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   wlx501ac505fcbcwifi  disconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1669643/+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 1669758] Re: Centrino Wireless-N 1000 not working on 16.10

[Aron Xu]

** Package changed: network-manager (Ubuntu) => 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/1669758

Title:
  Centrino Wireless-N 1000 not working on 16.10

Status in linux package in Ubuntu:
  New

Bug description:
  Summary
  Wifi is not working on Centrino Wireless-N 1000 not working on 16.10, but 
does work on windows.

  Please see following

  http://paste.ubuntu.com/24101344/
  
http://askubuntu.com/questions/887257/device-not-ready-wifi-not-working-on-ubuntu-16-10
  https://ubuntuforums.org/showthread.php?t=2354116=13615105#post13615105

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669758/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1676150] [NEW] Xorg freeze

[Andreas Schultz]

Public bug reported:

System freezes with black screen. Only kernels older than 4.8 work.

All current 4.10 kernels do not work.
System is a HP Compaq 6910p Laptop.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu2
Uname: Linux 4.6.0-040600rc1-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Mar 26 13:30:51 2017
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to zesty on 2016-11-05 (140 days ago)

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


** Tags: amd64 apport-bug freeze third-party-packages zesty

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  System freezes with black screen. Only kernels older than 4.8 work.

  All current 4.10 kernels do not work.
  System is a HP Compaq 6910p Laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  Uname: Linux 4.6.0-040600rc1-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Mar 26 13:30:51 2017
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2016-11-05 (140 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1676150/+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 1664748] Re: wifi connection drops, reconnects every 10 minutes

[Aron Xu]

Hi Dustin,

I would like to know which version of Ubuntu are you running on your
laptop? Specifically, I want to know what's behaving as your dhcp
client, is it dhclient or systemd-networkd?

Requesting IP addresses from two interfaces on the same machine to one
DHCP server is sometimes causing trouble because in systemd-networkd it
sends Client-Identifier to the server (which is about your D-Bus
machine-id), and some DHCP server (as far as I know at least some
versions of ISC DHCP Server) will take Client-Identifier as precedence
over the interface mac address, thus generating IP address allocation
problem.

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  wifi connection drops, reconnects every 10 minutes

Status in maas package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I recently moved my home DHCP and DNS server over to MAAS (2.1.3 from
  xenial-updates).

  Since doing so, I've noticed that my wifi connection drops and
  reconnects (with corresponding Unity pop-up notifications) exactly
  every 10 minutes.

  I suppose this is due to the fact that MAAS sets DHCP leases to 10
  minutes by default?

  Has anyone else noticed this behavior?

  Is there a suitable workaround?  Increasing the DHCP lease time?
  Using static addresses?  Something else?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1664748/+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 1571882] Re: 5GHz Wi-Fi Intermittently Disconnects on Dell Latitude 3340

[Aron Xu]

This looks more likely to be a kernel (driver) issue, reassigning.

** Package changed: network-manager (Ubuntu) => linux-lts-wily (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/1571882

Title:
  5GHz Wi-Fi Intermittently Disconnects on Dell Latitude 3340

Status in linux-lts-wily package in Ubuntu:
  New

Bug description:
  When connected to a 5GHz (802.11ac) WPA2 wireless network with UFW firewall 
enabled at system startup , I experience intermittent issues where the Wi-Fi 
completely disconnects and the 5G network is no longer displayed in the list of 
Wi-Fi Networks.
  Toggling the "Enable Wi-Fi" option resets the Wi-Fi and allows the user to 
reconnect.

  The latest A10 firmware version is installed on the laptop.

  I confirmed that the 5G network was still up and running , so the issue is 
most likely not on the router network end.
  I have no custom firewall rules that would cause this behaviour , but I do 
see a lot of multicast address resolution requests being blocked in the ufw 
logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-35-generic 4.2.0-35.40~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 18:32:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-03 (45 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1571882/+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 1326536] Re: libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd resolution behaviour on the VM

[Nathan Dorfman]

Right, my hack is almost the same as --no-hosts, it just doesn't require
patching libvirt.

Do you need that entry in your /etc/hosts? If you have a real DNS name,
you might not need it at all. If not, but you have a static IP address,
you could use that in the hosts file instead of 127.0.1.1.

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

Title:
  libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in
  odd resolution behaviour on the VM

Status in libvirt package in Ubuntu:
  Triaged
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  When libvirt configures / starts up dnsmasq on the host, it does not
  pass --no-hosts, resulting in it reading in the /etc/hosts file from
  the host.

  The default ubuntu setup will have the host's hostname in /etc/hosts
  under 127.0.1.1. Since libvirt's dnsmasq is reading this file,
  anything querying that dnsmasq instance will resolve the host's
  hostname out of /etc/hosts.

  The result of this is any VM running on the host will resolve the
  host's hostname as 127.0.1.1. For example, if the host's hostname is
  BoxA, any VM running on the host will resolve BoxA to 127.0.1.1, which
  is not BoxA's actual address.

  Would recommend passing --no-hosts to dnsmasq when libvirt starts it
  up. If a user wants hardcoded hosts for their libvirt network, they
  can add them to /var/lib/libvirt/dnsmasq/default.addnhosts . If this
  is an acceptable solution, I'd be happy to write the patch up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1326536/+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 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675519/+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 1675353] Re: Network manager does not resolve dns names

[Aron Xu]

*** This bug is a duplicate of bug 1675519 ***
https://bugs.launchpad.net/bugs/1675519

** This bug has been marked a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing

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

Title:
  Network manager does not resolve dns names

Status in network-manager package in Ubuntu:
  New

Bug description:
  NM seems completely broken in 16.10.

  I use NM, wifi and several VPN connections.

  Expected behaviour:

  1. Connect NM to default wlan -> name resolution works without interuption 
and permanently
  2. Connection to Cisco Anyconnect (via openconnect) -> DNS servers sent via 
DHCP should be added to the resolver list, name resolution should work in 
destination network, routes adjusted accordingly
  3. Connect NM to foreign network (WPA2) -> DNS resolution sent via DHCP 
should be taken as default

  Current behaviour:

  NM starts dnsmasq by default (I commented the start line to fix
  issues). DNS resolution stops after some minutes.

  Removing dnsmasq fron NetworkManager.conf (as I did) allows for name
  resolution except for web browsers (neither Firefox nor Chromium use
  the systemd.resolver).

  5 minutes of inactivity on the network suffice for the name resolution
  to stop working. Have to reestablish network connection (sudo
  resolveconf -u does not work).

  This violates expectation 1

  NM connects via openconnect. In the settings I added additional DNS
  servers and domain searches. They are ignored by dnsmasq. Name
  resolution does not work.

  *Worksaround* -> enter IP-addresses in /etc/hosts.

  dig @server-ip returns the correct IP address for target services but
  Firefox and Chromium do not utilize these services. dnsmasq does not
  return the correct address.

  This violates expectation 2

  Entering a foreign but known network, DNS resolution stops after a
  while (5 minutes inactivity suffice).

  Summarizing:

  a. DNS resolution using VPN connections does not work (I use openvpn, 
openconnect and pptp).
  b. dnsmasq does not resolve dns names correctly in wlan situations
  c. dnsmasq conflicts with systemd.resolver
  d. Firefox and Chromium ignore systemd.resolver
  e. removing dnsmasq from NetworkManager.conf releaves the issue a little 
(resolution drop-outs do not occur so frequently)

  Comparison to plain Debian demonstrated that Debian does not start
  dnsmasq. This led to the elimination of my dns=dnsmaq line in
  NetworkManager.conf

  Comparison to Raspian demonstrated that Raspian uses wpa_supplicant to
  control dns name resolution. I have not tried this setup in Ubuntu
  yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar 23 11:28:21 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-27 (54 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 10.1.0.254 dev wlp4s0  proto static  metric 600 
   10.0.0.0/8 dev wlp4s0  proto kernel  scope link  src 10.1.0.168  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   172.16.199.0/24 dev vmnet8  proto kernel  scope link  src 172.16.199.1 
   192.168.31.0/24 dev vmnet1  proto kernel  scope link  src 192.168.31.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-03-23T11:24:00.888213
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
rsb_hs  7a8389dc-afd3-444b-a106-1974e9e74dff  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   vmnet1  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

   vmnet8  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ---- 

   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/3  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  

[Touch-packages] [Bug 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1675519

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675519/+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 1675820] Re: Network manager fails to set domain server in some circumstances

[Aron Xu]

*** This bug is a duplicate of bug 1675519 ***
https://bugs.launchpad.net/bugs/1675519

** This bug has been marked a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing

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

Title:
  Network manager fails to set domain server in some circumstances

Status in network-manager package in Ubuntu:
  New

Bug description:
  Occasionally, after a resume from an update, network manager starts
  behaving strangely, not setting the DomainServer for the network.

  This happens when resuming the laptop to a location where:
  - an additional ethernet card (which is the one to use) is attached via USB
  - configuring that ethernet card NM is set up to clone a given mac address 
and get addresses only from dhcp, while the dns server is set manually in the 
network manager configuration
  - there are also free wifi signals to which NM tends to connect

  In this setup, NM fails to set the dns name in dnsmasq

  The issue gets worked around by either

  1) Using qdbus to call the dnsmasq dbus method to set the domain
  server. In this case the solution is temporary. Namely when NM is
  asked to disconnect from the net and then to reconnect, the issue
  comes again; or

  2) Killing dnsmasq. In this case, dnsmasq ia automatically restarted
  and everything starts working fine; or

  3) Restarting NM itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 24 16:22:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1197 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.143.1.254 dev enx0050b61af5c1  proto static  metric 100 
   10.143.0.0/19 dev enx0050b61af5c1  proto kernel  scope link  src 
10.143.20.139  metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2017-01-10 (73 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675820/+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 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Confirmed

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1613751/+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 1618839] Re: Regression: WiFi connection reconnects, but dead, after waking from standby

[Kseniya Blashchuk]

*** This bug is a duplicate of bug 1631241 ***
https://bugs.launchpad.net/bugs/1631241

Same for me on Dell XPS 9550 with 16.04

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

Title:
  Regression: WiFi connection reconnects, but dead, after waking from
  standby

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Bug introduced somewhere between Ubuntu 14.04.3 and 16.04.1

  If my Thinkpad T420s awakes from standby, very often the last
  connected WiFi network is reconnected immediately, but the connection
  is dysfunctional.

  ifconfig shows a valid connection with an IPv4 address assigned for
  the wlp3s0 interface.

  But there is no traffic, no success on DNS queries on the connection.

  If I reconnect by clicking the connection in the nm-applet menu, all
  is fine again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1618839/+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 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Bug Watch Updater]

** Changed in: systemd (Debian)
   Status: Unknown => Confirmed

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

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Confirmed

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1613751/+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 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

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

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1613751/+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 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (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.
https://bugs.launchpad.net/bugs/1613751

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1613751/+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 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** 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.
https://bugs.launchpad.net/bugs/1613751

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1613751/+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 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Nathan Dorfman]

** Bug watch added: Debian Bug tracker #837893
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837893

** Also affects: systemd (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837893
   Importance: Unknown
   Status: Unknown

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

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1613751/+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 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Nathan Dorfman]

** Summary changed:

- NM and gnome-session seem to be syslogging with facility KERN
+ journald forwards to syslog with facility=KERN on everything

** Package changed: gnome-session (Ubuntu) => systemd (Ubuntu)

** Bug watch added: github.com/systemd/systemd/issues #5640
   https://github.com/systemd/systemd/issues/5640

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/5640
   Importance: Unknown
   Status: Unknown

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

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  Unknown
Status in network-manager package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  Unknown

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1613751/+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 1273752] Re: Can't Copy Crash Report Details to Clipboard

[corrado venturini]

Same problem with other system windows. see screenshot.
I know, I can copy same info from terminal using 'last' command...

** Attachment added: "screenshot from user account login history"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1273752/+attachment/4846032/+files/Screenshot%20login%20history.png

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

Title:
  Can't Copy Crash Report Details to Clipboard

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Often times, after receiving a crash report, if I click the "Continue"
  button it doesn't launch the browser for me to submit my crash to
  launchpad.net.

  Because of this, I'd always like to copy the crash report to my
  clipboard before clicking the continue button, so that I can manually
  provide this information into a bug report to launchpad.net.

  However, this option is not available.

  More over, there is absolutely *no way* to copy any text from this
  crash report's dialog window!

  1) You cannot ctrl-a to select all.
  2) Ctrl-c doesn't copy anything
  3) Right-clicking doesn't produce a context menu where you can select "Copy".

  This is an unfinished design. You should always give the user the
  ability to copy any text displayed in the UI.

  Next to the "Show/Hide details" button, I suggest adding a "Copy to
  Clipboard" button. If not this, please offer some way to achieve this
  from the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:

  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 28 10:21:00 2014
  InstallationDate: Installed on 2013-10-07 (113 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1273752/+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 1676115] Re: systemd-resolved spams the system log with useless “Processing query...” messages

[Anders Kaseorg]

Ah, zesty still has 232-19 but this is presumably fixed in zesty-
proposed’s 232-21ubuntu1.

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  systemd-resolved spams the system log with useless “Processing
  query...” messages

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  If you are running ‘journalctl -f’ to try to debug some other problem,
  you are constantly interrupted by zillions of these messages from
  systemd-resolved:

  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...

  This was fixed upstream in v233 by downgrading this message from log_info to 
log_debug:
  https://github.com/systemd/systemd/pull/5233

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1676115/+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 1676115] Re: systemd-resolved spams the system log with useless “Processing query...” messages

[dino99]

Dont get your spam:
oem@u64:~$ journalctl | grep query
Mar 26 07:15:44 u64 geoclue[2802]: Failed to query location: Error resolving 
“location.services.mozilla.com”: Name or service not known

and seems already been fixed:

systemd (232-21) unstable; urgency=medium

  * resolved: Downgrade "processing query..." message to debug.
It doesn't really add much value in normal operation and just spams the
log. (Closes: #858197)

-- Michael Biebl   Tue, 21 Mar 2017 19:52:17 +0100

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

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

Title:
  systemd-resolved spams the system log with useless “Processing
  query...” messages

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  If you are running ‘journalctl -f’ to try to debug some other problem,
  you are constantly interrupted by zillions of these messages from
  systemd-resolved:

  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...

  This was fixed upstream in v233 by downgrading this message from log_info to 
log_debug:
  https://github.com/systemd/systemd/pull/5233

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1676115/+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