[Touch-packages] [Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot

[thedarkwinter]

To add to that, I just manually updated another running webserver, and
boom. The apache+php webserver uses DNS to resolve the database server,
which it can no longer do after the update, bringing the site down.

It sends these incorrect TYPE62321 DNS queries to our DNS server.

22-Mar-2017 05:33:01.205 queries: info: client 172.16.x.x#59821
(mysql.internal.domain): query: mysql.internal.domain IN TYPE62321 +
(172.16.x.x)

In this case, restarting apache2 clears the issue. I don't know if
anything else also needs restarting (so i did a reboot after to be
sure).

If it helps, I also have traditional resolv.conf instead of resolvconf

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Fix Released
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Fix Released
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Fix Released
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[thedarkwinter]

Just like my earlier comment, this _fix_ *broke* a running system after
it was automatically applied.

Start-Date: 2017-03-22  04:17:12
Commandline: /usr/bin/unattended-upgrade
Upgrade: libc6:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), locales:amd64 
(2.23-0ubuntu6, 2.23-0ubuntu7), libc-bin:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), 
multiarch-support:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7)
End-Date: 2017-03-22  04:17:34

Immediately after that, the system is no longer able to resolve names.
On my DNS server, I can see this is sending queries of TYPE62321 instead
of A

22-Mar-2017 04:17:30.407 queries: info: client 172.16.x.x#63762
(host.interna.domain): query: host.interna.domain IN TYPE62321 +
(172.16.1.10)

A reboot clears the issue, but the point is that applying the update is
still a "critical" bug because it breaks [some] running systems. In this
case, the system is running apache+php. It might be that it only effects
certain things.

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Fix Released
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Fix Released
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Fix Released
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1672269] Re: [regression] Mixing screen rotation with mode changes makes the image squished

[mir-ci-bot]

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1672269

Title:
  [regression] Mixing screen rotation with mode changes makes the image
  squished

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

Bug description:
  [regression] Mixing screen rotation with mode changes makes the image
  squished

  This problem is visible in lp:mir but not in Mir 0.26 (zesty):

  1. Start a client
  2. Move the client to the top left of the screen.
  3. Rotate right (mirout rotate right)
  3. Lower the resolution (mirout mode 720x400)

  Expected: Rendering stays in correct proportions
  Observed: Rendering is squished out of proportion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1672269/+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 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot under Mir

[Daniel van Vugt]

That all said... why don't we just declare gnome-screenshot unsupported
if it's really just a client of gnome-shell. Doesn't Unity8 have other
adequate screenshotting mechanisms?

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+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 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot under Mir

[Daniel van Vugt]

"Is there some mir client api for scraping the screen?"

Yes, but it's also not nice. See src/utils/screencast.cpp. That's why I
suggest we need to fix Mir in bug 1660269.

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+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 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot under Mir

[Daniel van Vugt]

On one hand asking the shell to own screenshotting is nice and secure.

On the other hand, persisting with an architecture where apps don't work
unless processes other than the shell happen to be running is a bit
nasty in my opinion. And similarly anything that depends on a bus is
ugly IMHO. I've lost count of the number of times in recent months where
GTK apps refused to start because they were timing out waiting for some
process or bus to become available that didn't exist in Mir.

When you develop an app for a platform, like for Mir using just
libmirclient, there should ideally be zero other dependencies on the
system. Everything should be implemented or proxied through that one
library.

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+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 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot under Mir

[William Hua]

I don't know if that would be the easiest approach. It sounds to me like
having U8 implement that dbus interface would be the easiest and least
invasive solution, but then again, I'm not the one volunteering for that
:)

Is there some mir client api for scraping the screen? I'm worried about
whether or not that kind of change would be accepted upstream (there's
no wayland-specific code in gnome-screenshot). Also, how does it look
from a security perspective? The nice thing about that interface is that
the screenshot app never has direct access to the pixel data in the
first place (it's just file names that U8 would save the image data
directly to), and access to the interface could be restricted via
apparmor dbus rules.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

** Tags removed: gtk-mir

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+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 1670390] Re: Desktop applications don't get properly resized when launched in staged mode

[William Hua]

This should be fixed under U8 with the gtk just released in zesty.

Under miral-shell, there's a small regression which is fixed in the PPA:

https://launchpad.net/~attente/+archive/ubuntu/gtk-mir

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

Title:
  Desktop applications don't get properly resized when launched in
  staged mode

Status in Canonical System Image:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce the issue:

  1 - Put unity8 in staged mode
  2 - Launch a desktop application like kate or qtcreator

  Expected outcome:
  The launched application takes up the entire stage area

  Actual outcome:
  The launched application starts with some windowed size it wanted to have, 
not filling the entire stage area. As if launched in desktop mode.

  Comments:
  Leaving staged mode and going back into it again gets the application to 
resize correctly and fill the entire stage area.

  Going from desktop to staged mode while the desktop application is
  already running also works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670390/+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 1674389] Re: Session Indicator's "Suspend" button has no effect in Unity 8

[Daniel van Vugt]

** Tags added: unity8-desktop

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: 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/1674389

Title:
  Session Indicator's "Suspend" button has no effect in Unity 8

Status in Canonical System Image:
  New
Status in indicator-session package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing Unity 8 from a Zesty nightly iso install on March 17 2017.

  When clicking on the "Suspend" button in the session indicator,
  nothing happens.

  This may or may not be an indicator-session issue. I need to triage
  this and see where the breakage is, e.g. does it work in Unity 7 on
  Zesty, and are there are any DBus signatures that have changed in
  Zesty that would cause this

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674389/+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 1674869] [NEW] package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade: unable to open '/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operati

[moses]

Public bug reported:

while installing

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: qtbase5-dev 5.7.1+dfsg-2ubuntu4~1
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
Date: Wed Mar 22 08:18:13 2017
DuplicateSignature:
 package:qtbase5-dev:5.7.1+dfsg-2ubuntu4~1
 Unpacking qtbase5-dev:amd64 (5.7.1+dfsg-2ubuntu4~1) over 
(5.7.1+dfsg-2ubuntu3~2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-xZbwtA/073-qtbase5-dev_5.7.1+dfsg-2ubuntu4~1_amd64.deb 
(--unpack):
  unable to open 
'/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': 
Operation not permitted
ErrorMessage: unable to open 
'/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': 
Operation not permitted
InstallationDate: Installed on 2016-12-10 (101 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161210)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.4~rc2
SourcePackage: qtbase-opensource-src
Title: package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade: 
unable to open 
'/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': 
Operation not permitted
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade:
  unable to open '/usr/include/x86_64-linux-
  gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation not permitted

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  while installing

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: qtbase5-dev 5.7.1+dfsg-2ubuntu4~1
  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
  Date: Wed Mar 22 08:18:13 2017
  DuplicateSignature:
   package:qtbase5-dev:5.7.1+dfsg-2ubuntu4~1
   Unpacking qtbase5-dev:amd64 (5.7.1+dfsg-2ubuntu4~1) over 
(5.7.1+dfsg-2ubuntu3~2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xZbwtA/073-qtbase5-dev_5.7.1+dfsg-2ubuntu4~1_amd64.deb 
(--unpack):
unable to open 
'/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2016-12-10 (101 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161210)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4~rc2
  SourcePackage: qtbase-opensource-src
  Title: package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade: 
unable to open 
'/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1674869/+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 1674869] Re: package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade: unable to open '/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation

[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 qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1674869

Title:
  package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade:
  unable to open '/usr/include/x86_64-linux-
  gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation not permitted

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  while installing

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: qtbase5-dev 5.7.1+dfsg-2ubuntu4~1
  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
  Date: Wed Mar 22 08:18:13 2017
  DuplicateSignature:
   package:qtbase5-dev:5.7.1+dfsg-2ubuntu4~1
   Unpacking qtbase5-dev:amd64 (5.7.1+dfsg-2ubuntu4~1) over 
(5.7.1+dfsg-2ubuntu3~2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xZbwtA/073-qtbase5-dev_5.7.1+dfsg-2ubuntu4~1_amd64.deb 
(--unpack):
unable to open 
'/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2016-12-10 (101 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161210)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4~rc2
  SourcePackage: qtbase-opensource-src
  Title: package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade: 
unable to open 
'/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1674869/+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 1674389] Re: Session Indicator's "Suspend" button has no effect in Unity 8

[Charles Kerr]

Might be a two-parter bug.

On the indicator-session side, we need to handle "challenge" as a
response to CanSuspend / CanHibernate calls and, when calling
suspend/hibernate, allow interactivity. This is in the fix-suspend-on-u8
branch.

Even after this is done, u8's challenge prompt is the lockscreen, so the 
unintuitive UX is that you have to (appear to) unlock in order to suspend. So 
in u8,
1. we should consider whether a password prompt should be necessary for 
suspend, and
2. if prompt is necessary, Calls to login1.Suspend(interactive=True) should 
probably be handled more elegantly than showing the lockscreen prompt


** Changed in: indicator-session (Ubuntu)
   Importance: Undecided => High

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: 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/1674389

Title:
  Session Indicator's "Suspend" button has no effect in Unity 8

Status in indicator-session package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing Unity 8 from a Zesty nightly iso install on March 17 2017.

  When clicking on the "Suspend" button in the session indicator,
  nothing happens.

  This may or may not be an indicator-session issue. I need to triage
  this and see where the breakage is, e.g. does it work in Unity 7 on
  Zesty, and are there are any DBus signatures that have changed in
  Zesty that would cause this

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1674389/+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 1624407] Re: Add a 'quit' message that is app-wide, as opposed to mir_event_type_close_surface

[Daniel van Vugt]

Generally speaking fixing bug 1674749 (now bug 1671424) should be enough
for most apps in the short term.

I'm reminded of how Microsoft handles this problem...

WM_CLOSE: https://msdn.microsoft.com/en-
us/library/windows/desktop/ms632617(v=vs.85).aspx

WM_QUIT: 
https://msdn.microsoft.com/en-us/library/windows/desktop/ms632641(v=vs.85).aspx
"The WM_QUIT message is not associated with a window and therefore will never 
be received through a window's window procedure."

WM_POWERBROADCAST: https://msdn.microsoft.com/en-
us/library/windows/desktop/aa373247(v=vs.85).aspx

WM_ENDSESSION: https://msdn.microsoft.com/en-
us/library/windows/desktop/aa376889(v=vs.85).aspx

Each has a valid use case, and I don't think we can get away from
similarly wanting a 'quit' message in Mir eventually.

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

Title:
  Add a 'quit' message that is app-wide, as opposed to
  mir_event_type_close_surface

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Currently in unity8, when requesting to "Quit" a running application
  from the launcher, what happens is that qtmir goes through all its
  associated windows/surfaces, and closes them one by one. Supposedly,
  when the last window is closed, the application terminates itself (but
  this is not necessarily the case, see
  https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed-
  prop).

  This prevents application authors from doing proper cleanup before the
  app is closed. For example in Qt, the QCoreApplication::aboutToQuit()
  signal is emitted only after all windows have been closed, so the
  application doesn’t get a chance to e.g. save the list of open windows
  (real use case for multi-window browser application which saves the
  current session).

  This is similar to unity7’s implementation by the way, but I think
  it’s wrong. Surely there must be a way (maybe toolkit-specific) to
  request an app to terminate itself (and fall back to closing all
  windows if not).

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1624407/+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 1646648] Re: Unity8 crashes with SIGSEGV in qtmir::MirSurface::onCloseTimedOut () at ./src/modules/Unity/Application/mirsurface.cpp:917

[Daniel van Vugt]

Incomplete. This crash hasn't been seen on zesty since unity8
8.15+17.04.20161207.1-0ubuntu1

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

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

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

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

Title:
  Unity8 crashes with SIGSEGV in qtmir::MirSurface::onCloseTimedOut ()
  at ./src/modules/Unity/Application/mirsurface.cpp:917

Status in Canonical System Image:
  Incomplete
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity8.  This problem was most recently seen with package version 
8.15+17.04.20161116.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ded3a210b92755ec7de56b1bb4097103984eb123 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646648/+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 1646648] Re: Unity8 crashes with SIGSEGV in qtmir::MirSurface::onCloseTimedOut () at ./src/modules/Unity/Application/mirsurface.cpp:917

[Daniel van Vugt]

Are we maintaining Unity8 on 16.10 at all?

Unity8 for yakkety is 5 months out of date. I thought we were developing
for 17.04 only...?

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

Title:
  Unity8 crashes with SIGSEGV in qtmir::MirSurface::onCloseTimedOut ()
  at ./src/modules/Unity/Application/mirsurface.cpp:917

Status in Canonical System Image:
  Incomplete
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity8.  This problem was most recently seen with package version 
8.15+17.04.20161116.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ded3a210b92755ec7de56b1bb4097103984eb123 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646648/+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 1668053] Re: [unity8] kate, impossible to close "Print Preview" window

[Daniel van Vugt]

Window types generally have nothing to do with which window buttons
should be visible. Window type dictates if there is a titlebar, and if
so then...

Close button: Must always be visible because apps exist which have no
other way of closing their windows.

Maximize button: Should only be visible for a window whose resize
constraints allow it to be maximized.

Minimize button: Almost always visible, unless the window is modal to
its parent.

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

Title:
  [unity8] kate, impossible to close "Print Preview" window

Status in Canonical System Image:
  In Progress
Status in Mir:
  Incomplete
Status in Ubuntu UX:
  New
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 Unity 8
  [unity8] kate, impossible to close "Print Preview" window

  see attached screenshot
  Print Preview window doesn't have windows controls or a close button

  Launch Kate, from the menu File > Print Preview
  try to close the window, you can't because doh

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668053/+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 1671424] Re: qtmir destroys windows after requesting them to close

[Daniel van Vugt]

Indeed the close button and Alt+F4 should never ever destroy a window.

They should just send the window an event: mir_event_type_close_window
Then it's up to the app how to proceed.

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

Title:
  qtmir destroys windows after requesting them to close

Status in Canonical System Image:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Using unity7:
   * Open kate
   * write something very important in the text area
   * Press Alt+F4 because you're not very smart
   * Get dialog saying you have unsaved changes
   * You can:
 * save (which ends in a quit after saving)
 * cancel the close

  Using unity8
   * Open kate
   * write something very important in the text area
   * Press Alt+F4 because you're not very smart
   * You lost your very important text

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671424/+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 1672337] Re: [unity8] can't restore an app if you minimize it while a child window, menu or context menu is opened

[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/1672337

Title:
  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

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

Bug description:
  ubuntu 17.04 unity8

  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

  open whatever app, kate without Xmir, right click to open a context
  menu or just open a child window. minize the app then try to restore
  it by clicking on the icon on the launcher

  doesn't seem to work here

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672337/+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 1672983] Re: OSK fails to appear with GTK

[Daniel van Vugt]

AFAIK input methods like the OSK require a third-party process to
mediate between the toolkit and the shell, telling the shell when to pop
up/down the OSK. So not having that intermediary running (and/or with
sufficient privileges) is the problem.

Was it content-hub or something else? I can't remember. If it's not
UAL's job then Unity8 should have it running already as part of the
session.

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

Title:
  OSK fails to appear with GTK

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

Bug description:
  Ubuntu 17.04 Unity 8

  OSK doesn't work with Xmir or gtk3 
  enable the On Screen Keyboard (from indicator menu or from system settings)
  open gedit or terminix (without Xmir) and try to type something, OSK doesn't 
show, same with running on Xmir

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672983/+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 1668467] Re: gnome-calculator, you can open the Preferences window multiple times, making the window transparent the second time

[Daniel van Vugt]

Actually, this could easily be a side-effect of bug 1671424. Let's fix
that first.

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

Title:
  gnome-calculator, you can open the Preferences window multiple times,
  making the window transparent the second time

Status in Canonical System Image:
  Confirmed
Status in MirAL:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.04 unity8

  gnome-calculator, you can open the Preferences window many times,
  making the window transparent the second time (see screenshot)

  it doesn't work with About or Keyboard Shortcuts, only with
  Preferences.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668467/+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 1674865] [NEW] Printing operation doesn't start

[Deependra Dhakal]

Public bug reported:

Printer does not start.

The attachment below is the output of debug log, generated by from,

$ cupsctl LogLevel=debug
$ cancel -a
$ sudo less /var/log/cups/error_log

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.8
ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CupsErrorLog:
 E [22/Mar/2017:06:36:13 +0545] [Client 21] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/Canon-LBP2900) from localhost
 E [22/Mar/2017:06:37:24 +0545] [Client 8] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/Canon-LBP2900) from localhost
CurrentDesktop: Unity
Date: Wed Mar 22 06:45:17 2017
InstallationDate: Installed on 2017-02-22 (27 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A3A3ONmL
MachineType: TOSHIBA Satellite L840
Papersize: a4
PpdFiles: Canon-LBP2900: Generic text-only printer
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=6948ffd7-612e-4f3e-ae73-46d0f433dc7d ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.80
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd06/26/2012:svnTOSHIBA:pnSatelliteL840:pvrPSK8NL-00F004:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L840
dmi.product.version: PSK8NL-00F004
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug trusty

** Attachment added: "error_log.txt"
   
https://bugs.launchpad.net/bugs/1674865/+attachment/4842053/+files/error_log.txt

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

Title:
  Printing operation doesn't start

Status in cups package in Ubuntu:
  New

Bug description:
  Printer does not start.

  The attachment below is the output of debug log, generated by from,

  $ cupsctl LogLevel=debug
  $ cancel -a
  $ sudo less /var/log/cups/error_log

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CupsErrorLog:
   E [22/Mar/2017:06:36:13 +0545] [Client 21] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/Canon-LBP2900) from localhost
   E [22/Mar/2017:06:37:24 +0545] [Client 8] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/Canon-LBP2900) from localhost
  CurrentDesktop: Unity
  Date: Wed Mar 22 06:45:17 2017
  InstallationDate: Installed on 2017-02-22 (27 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A3A3ONmL
  MachineType: TOSHIBA Satellite L840
  Papersize: a4
  PpdFiles: Canon-LBP2900: Generic text-only printer
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=6948ffd7-612e-4f3e-ae73-46d0f433dc7d ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd06/26/2012:svnTOSHIBA:pnSatelliteL840:pvrPSK8NL-00F004:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L840
  dmi.product.version: PSK8NL-00F004
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1674296] Re: In Terminal app, when settings window is already opened clicking on the settings icon does not raise it

[Daniel van Vugt]

** Tags added: unity8-desktop

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** 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/1674296

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in Canonical System Image:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  Confirmed

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674296/+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 1674668] Re: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1118903, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1118903
   [enhancement] Mir lacks a software rendering backend (and doesn't work in 
virtual machines)

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

Title:
  unity-system-compositor crashed with SIGABRT in
  mir::fatal_error_abort()

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity-system-compositor 0.9.1+17.04.20170216-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
  Date: Mon Mar 20 16:42:30 2017
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2017-02-07 (41 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170207)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   mir::fatal_error_abort(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libmircore.so.1
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.12
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.12
   mir::graphics::OverlappingOutputGrouping::for_each_group(std::function const&) () from 
/usr/lib/x86_64-linux-gnu/libmirplatform.so.15
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.12
  Title: unity-system-compositor crashed with SIGABRT in 
mir::fatal_error_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.75-1ubuntu1
  version.lightdm: lightdm 1.21.5-0ubuntu1
  version.mesa: libegl1-mesa-dev 17.0.1-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1674668/+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 1673817] Re: update-secure-boot-policy behaving badly with unattended-upgrades

[Mathieu Trudel-Lapierre]

** Changed in: shim-signed (Ubuntu)
Milestone: None => ubuntu-17.03

** Changed in: shim-signed (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  update-secure-boot-policy behaving badly with unattended-upgrades

Status in shim-signed package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Currently, unattended-upgrades will automatically install all updates
  for those running development releases of Ubuntu (LP: #1649709)

  Today, my computer was acting very sluggish. Looking at my process
  list, I saw/ usr/sbin/update-secureboot-policy was using a log of CPU.

  I killed the process. I have a /var/crash/shim-signed.0.crash but
  since it's 750 MB, I didn't bother submitting it or looking at it
  more. Maybe it crashed because I killed the process. Also, I see that
  unattended-upgrades-dpkg.log is 722 MB.

  Today's update included both VirtualBox and the linux kernel.

  I am attaching an excerpt of /var/log/unattended-upgrades/unattended-
  upgrades-dpkg.log

  This message was repeated a very large number of times (but I only
  included it once in the attachment:

  "Invalid password

  The Secure Boot key you've entered is not valid. The password used must be 
  between 8 and 16 characters."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: shim-signed 1.23+0.9+1474479173.6c180c6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 17 11:15:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-23 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  SourcePackage: shim-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1673817/+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 1640561] Re: package python3-libapparmor 2.10.95-4ubuntu5 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package python3-libapparmor 2.10.95-4ubuntu5 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  having this trouble and i am new to ubuntu, please help

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: python3-libapparmor 2.10.95-4ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  9 17:33:41 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-11-08 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=63c80f06-d5ed-42a4-b94e-08a8b996817b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: apparmor
  Syslog: Nov  9 18:02:44 gurminder-Aspire-5745PG dbus[745]: [system] AppArmor 
D-Bus mediation is enabled
  Title: package python3-libapparmor 2.10.95-4ubuntu5 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[WolphFang]

It took me a week to figure out why I could not get networking to work
on my non-chroot desktop.

I had to add a blank file and reboot? WTF?

-- 
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 1674859] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1629638, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1674859/+attachment/4842038/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1674859/+attachment/4842044/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1674859/+attachment/4842046/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1674859/+attachment/4842047/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1674859/+attachment/4842048/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1674859/+attachment/4842049/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1629638

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  I was creating a new bootable usb to test for final beta and then this
  popped up on ubiquity.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-19
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Tue Mar 21 17:31:02 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2015-09-20 (548 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150920)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=e1869ded-823c-486c-8440-14a4466778e2 ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: Upgraded to zesty on 2017-03-14 (7 days ago)
  UserGroups:
   
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H97M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd06/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1674859/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Rally]

The libc6-udeb_2.19-0ubuntu6.11_amd64.udeb fix that was just released
fixes the name resolution issues and we're able to provision our systems
as normal again.

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Fix Released
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Fix Released
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Fix Released
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[s frahm]

Yes sir (jarnos), thank you. This same recurring Bug #1460396 by many
names. Is there a patch like this that also works on 16.04 Lubuntu LTS
?? Every time I have researched it over the years, there are variations
on this theme. This should be a core functionality of each LTS package
upon launch at minimum. What I am trying to get at, are the
possibilities of even more helpful suggestions and options upon install,
such as how large would you like /root to be? (say 1-5 GB) and how many
old kernel versions would you like to keep (2-3 minimum as a safe
default) Yes, pruning old kernels automagically could be dangerous, but
more so is crashing 1/2 completed upgrades IMHO. Thanks to all!

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1674680] Re: Deprecated rfcomm.conf still mentioned

[Dave Chiluk]

** Also affects: bluez (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

Title:
  Deprecated rfcomm.conf still mentioned

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  New

Bug description:
  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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: NM and gnome-session seem to be syslogging with facility KERN

[Nathan Dorfman]

This is actually getting worse in Debian stretch, and there affects
almost 2 dozen packages, so it might not even be the packages'
(NetworkManager, gnome-session) fault. Anyway, https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=858399

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

-- 
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:
  NM and gnome-session seem to be syslogging with facility KERN

Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

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/ubuntu/+source/gnome-session/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Launchpad Bug Tracker]

This bug was fixed in the package eglibc - 2.15-0ubuntu10.17

---
eglibc (2.15-0ubuntu10.17) precise-security; urgency=medium

  * REGRESSION UPDATE: Previous update introduce ABI breakage in
internal glibc query ABI
- Back out patches/any/CVE-2015-5180-regression.diff
  (LP: #1674532)

 -- Steve Beattie   Tue, 21 Mar 2017 08:49:32 -0700

** Changed in: eglibc (Ubuntu Precise)
   Status: Confirmed => Fix Released

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Fix Released
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Fix Released
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Fix Released
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1672099] Re: DNS loop, >5, 000 queries per second for minutes at a time

[Paul]

You're right, it turns out dnsmasq was only installed because I had
installed polipo, which depends on the dnsmasq package. Purging polipo
removes dnsmasq.

I have been running polipo (with config files unmodified from default)
for several years, including since fresh installing Ubuntu-Gnome 16.10.
Only since the upgrade to 17.04 two weeks ago has this problem emerged.
Presumably it will hit every user who installs polipo or dnsmasq in
17.04.

$ cat /etc/hosts
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.1
$ 
$ dpkg -l dnsmasq\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  dnsmasq2.76-5   all  Small caching DNS proxy and DHCP/
ii  dnsmasq-base   2.76-5   amd64Small caching DNS proxy and DHCP/
$ 
$ cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

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

Title:
  DNS loop, >5,000 queries per second for minutes at a time

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading a desktop to 17.04, several times a day a DNS storm
  occurs. The same A or  record is requested over and over again.
  The storm lasts 10 to 15 minutes and can clog name resolution
  entirely, making the computer unusable for that time.

  Mar 12 08:55:12 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:13 hostname systemd-resolved[1188]: message repeated 5401 times: 
[ Processing query...]
  Mar 12 08:55:13 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:13 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:14 hostname kernel: [185434.365153] proc_thermal :00:04.0: 
Unsupported event [0x84]
  Mar 12 08:55:19 hostname systemd-resolved[1188]: message repeated 40288 
times: [ Processing query...]
  Mar 12 08:55:19 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:19 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:25 hostname systemd-resolved[1188]: message repeated 44022 
times: [ Processing query...]
  Mar 12 08:55:25 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:25 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:31 hostname systemd-resolved[1188]: message repeated 43874 
times: [ Processing query...]

  Both Firefox and Transmission originated hostnames have appeared in
  the storms, so it does not seem like an individual application is
  causing the problem.

  There are so many requests that running tcpdump on a random port (port
  29381 is used below) soon catches part of the storm. Example output
  below. Note that throughout the duration of these captures, identical
  DNS requests were being sent from pretty much every other port as
  well.

  

  = Transmission looking up mgtracker.org, got stuck on this single hostname 
for =
  = about 15 minutes (this is just the tail end of yesterday morning's storm).  
 = 
  


  08:40:24.667302 IP localhost.29381 > 127.0.0.53.domain: 60802+% [1au] ? 
mgtracker.org. (42)
  E..F..@.@..5r..5.2.y  mgtracker.org...)
  08:40:24.685708 IP 127.0.0.53.domain > localhost.29381: 60802 0/0/1 (42)
  E..Fdd@.@..5.5r..2.y  mgtracker.org...)
  08:40:33.580735 IP localhost.29381 > 127.0.0.53.domain: 53746+% [1au] A? 
mgtracker.org. (42)
  E..F.+@.@.9F...5r..5.2.y  mgtracker.org...)
  08:40:33.594830 IP 127.0.0.53.domain > localhost.29381: 53746 6/0/1 A 
92.241.171.245, A 37.19.5.139, A 77.91.229.218, A 5.79.83.194, A 5.79.83.193, A 
37.19.5.155 (138)
  E.@.@.t8...5.5r.  
mgtracker.org..X..\X..%X..M[...X...OS..X...OS..X..%.)
  08:41:30.717640 IP localhost.29381 > 127.0.0.53.domain: 63667+% [1au] ? 
mgtracker.org. (42)
  E..F\.@.@..5r..5.2.y  mgtracker.org...)
  08:41:30.733855 IP 127.0.0.53.domain > localhost.29381: 63667 0/0/1 (42)
  E..F 

[Touch-packages] [Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Launchpad Bug Tracker]

This bug was fixed in the package eglibc - 2.19-0ubuntu6.11

---
eglibc (2.19-0ubuntu6.11) trusty-security; urgency=medium

  * REGRESSION UPDATE: Previous update introduced ABI breakage in
internal glibc query ABI
- Back out patches/any/CVE-2015-5180-regression.diff
  (LP: #1674532)

 -- Steve Beattie   Tue, 21 Mar 2017 03:28:13 -0700

** Changed in: eglibc (Ubuntu Trusty)
   Status: Confirmed => Fix Released

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Fix Released
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Fix Released
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Fix Released
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1444656] Re: GnuTLS TLS 1.2 handshake failure

[Mathew Hodson]

** No longer affects: gnutls26 (Ubuntu)

** Tags removed: ssl tls
** Tags added: patch trusty

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

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

Title:
  GnuTLS TLS 1.2 handshake failure

Status in gnutls26 source package in Trusty:
  Triaged

Bug description:
  I'm experiencing the same issue as here:

  http://comments.gmane.org/gmane.network.gnutls.general/3713

  
  I came across a SSL handshake problem with gnutls-cli when connecting to 
  some websites, see below. It is somehow specific to gnutls as 
  openssl/Chrome/Firefox can connect fine. 

  Is this is a bug in gnutls or do you have any ideas how to
  troubleshoot it?

  $ gnutls-cli --version
  gnutls-cli (GnuTLS) 2.12.23
  Packaged by Debian (2.12.23-12ubuntu2.1)

  $ gnutls-cli www.openlearning.com
  Resolving 'www.openlearning.com'...
  Connecting to '119.9.9.205:443'...
  *** Fatal error: A TLS fatal alert has been received.
  *** Received alert [40]: Handshake failed
  *** Handshake has failed
  GnuTLS error: A TLS fatal alert has been received.

  $ gnutls-cli sequencewiz.com
  Resolving 'sequencewiz.com'...
  Connecting to '50.112.144.117:443'...
  *** Fatal error: A TLS packet with unexpected length was received.
  *** Handshake has failed
  GnuTLS error: A TLS packet with unexpected length was received.

  Thank you,

  
  Please back port the latest GnuTLS to Trusty as it is an LTS release and 
clearly GnuTLS 2.12 is an old branch.

  I've also attached packet captures of this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/trusty/+source/gnutls26/+bug/1444656/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Launchpad Bug Tracker]

This bug was fixed in the package glibc - 2.23-0ubuntu7

---
glibc (2.23-0ubuntu7) xenial-security; urgency=medium

  * REGRESSION UPDATE: Previous update introduced ABI breakage in
internal glibc query ABI
- Revert patches/any/CVE-2015-5180-regression.diff
  (LP: #1674532)

 -- Steve Beattie   Tue, 21 Mar 2017 08:54:23 -0700

** Changed in: glibc (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Confirmed
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Fix Released
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Fix Released
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1674680] Re: Deprecated rfcomm.conf still mentioned

[Mathew Hodson]

** Changed in: bluez (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Deprecated rfcomm.conf still mentioned

Status in bluez package in Ubuntu:
  New

Bug description:
  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 703800] Re: init: restart command fails to restart main process when pre-stop stanza exists

[dino99]

** Tags removed: glucid lucid
** Tags added: trusty

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

Title:
  init: restart command fails to restart main process when pre-stop
  stanza exists

Status in upstart :
  Triaged
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  While testing the portmap daemon's recent changes in Ubuntu which
  cause statd to properly follow it on stop/start, I tried to restart
  portmap, only to find that it was not in fact restarted.

  This happens with any job that has a pre-stop. The reason is that in
  job_restart(), the code does this:

  
  job_change_goal (job, JOB_STOP);
  job_change_goal (job, JOB_START);

  job_change_goal will return as soon as the *first* state change has
  been completed. If there is no pre-stop, that is the change from
  JOB_RUNNING to JOB_KILLED, which does dutifully kill the main process.

  However, if there is a pre-stop, the pre-stop is run, but then
  job_change_state returns to job_change_goal, which then returns to
  job_restart, which then changes the goal back to start, which makes
  the new job_next_state() one that will bypass the change to
  JOB_KILLED.

  This was found on upstart v0.6.7-3 in Ubuntu, but also exists in the
  code in the current trunk.

  TEST CASE

  1. create job file /etc/init/test-restart-prestop.conf  with this content:
  # test-restart-prestop

  pre-stop exec /bin/true

  exec /bin/sleep 3600
  2. run "start test-restart-prestop" -- record pid of job
  3. immediately run "restart test-restart-prestop" -- if bug is present, pid 
remains the same when it should be a new pid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/703800/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

[Benjamin Blanchard]

I also had the issue on a fresh Ubuntu 16.04, the applet not working
properly after resuming from suspend.

But I may have something to help here. A few days ago, I didn't had the
issue on a previous install, so I tried the two changes I made on that
one suspend-related.

First, I enabled hibernation, but it didn't change anything, still the
bug after resume.

And then, I installed tlp, basic with no modification, and it now works
properly every time.

Hope that may help.

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

Title:
  cannot view wifi networks after re-enabling wifi

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

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Adam Conrad]

** Changed in: glibc (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: glibc (Ubuntu Xenial)
   Importance: Undecided => Critical

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

** Changed in: eglibc (Ubuntu Precise)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

** Changed in: eglibc (Ubuntu Trusty)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

** Changed in: glibc (Ubuntu Xenial)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Confirmed
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Confirmed
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1672983] Re: OSK fails to appear with GTK

[Ted Gould]

** No longer affects: ubuntu-app-launch (Ubuntu)

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

Title:
  OSK fails to appear with GTK

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

Bug description:
  Ubuntu 17.04 Unity 8

  OSK doesn't work with Xmir or gtk3 
  enable the On Screen Keyboard (from indicator menu or from system settings)
  open gedit or terminix (without Xmir) and try to type something, OSK doesn't 
show, same with running on Xmir

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672983/+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 1670704] Re: No way to discern multiple versions of the same app (from different sources)

[Ted Gould]

** Changed in: ubuntu-app-launch (Ubuntu)
   Importance: Undecided => Low

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

Title:
  No way to discern multiple versions of the same app (from different
  sources)

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  In the new world there's basically an infinite number of the same
  application you can have installed at the same time:

  - snap
- multiple different snaps can ship the same application
  - libertine
- you can have multiple containers with the same application
  - deb
- you could have a PPA added that has the same application under a 
different package name

  Today the result is that the app drawer shows all of them, in
  undefined order. This makes it impossible to know which of them you
  launch.

  === Proposal 1 ===

  In the app drawer, have "badges" for apps that have multiple versions
  installed, and a drop-down to select between the different versions.

  Since we'd be grouping in the app drawer, I'd propose to group
  elsewhere in the shell (launcher, switcher), with icon badges
  indicating for each top-level window.

  === Proposal 2 ===

  Have all the different versions listed as usual, but have unique
  badges for those that have multiple versions.

  In this case we'd treat all of them as completely separate in the rest
  of the shell as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 15:15:58 2017
  InstallationDate: Installed on 2016-05-06 (304 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (105 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670704/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Adam Conrad]

** Changed in: glibc (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Confirmed
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  New
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  New

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 703800] Re: init: restart command fails to restart main process when pre-stop stanza exists

[Paul Draper]

How is systemd relevant?

Precise is still supported. Trusty will be supported until 2019.

Neither of those have systemd.

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

Title:
  init: restart command fails to restart main process when pre-stop
  stanza exists

Status in upstart :
  Triaged
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  While testing the portmap daemon's recent changes in Ubuntu which
  cause statd to properly follow it on stop/start, I tried to restart
  portmap, only to find that it was not in fact restarted.

  This happens with any job that has a pre-stop. The reason is that in
  job_restart(), the code does this:

  
  job_change_goal (job, JOB_STOP);
  job_change_goal (job, JOB_START);

  job_change_goal will return as soon as the *first* state change has
  been completed. If there is no pre-stop, that is the change from
  JOB_RUNNING to JOB_KILLED, which does dutifully kill the main process.

  However, if there is a pre-stop, the pre-stop is run, but then
  job_change_state returns to job_change_goal, which then returns to
  job_restart, which then changes the goal back to start, which makes
  the new job_next_state() one that will bypass the change to
  JOB_KILLED.

  This was found on upstart v0.6.7-3 in Ubuntu, but also exists in the
  code in the current trunk.

  TEST CASE

  1. create job file /etc/init/test-restart-prestop.conf  with this content:
  # test-restart-prestop

  pre-stop exec /bin/true

  exec /bin/sleep 3600
  2. run "start test-restart-prestop" -- record pid of job
  3. immediately run "restart test-restart-prestop" -- if bug is present, pid 
remains the same when it should be a new pid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/703800/+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]

And about the bug #1535666 i think is not the case, since the pt-BR
version of Ubuntu the folder name is called Downloads, we don't have a
100% accurate word for this in portuguese, so we don't translate it...

-- 
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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Adam Conrad]

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

** Also affects: glibc (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: eglibc (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: eglibc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: eglibc (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: eglibc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: eglibc (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: eglibc (Ubuntu Precise)
   Importance: Undecided => Critical

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

** Changed in: eglibc (Ubuntu Trusty)
   Importance: Undecided => Critical

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

** Changed in: eglibc (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: eglibc (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: glibc (Ubuntu Precise)
   Status: New => Invalid

** Changed in: glibc (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: glibc (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Confirmed
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  New
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  New

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 did this sir, there's no log with this name there... There's an
attachment showing the whole folder.

My system is pt-BR by the way...

** Attachment added: "folder.png"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1673939/+attachment/4841979/+files/folder.png

-- 
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 1650972] Re: No .vapi in Zesty

[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/1650972

Title:
  No .vapi in Zesty

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The .vapi file is missing from the packaging in the Zesty version.
  This triggers some build to fail in elementary for example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650972/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Eric Horne]

is it valid to run the broken install, when it breaks manually pull down
the new package that you pushed and install that, then let it continue
with the installation?

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[mohican]

Welcome Phil,
did you try the fix from post #8 ?
and rebooting from Linux (not from Windows) as I suggest in my post #16.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  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_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  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.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1674820] [NEW] TPM_CRB probe fails on ASUS N552V, causes system to freeze while starting

[Sjoerd van Leent]

Public bug reported:

While starting up (arranged by systemd, the problem is in the kernel),
The system attempts to perform some kind of probe, when that happens,
there is 50% chance that the system simply freezes. It always occurs
when these lines pass the screen (and are found on dmesg on a running
instance):

[8.351515] tpm_crb MSFT0101:00: can't request region for resource [mem 
0xfed40080-0xfed40fff]
[8.351550] tpm_crb: probe of MSFT0101:00 failed with error -16

I have noticed that this particular problem occurred in earlier releases
of the kernel. I have the same problem in any of the following kernels:

4.8.0-36-generic
4.8.0-39-generic
4.8.0-41-generic

It is annoying, as I have to restart the system manually with a change
of failure. Sometimes it takes over five reboots to get passed this
problem. Which indicates that somehow the problem doesn't always lock
the kernel from booting.

I hope you'll find an answer to this problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu16
ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue Mar 21 21:43:41 2017
EcryptfsInUse: Yes
ExecutablePath: /lib/systemd/systemd
InstallationDate: Installed on 2017-03-01 (19 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 002: ID 13d3:5666 IMC Networks 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. N552VW
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed 
root=UUID=68636ac9-2333-44e0-9737-9dc43321bc8a ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 
 3 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N552VW.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N552VW
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.:bvrN552VW.300:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnN552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N552VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1674820

Title:
  TPM_CRB probe fails on ASUS N552V, causes system to freeze while
  starting

Status in systemd package in Ubuntu:
  New

Bug description:
  While starting up (arranged by systemd, the problem is in the kernel),
  The system attempts to perform some kind of probe, when that happens,
  there is 50% chance that the system simply freezes. It always occurs
  when these lines pass the screen (and are found on dmesg on a running
  instance):

  [8.351515] tpm_crb MSFT0101:00: can't request region for resource [mem 
0xfed40080-0xfed40fff]
  [8.351550] tpm_crb: probe of MSFT0101:00 failed with error -16

  I have noticed that this particular problem occurred in earlier
  releases of the kernel. I have the same problem in any of the
  following kernels:

  4.8.0-36-generic
  4.8.0-39-generic
  4.8.0-41-generic

  It is annoying, as I have to restart the system manually with a change
  of failure. Sometimes it takes over five reboots to get passed this
  problem. Which indicates that somehow the problem doesn't always lock
  the kernel from booting.

  I hope you'll find an answer to this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu16
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Mar 21 21:43:41 2017
  EcryptfsInUse: Yes
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2017-03-01 (19 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/webbrowser-app/webbrowser-app-ubuntu-
zesty-2615

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1620635/+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 1434591] Re: [mako] Cannot connect to a secure, shared "ap" hotspot

[Fice]

Wi-fi hotspot works on mako with the current build of LineageOS 14.1
(the successor of CyanogenMod). Will it help to port the kernel from
LineageOS?

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

Title:
  [mako] Cannot connect to a secure, shared "ap" hotspot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 138
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-17 15:04:46
  version version: 138
  version ubuntu: 20150317.1
  version device: 20150210
  version custom: 20150317.1

  I have tried most types of security, but the spec [2] says for maximum
  compatibility, most of the options should be left blank. Blank
  settings failed on both a and bg bands.

  How to reproduce:
  1. Create a secure hotspot (I am using this [1] script)
  2. Confirm that the hotspot is active and appears secured for other devices

  What happens:
  Connecting to it fails.

  What should have happened:
  Connecting to it should not fail.

  Excerpt from syslog
  http://pastebin.ubuntu.com/10627959/

  Insecure hotspots should work using this [3] script.

  [1] http://pastebin.ubuntu.com/10683465/
  [2] https://developer.gnome.org/NetworkManager/stable/ref-settings.html
  [3] 
http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1434591/+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 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

[Launchpad Bug Tracker]

** Branch linked: lp:webbrowser-app/staging

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1620635/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Steve Beattie]

Hi, I've put test glibc packages in the ubuntu-security-proposed ppa
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages that revert the fix for
CVE-2015-5180. If someone could test that the udeb's from there don't
break your pxe install that would be great.

Quite likely what will happen is if the libc6-udeb is manually installed
after it breaks and the install is continued on successfully, another
failure will happen when the libnss-dns-udeb is pulled from the ubuntu
archive, and will likely need to also be manually installed.

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1624407] Re: Add a 'quit' message that is app-wide, as opposed to mir_event_type_close_surface

[Olivier Tilloy]

I’m not sure how a fix for bug #1674749 would address the use case in
the description: a multi-window application (such as web browser) wants
to distinguish between:

 - please close all windows one by one without retaining state for them

 - please quit the app, and save the state for all windows and tabs in
them

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

Title:
  Add a 'quit' message that is app-wide, as opposed to
  mir_event_type_close_surface

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Currently in unity8, when requesting to "Quit" a running application
  from the launcher, what happens is that qtmir goes through all its
  associated windows/surfaces, and closes them one by one. Supposedly,
  when the last window is closed, the application terminates itself (but
  this is not necessarily the case, see
  https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed-
  prop).

  This prevents application authors from doing proper cleanup before the
  app is closed. For example in Qt, the QCoreApplication::aboutToQuit()
  signal is emitted only after all windows have been closed, so the
  application doesn’t get a chance to e.g. save the list of open windows
  (real use case for multi-window browser application which saves the
  current session).

  This is similar to unity7’s implementation by the way, but I think
  it’s wrong. Surely there must be a way (maybe toolkit-specific) to
  request an app to terminate itself (and fall back to closing all
  windows if not).

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1624407/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Eric Horne]

The IP workaround doesn't work because archive.ubuntu.com is a virutal
host (ie it needs the Host: header in the HTTP request). What I did to
work around that was add this to my preseed.cfg. Adjust as needed

d-i preseed/early_command string echo "91.189.88.161 archive.ubuntu.com"
>> /etc/hosts && echo "hosts: files dns" >> /etc/nsswitch.conf

I added the dns in there just in case it happened to start working again
:)

Of course, add other IPs/names that you need. If you need a lot, not
sure. I was playing with the idea of trying to get it to install 6.9
only, but I couldn't figure out how to tell it to do that (and the
early_command is too soon, and the late_command is too late).

It'd be great if 6.10 could be rolled back for now.

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Rally]

I just tested the workaround of setting the apt mirror to be an IP
instead of a hostname and it does finish the base install but our
provisioning process is still broken. We have a late_command that gets a
script to do integrations into our environment (AD domain joining,
configuration management, certificates, etc.). All of that breaks as
well because there's numerous parts that need hostname resolution.

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

[Thomas Leonard]

I've now uploaded zeroinstall-injector 2.12-4 to Debian. That should fix
the build problem here.

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Triaged
Status in aptdaemon source package in aa-series:
  New
Status in apturl source package in aa-series:
  New
Status in dell-recovery source package in aa-series:
  New
Status in gnome-software source package in aa-series:
  New
Status in language-selector source package in aa-series:
  New
Status in lubuntu-software-center source package in aa-series:
  New
Status in mythbuntu-control-centre source package in aa-series:
  New
Status in sessioninstaller source package in aa-series:
  New
Status in software-properties source package in aa-series:
  New
Status in ubiquity source package in aa-series:
  New
Status in ubuntu-mate-meta source package in aa-series:
  New
Status in ubuntu-mate-welcome source package in aa-series:
  New
Status in update-manager source package in aa-series:
  New
Status in update-notifier source package in aa-series:
  New

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

[ChristianEhrhardt]

The suggestion was made to add a accountsservice file for it like:
echo -e "[User]\nSystemAccount=true" > 
/var/lib/AccountsService/users/libvirt-qemu

I agree this might be an option - and I might even be forced to take it at some 
point, but then I ask myself for how many extra Desktop envs/services would we 
make extra files if more are found.
Do we really want to make this a custom change in all those packages (and any 
else in the future who add system users).
- OR -
Wouldn't it make much much more sense to make accountsservice realize on non 
login shells as all other logins seem to do (e.g. sddm) and as itself did in 
the past (hidden-shells)?

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  Confirmed
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in ifmail package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Confirmed

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+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 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Igor]

** Attachment added: "xorg_after_lightdm.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033/+attachment/4841880/+files/xorg_after_lightdm.txt

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:

[Touch-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Igor]

** Attachment added: "xorg_faileed_monitor_detect.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033/+attachment/4841879/+files/xorg_faileed_monitor_detect.txt

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:

[Touch-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Igor]

Here you go:

** Attachment added: "logind.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033/+attachment/4841878/+files/logind.txt

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:

[Touch-packages] [Bug 1671424] Re: qtmir destroys windows after requesting them to close

[Daniel d'Andrada]

qtmir always destroys a window if it doesn't do so itself after being
requested to close.

Specially on desktop, requesting a window to close doesn't necessarily
mean it should destroy itself. It's a common idiom for an application to
just hide it instead, so it can be reused next time it's needed
(particularly for child windows).

Some might even stay around and just popup a dialog if there's modified
content that hasn't been saved yet.

So on desktop we should just send the close request without further
expectations. On phone though, we should keep the current behavior of
forcibly destroying the window if it doesn't comply after some time.

I wouldn't mix this bug with gtk+

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

Title:
  qtmir destroys windows after requesting them to close

Status in Canonical System Image:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Using unity7:
   * Open kate
   * write something very important in the text area
   * Press Alt+F4 because you're not very smart
   * Get dialog saying you have unsaved changes
   * You can:
 * save (which ends in a quit after saving)
 * cancel the close

  Using unity8
   * Open kate
   * write something very important in the text area
   * Press Alt+F4 because you're not very smart
   * You lost your very important text

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671424/+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 1672099] Re: DNS loop, >5, 000 queries per second for minutes at a time

[Mathieu Trudel-Lapierre]

Where does the dnsmasq package come from that is listening on 127.0.0.1?
dnsmasq should normally not be listening on that address if it was
spawned by NetworkManager.

Do you have the 'dnsmasq' package installed instead of dnsmasq-base?
dnsmasq-base can be used in a variety of scenarios as a local nameserver
and/or for lxc/libvirt and other uses.

dnsmasq ships a service file which by default might conflict with
resolved. If you need dnsmasq to run a nameserver on that system, you
would have to make sure the configuration of the whole system is such
that both would not conflict.

This can be achieved in two different ways:
 - Setting DNS= in resolved if you want to use resolved as an authoritative 
nameserver to provide dnsmasq with the information it needs (but not circle 
back to dnsmasq).
 - Setting 'no-resolv' and possibly other settings for the dnsmasq instance, 
such that it doesn't go ask systemd-resolved for nameservers, and that it does 
not update resolv.conf if it should not.

** Changed in: dnsmasq (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  DNS loop, >5,000 queries per second for minutes at a time

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading a desktop to 17.04, several times a day a DNS storm
  occurs. The same A or  record is requested over and over again.
  The storm lasts 10 to 15 minutes and can clog name resolution
  entirely, making the computer unusable for that time.

  Mar 12 08:55:12 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:13 hostname systemd-resolved[1188]: message repeated 5401 times: 
[ Processing query...]
  Mar 12 08:55:13 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:13 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:14 hostname kernel: [185434.365153] proc_thermal :00:04.0: 
Unsupported event [0x84]
  Mar 12 08:55:19 hostname systemd-resolved[1188]: message repeated 40288 
times: [ Processing query...]
  Mar 12 08:55:19 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:19 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:25 hostname systemd-resolved[1188]: message repeated 44022 
times: [ Processing query...]
  Mar 12 08:55:25 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:25 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:31 hostname systemd-resolved[1188]: message repeated 43874 
times: [ Processing query...]

  Both Firefox and Transmission originated hostnames have appeared in
  the storms, so it does not seem like an individual application is
  causing the problem.

  There are so many requests that running tcpdump on a random port (port
  29381 is used below) soon catches part of the storm. Example output
  below. Note that throughout the duration of these captures, identical
  DNS requests were being sent from pretty much every other port as
  well.

  

  = Transmission looking up mgtracker.org, got stuck on this single hostname 
for =
  = about 15 minutes (this is just the tail end of yesterday morning's storm).  
 = 
  


  08:40:24.667302 IP localhost.29381 > 127.0.0.53.domain: 60802+% [1au] ? 
mgtracker.org. (42)
  E..F..@.@..5r..5.2.y  mgtracker.org...)
  08:40:24.685708 IP 127.0.0.53.domain > localhost.29381: 60802 0/0/1 (42)
  E..Fdd@.@..5.5r..2.y  mgtracker.org...)
  08:40:33.580735 IP localhost.29381 > 127.0.0.53.domain: 53746+% [1au] A? 
mgtracker.org. (42)
  E..F.+@.@.9F...5r..5.2.y  mgtracker.org...)
  08:40:33.594830 IP 127.0.0.53.domain > localhost.29381: 53746 6/0/1 A 
92.241.171.245, A 37.19.5.139, A 77.91.229.218, A 5.79.83.194, A 5.79.83.193, A 
37.19.5.155 (138)
  E.@.@.t8...5.5r.  
mgtracker.org..X..\X..%X..M[...X...OS..X...OS..X..%.)
  08:41:30.717640 IP localhost.29381 > 127.0.0.53.domain: 63667+% [1au] ? 
mgtracker.org. (42)
  E..F\.@.@..5r..5.2.y  mgtracker.org...)
  08:41:30.733855 IP 127.0.0.53.domain > localhost.29381: 63667 0/0/1 (42)
  E..F .@.@..5.5r..2.y  mgtracker.org...)
  08:42:35.768840 IP localhost.29381 > 127.0.0.53.domain: 18342+% [1au] ? 
mgtracker.org. (42)
  E..FeH@.@..(...5r..5.2.yG...  mgtracker.org...)
  08:42:35.786098 IP 127.0.0.53.domain > 

[Touch-packages] [Bug 1671424] Re: qtmir destroys windows after requesting them to close

[Daniel d'Andrada]

** Summary changed:

- Applications fail to interrupt closing them
+ qtmir destroys windows after requesting them to close

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

Title:
  qtmir destroys windows after requesting them to close

Status in Canonical System Image:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Using unity7:
   * Open kate
   * write something very important in the text area
   * Press Alt+F4 because you're not very smart
   * Get dialog saying you have unsaved changes
   * You can:
 * save (which ends in a quit after saving)
 * cancel the close

  Using unity8
   * Open kate
   * write something very important in the text area
   * Press Alt+F4 because you're not very smart
   * You lost your very important text

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671424/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Rally]

Just hit this bug with our PXE provisioning system when trying to deploy
14.04. We were deploying without issues days ago.

The syslog from the failed install shows wget to our apt mirror location
working fine until after anna retrieves
libc6-udeb_2.19-0ubuntu6.10_amd64.deb. The subsequent retrieval of
libcryptsetu4-udeb 2:1.6.1-1ubuntu1 fails due to wget being unable to
resolve host address.

It looks like libc6-udeb_2.19-0ubuntu6.10_amd64.deb in the last 24 hours
with numerous security fixes related to hostname resolution.

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1612367] Re: [Touch] Incoming call gets silent randomly

[Cesar Herrera]

In E4.5 with OTA-15
It makes a vibration.

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1614943] Re: No ringtone on incoming calls

[Cesar Herrera]

E4.5 with OTA-15
It make a vibration.

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

Title:
  No ringtone on incoming calls

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  current build number: 405
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Regularly on incoming calls, there is no ringtone or just a click.
  Apart from that, the notification is displayed, I can answer the call
  normally.

  Phone is not muted, sound is close to the max, and if I reboot it
  works again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614943/+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 1672099] Re: DNS loop, >5, 000 queries per second for minutes at a time

[Steve Langasek]

What are the contents of /etc/resolv.conf when this happens?

What is the output of 'dpkg -l dnsmasq\*'?

What are the contents of /etc/NetworkManager/NetworkManager.conf?

Your bug report shows that this system was installed with 16.10 media
and then upgraded to 17.04.  How long ago did you upgrade?  Have you
rebooted since upgrading?

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

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

Title:
  DNS loop, >5,000 queries per second for minutes at a time

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading a desktop to 17.04, several times a day a DNS storm
  occurs. The same A or  record is requested over and over again.
  The storm lasts 10 to 15 minutes and can clog name resolution
  entirely, making the computer unusable for that time.

  Mar 12 08:55:12 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:13 hostname systemd-resolved[1188]: message repeated 5401 times: 
[ Processing query...]
  Mar 12 08:55:13 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:13 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:14 hostname kernel: [185434.365153] proc_thermal :00:04.0: 
Unsupported event [0x84]
  Mar 12 08:55:19 hostname systemd-resolved[1188]: message repeated 40288 
times: [ Processing query...]
  Mar 12 08:55:19 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:19 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:25 hostname systemd-resolved[1188]: message repeated 44022 
times: [ Processing query...]
  Mar 12 08:55:25 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:25 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:31 hostname systemd-resolved[1188]: message repeated 43874 
times: [ Processing query...]

  Both Firefox and Transmission originated hostnames have appeared in
  the storms, so it does not seem like an individual application is
  causing the problem.

  There are so many requests that running tcpdump on a random port (port
  29381 is used below) soon catches part of the storm. Example output
  below. Note that throughout the duration of these captures, identical
  DNS requests were being sent from pretty much every other port as
  well.

  

  = Transmission looking up mgtracker.org, got stuck on this single hostname 
for =
  = about 15 minutes (this is just the tail end of yesterday morning's storm).  
 = 
  


  08:40:24.667302 IP localhost.29381 > 127.0.0.53.domain: 60802+% [1au] ? 
mgtracker.org. (42)
  E..F..@.@..5r..5.2.y  mgtracker.org...)
  08:40:24.685708 IP 127.0.0.53.domain > localhost.29381: 60802 0/0/1 (42)
  E..Fdd@.@..5.5r..2.y  mgtracker.org...)
  08:40:33.580735 IP localhost.29381 > 127.0.0.53.domain: 53746+% [1au] A? 
mgtracker.org. (42)
  E..F.+@.@.9F...5r..5.2.y  mgtracker.org...)
  08:40:33.594830 IP 127.0.0.53.domain > localhost.29381: 53746 6/0/1 A 
92.241.171.245, A 37.19.5.139, A 77.91.229.218, A 5.79.83.194, A 5.79.83.193, A 
37.19.5.155 (138)
  E.@.@.t8...5.5r.  
mgtracker.org..X..\X..%X..M[...X...OS..X...OS..X..%.)
  08:41:30.717640 IP localhost.29381 > 127.0.0.53.domain: 63667+% [1au] ? 
mgtracker.org. (42)
  E..F\.@.@..5r..5.2.y  mgtracker.org...)
  08:41:30.733855 IP 127.0.0.53.domain > localhost.29381: 63667 0/0/1 (42)
  E..F .@.@..5.5r..2.y  mgtracker.org...)
  08:42:35.768840 IP localhost.29381 > 127.0.0.53.domain: 18342+% [1au] ? 
mgtracker.org. (42)
  E..FeH@.@..(...5r..5.2.yG...  mgtracker.org...)
  08:42:35.786098 IP 127.0.0.53.domain > localhost.29381: 18342 0/0/1 (42)
  E..F)N@.@..#...5.5r..2.yG...  mgtracker.org...)
  08:42:38.568885 IP localhost.29381 > 127.0.0.53.domain: 43765+% [1au] ? 
mgtracker.org. (42)
  E..F..@.@.s5r..5.2.y  mgtracker.org...)
  08:42:38.587299 IP 127.0.0.53.domain > localhost.29381: 43765 0/0/1 (42)
  E..F..@.@..5.5r..2.y  mgtracker.org...)
  08:42:41.348249 IP localhost.29381 > 127.0.0.53.domain: 39157+% [1au] A? 
mgtracker.org. (42)
  E..F)Z@.@..5r..5.2.y  mgtracker.org...)
  08:42:41.362068 IP 127.0.0.53.domain > localhost.29381: 39157 6/0/1 A 
92.241.171.245, A 

[Touch-packages] [Bug 1674776] Re: getaddrinfo() dont work correct with ipv4+ipv6 addreses aftrer upgrade libc6 in Ubuntu Precise

[Steve Beattie]

Hi, thanks for reporting your issue. I think this is actually the fix
for CVE-2015-5180 (due to an internal ABI change around T_UNSPEC). I
have uploaded a test version of eglibc with the commit to address that
issue reverted to https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/ ; is it possible to test the version there
to confirm or disprove that reverting that addresses your issue?

Thanks.

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-5180

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

Title:
  getaddrinfo() dont work correct with ipv4+ipv6 addreses aftrer upgrade
  libc6 in Ubuntu Precise

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  getaddrinfo() dont work correct with ipv4+ipv6 addreses aftrer upgrade
  libc6 in Ubuntu Precise.

  server has only ipv6 address.
  Ubuntu 12.04.5 LTS \n \l
  libc6 = 2.15-0ubuntu10.16

  host ya.ru
  YA.ru has address 93.158.134.3
  YA.ru has address 213.180.193.3
  YA.ru has address 213.180.204.3
  YA.ru has IPv6 address 2a02:6b8::3

  strace -e connect nc -zv ya.ru http
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("93.158.134.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  nc: connect to ya.ru port 80 (tcp) failed: Network is unreachable
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  nc: connect to ya.ru port 80 (tcp) failed: Network is unreachable
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("93.158.134.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)

  nc: connect to ya.ru port 80 (tcp) failed: Network is unreachable

  python -c 'import socket; print socket.getaddrinfo("ya.ru.", 0, 
socket.AF_UNSPEC, 0)[0][4]'; python -c 'import socket; print 
socket.getaddrinfo("ya.ru.", 0, socket.AF_INET6, 0)[0][4]'
  ('93.158.134.3', 0)
  ('2a02:6b8::3', 0, 0, 0)

  before update libc6=2.15-0ubuntu10.15

  strace -e connect nc -zv ya.ru http
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, 
"2a02:6b8::3", _addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("93.158.134.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, 
"2a02:6b8::3", _addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 
EINPROGRESS (Operation now in progress)

  Connection to ya.ru 80 port [tcp/http] succeeded!

  python -c 'import socket; print socket.getaddrinfo("ya.ru.", 0, 
socket.AF_UNSPEC, 0)[0][4]'; python -c 'import socket; print 
socket.getaddrinfo("ya.ru.", 0, socket.AF_INET6, 0)[0][4]'
  ('2a02:6b8::3', 0, 0, 0)
  ('2a02:6b8::3', 0, 0, 0)

  I think problem with patch: CVE-2016-3706: getaddrinfo: stack overflow in 
hostent conversion [BZ #20010]
  
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=blobdiff;f=sysdeps/posix/getaddrinfo.c;h=df6ce8b13e3897f3ed47877b029da39abafe9f25;hp=d2283bcd4ad4fe7e41cf9c6ee74ec8c63ab32e34;hb=762aafec34478bcef01a16acf1959732ab8bb2b6;hpb=e97fb84811238c627f93e5e703a11eb841601947;ds=sidebyside

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

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1672099] Re: DNS loop, >5, 000 queries per second for minutes at a time

[Robie Basak]

I asked on IRC:

18:15  rbasak: AFAIK dnsmasq is dropped out of the default DNS stack 
again in 17.04, so that shouldn't be happening?
18:15  certainly, resolved+networkd+resolvconf+dnsmasq might have 
bugs like this
18:15  but that's not the config we're supposed to be shipping

So I think dnsmasq isn't supposed to be the default on 17.04. Since this
is a non-default configuration, I'll set Importance to Low.

** Changed in: dnsmasq (Ubuntu)
   Importance: Undecided => Low

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

Title:
  DNS loop, >5,000 queries per second for minutes at a time

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Since upgrading a desktop to 17.04, several times a day a DNS storm
  occurs. The same A or  record is requested over and over again.
  The storm lasts 10 to 15 minutes and can clog name resolution
  entirely, making the computer unusable for that time.

  Mar 12 08:55:12 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:13 hostname systemd-resolved[1188]: message repeated 5401 times: 
[ Processing query...]
  Mar 12 08:55:13 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:13 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:14 hostname kernel: [185434.365153] proc_thermal :00:04.0: 
Unsupported event [0x84]
  Mar 12 08:55:19 hostname systemd-resolved[1188]: message repeated 40288 
times: [ Processing query...]
  Mar 12 08:55:19 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:19 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:25 hostname systemd-resolved[1188]: message repeated 44022 
times: [ Processing query...]
  Mar 12 08:55:25 hostname dnsmasq[1227]: Maximum number of concurrent DNS 
queries reached (max: 150)
  Mar 12 08:55:25 hostname systemd-resolved[1188]: Processing query...
  Mar 12 08:55:31 hostname systemd-resolved[1188]: message repeated 43874 
times: [ Processing query...]

  Both Firefox and Transmission originated hostnames have appeared in
  the storms, so it does not seem like an individual application is
  causing the problem.

  There are so many requests that running tcpdump on a random port (port
  29381 is used below) soon catches part of the storm. Example output
  below. Note that throughout the duration of these captures, identical
  DNS requests were being sent from pretty much every other port as
  well.

  

  = Transmission looking up mgtracker.org, got stuck on this single hostname 
for =
  = about 15 minutes (this is just the tail end of yesterday morning's storm).  
 = 
  


  08:40:24.667302 IP localhost.29381 > 127.0.0.53.domain: 60802+% [1au] ? 
mgtracker.org. (42)
  E..F..@.@..5r..5.2.y  mgtracker.org...)
  08:40:24.685708 IP 127.0.0.53.domain > localhost.29381: 60802 0/0/1 (42)
  E..Fdd@.@..5.5r..2.y  mgtracker.org...)
  08:40:33.580735 IP localhost.29381 > 127.0.0.53.domain: 53746+% [1au] A? 
mgtracker.org. (42)
  E..F.+@.@.9F...5r..5.2.y  mgtracker.org...)
  08:40:33.594830 IP 127.0.0.53.domain > localhost.29381: 53746 6/0/1 A 
92.241.171.245, A 37.19.5.139, A 77.91.229.218, A 5.79.83.194, A 5.79.83.193, A 
37.19.5.155 (138)
  E.@.@.t8...5.5r.  
mgtracker.org..X..\X..%X..M[...X...OS..X...OS..X..%.)
  08:41:30.717640 IP localhost.29381 > 127.0.0.53.domain: 63667+% [1au] ? 
mgtracker.org. (42)
  E..F\.@.@..5r..5.2.y  mgtracker.org...)
  08:41:30.733855 IP 127.0.0.53.domain > localhost.29381: 63667 0/0/1 (42)
  E..F .@.@..5.5r..2.y  mgtracker.org...)
  08:42:35.768840 IP localhost.29381 > 127.0.0.53.domain: 18342+% [1au] ? 
mgtracker.org. (42)
  E..FeH@.@..(...5r..5.2.yG...  mgtracker.org...)
  08:42:35.786098 IP 127.0.0.53.domain > localhost.29381: 18342 0/0/1 (42)
  E..F)N@.@..#...5.5r..2.yG...  mgtracker.org...)
  08:42:38.568885 IP localhost.29381 > 127.0.0.53.domain: 43765+% [1au] ? 
mgtracker.org. (42)
  E..F..@.@.s5r..5.2.y  mgtracker.org...)
  08:42:38.587299 IP 127.0.0.53.domain > localhost.29381: 43765 0/0/1 (42)
  E..F..@.@..5.5r..2.y  mgtracker.org...)
  08:42:41.348249 IP localhost.29381 > 127.0.0.53.domain: 39157+% [1au] A? 
mgtracker.org. (42)
  E..F)Z@.@..5r..5.2.y  mgtracker.org...)
  08:42:41.362068 IP 

[Touch-packages] [Bug 1672337] Re: [unity8] can't restore an app if you minimize it while a child window, menu or context menu is opened

[Lukáš Tinkl]

** Also affects: qtmir (Ubuntu)
   Importance: Undecided
   Status: 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/1672337

Title:
  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

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

Bug description:
  ubuntu 17.04 unity8

  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

  open whatever app, kate without Xmir, right click to open a context
  menu or just open a child window. minize the app then try to restore
  it by clicking on the icon on the launcher

  doesn't seem to work here

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672337/+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 1674776] Re: getaddrinfo() dont work correct with ipv4+ipv6 addreses aftrer upgrade libc6 in Ubuntu Precise

[Launchpad Bug Tracker]

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

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

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

Title:
  getaddrinfo() dont work correct with ipv4+ipv6 addreses aftrer upgrade
  libc6 in Ubuntu Precise

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  getaddrinfo() dont work correct with ipv4+ipv6 addreses aftrer upgrade
  libc6 in Ubuntu Precise.

  server has only ipv6 address.
  Ubuntu 12.04.5 LTS \n \l
  libc6 = 2.15-0ubuntu10.16

  host ya.ru
  YA.ru has address 93.158.134.3
  YA.ru has address 213.180.193.3
  YA.ru has address 213.180.204.3
  YA.ru has IPv6 address 2a02:6b8::3

  strace -e connect nc -zv ya.ru http
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("93.158.134.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  nc: connect to ya.ru port 80 (tcp) failed: Network is unreachable
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  nc: connect to ya.ru port 80 (tcp) failed: Network is unreachable
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("93.158.134.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)

  nc: connect to ya.ru port 80 (tcp) failed: Network is unreachable

  python -c 'import socket; print socket.getaddrinfo("ya.ru.", 0, 
socket.AF_UNSPEC, 0)[0][4]'; python -c 'import socket; print 
socket.getaddrinfo("ya.ru.", 0, socket.AF_INET6, 0)[0][4]'
  ('93.158.134.3', 0)
  ('2a02:6b8::3', 0, 0, 0)

  before update libc6=2.15-0ubuntu10.15

  strace -e connect nc -zv ya.ru http
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, 
"2a02:6b8::3", _addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("93.158.134.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, 
"2a02:6b8::3", _addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 
EINPROGRESS (Operation now in progress)

  Connection to ya.ru 80 port [tcp/http] succeeded!

  python -c 'import socket; print socket.getaddrinfo("ya.ru.", 0, 
socket.AF_UNSPEC, 0)[0][4]'; python -c 'import socket; print 
socket.getaddrinfo("ya.ru.", 0, socket.AF_INET6, 0)[0][4]'
  ('2a02:6b8::3', 0, 0, 0)
  ('2a02:6b8::3', 0, 0, 0)

  I think problem with patch: CVE-2016-3706: getaddrinfo: stack overflow in 
hostent conversion [BZ #20010]
  
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=blobdiff;f=sysdeps/posix/getaddrinfo.c;h=df6ce8b13e3897f3ed47877b029da39abafe9f25;hp=d2283bcd4ad4fe7e41cf9c6ee74ec8c63ab32e34;hb=762aafec34478bcef01a16acf1959732ab8bb2b6;hpb=e97fb84811238c627f93e5e703a11eb841601947;ds=sidebyside

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674776/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

[Brandon Schaefer]

Bug is in protobuf leaking symbols, so not a mir/sdl2 bug.

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

** Changed in: mir/0.26
 Assignee: Brandon Schaefer (brandontschaefer) => (unassigned)

** Changed in: mir
   Status: In Progress => Invalid

** Changed in: mir/0.26
   Status: Triaged => Invalid

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

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in Mir 0.26 series:
  Invalid
Status in libsdl2 package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1674776] [NEW] getaddrinfo() dont work correct with ipv4+ipv6 addreses aftrer upgrade libc6 in Ubuntu Precise

[helodron]

Public bug reported:

getaddrinfo() dont work correct with ipv4+ipv6 addreses aftrer upgrade
libc6 in Ubuntu Precise.

server has only ipv6 address.
Ubuntu 12.04.5 LTS \n \l
libc6 = 2.15-0ubuntu10.16

host ya.ru
YA.ru has address 93.158.134.3
YA.ru has address 213.180.193.3
YA.ru has address 213.180.204.3
YA.ru has IPv6 address 2a02:6b8::3

strace -e connect nc -zv ya.ru http
connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("93.158.134.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
nc: connect to ya.ru port 80 (tcp) failed: Network is unreachable
connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
nc: connect to ya.ru port 80 (tcp) failed: Network is unreachable
connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("93.158.134.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)

nc: connect to ya.ru port 80 (tcp) failed: Network is unreachable

python -c 'import socket; print socket.getaddrinfo("ya.ru.", 0, 
socket.AF_UNSPEC, 0)[0][4]'; python -c 'import socket; print 
socket.getaddrinfo("ya.ru.", 0, socket.AF_INET6, 0)[0][4]'
('93.158.134.3', 0)
('2a02:6b8::3', 0, 0, 0)

before update libc6=2.15-0ubuntu10.15

strace -e connect nc -zv ya.ru http
connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
connect(3, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, 
"2a02:6b8::3", _addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("93.158.134.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
connect(3, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, 
"2a02:6b8::3", _addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 
EINPROGRESS (Operation now in progress)

Connection to ya.ru 80 port [tcp/http] succeeded!

python -c 'import socket; print socket.getaddrinfo("ya.ru.", 0, 
socket.AF_UNSPEC, 0)[0][4]'; python -c 'import socket; print 
socket.getaddrinfo("ya.ru.", 0, socket.AF_INET6, 0)[0][4]'
('2a02:6b8::3', 0, 0, 0)
('2a02:6b8::3', 0, 0, 0)

I think problem with patch: CVE-2016-3706: getaddrinfo: stack overflow in 
hostent conversion [BZ #20010]
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=blobdiff;f=sysdeps/posix/getaddrinfo.c;h=df6ce8b13e3897f3ed47877b029da39abafe9f25;hp=d2283bcd4ad4fe7e41cf9c6ee74ec8c63ab32e34;hb=762aafec34478bcef01a16acf1959732ab8bb2b6;hpb=e97fb84811238c627f93e5e703a11eb841601947;ds=sidebyside

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

** Description changed:

  getaddrinfo() dont work correct with ipv4+ipv6 addreses aftrer upgrade
  libc6 in Ubuntu Precise.
  
  server has only ipv6 address.
  Ubuntu 12.04.5 LTS \n \l
  libc6 = 2.15-0ubuntu10.16
  
  host ya.ru
  YA.ru has address 93.158.134.3
  YA.ru has address 213.180.193.3
  YA.ru has address 213.180.204.3
  YA.ru has IPv6 address 2a02:6b8::3
  
  strace -e connect nc -zv ya.ru http
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.193.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) 
= 0
  connect(3, {sa_family=AF_INET, sin_port=htons(80), 
sin_addr=inet_addr("213.180.204.3")}, 16) = -1 ENETUNREACH (Network is 
unreachable)
  connect(3, {sa_family=AF_UNSPEC, 

[Touch-packages] [Bug 1672337] Re: [unity8] can't restore an app if you minimize it while a child window, menu or context menu is opened

[Lukáš Tinkl]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

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

Title:
  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

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

Bug description:
  ubuntu 17.04 unity8

  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

  open whatever app, kate without Xmir, right click to open a context
  menu or just open a child window. minize the app then try to restore
  it by clicking on the icon on the launcher

  doesn't seem to work here

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672337/+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 1674774] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1663995, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1674774/+attachment/4841836/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1674774/+attachment/4841842/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1674774/+attachment/4841844/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1674774/+attachment/4841845/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1674774/+attachment/4841846/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1674774/+attachment/4841847/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1663995
   systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

** Tags removed: need-amd64-retrace

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

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-19
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-9-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Mar 20 23:48:08 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2015-03-25 (727 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55d4a8fdbec0, argc=1, argv=0x7ffc7b0f5878, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc7b0f5868) at ../csu/libc-start.c:291
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-yakkety
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu2:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-yakkety
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1674774/+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 1674774] [NEW] systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

[Till Kamppeter]

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

Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: udev 232-19
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-9-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CustomUdevRuleFiles: 80-net-setup-link.rules
Date: Mon Mar 20 23:48:08 2017
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2015-03-25 (727 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcCmdline: /lib/systemd/systemd-udevd
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x55d4a8fdbec0, argc=1, argv=0x7ffc7b0f5878, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc7b0f5868) at ../csu/libc-start.c:291
Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu2
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-yakkety
dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu2:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-yakkety
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-crash zesty

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

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-19
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-9-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Mar 20 23:48:08 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2015-03-25 (727 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55d4a8fdbec0, argc=1, argv=0x7ffc7b0f5878, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc7b0f5868) at ../csu/libc-start.c:291
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-yakkety
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu2:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-yakkety
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1674774/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

[Michael Terry]

@Alexandros, I uploaded this to zesty, thanks!  Since we're in freeze
for zesty (and releasing a beta on Thursday), it may not land in short
order, but I'll keep an eye on it.

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

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1624407] Re: Add a 'quit' message that is app-wide, as opposed to mir_event_type_close_surface

[Daniel d'Andrada]

Maybe a fix for bug 1674749 is what you want.

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

Title:
  Add a 'quit' message that is app-wide, as opposed to
  mir_event_type_close_surface

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Currently in unity8, when requesting to "Quit" a running application
  from the launcher, what happens is that qtmir goes through all its
  associated windows/surfaces, and closes them one by one. Supposedly,
  when the last window is closed, the application terminates itself (but
  this is not necessarily the case, see
  https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed-
  prop).

  This prevents application authors from doing proper cleanup before the
  app is closed. For example in Qt, the QCoreApplication::aboutToQuit()
  signal is emitted only after all windows have been closed, so the
  application doesn’t get a chance to e.g. save the list of open windows
  (real use case for multi-window browser application which saves the
  current session).

  This is similar to unity7’s implementation by the way, but I think
  it’s wrong. Surely there must be a way (maybe toolkit-specific) to
  request an app to terminate itself (and fall back to closing all
  windows if not).

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1624407/+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 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

[Andrew Hayzen]

FWIW, this bug was stopping the webbrowser from being able to export a
PDF to the printing 'app'.

This was due to content-hub using libapparmor to check if the app was
able to read the path, and the webbrowser-app using an apparmor manifest
which generated a rule with owner in it.

It would be good to get this fixed to prevent other apps using content-
hub failing to import/export.

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1620635/+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 1672491] Re: New NetworkManager breaks VPN DNS.

[Nicolás Abel Carbone]

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

** This bug has been marked a duplicate of bug 1671606
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6-0ubuntu0.16.04.1

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

Title:
  New NetworkManager breaks VPN DNS.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Alright, this is going to be a frustrating bug for everyone involved I
  expect, but here goes.

  On Ubuntu 16.04, using a non-released VPN client (making this _much_
  harder for anyone to reproduce), upgrading the network-manager
  packages from 1.2.2-0ubuntu0.16.04.3 to 1.2.6-0ubuntu0.16.04.1 quite
  handily broke DNS over the VPN.

  And it broke it really oddly.

  dnsmasq binds to socket 12 for the new interface, just fine.

  strace shows that it does the sendto for the DNS request, and that the
  poll calls are working, just fine.

  tcpdump shows the response messages, they are coming back from the
  correct host and port, going to my IP and the port that dnsmasq is
  sending from.

  There are no iptables rules involved, nothing is set to deny.

  dnsmasq is never getting the response packet.

  The request thus times out.

  Doing a host or dig directly to the DNS server works just fine.

  And this is completely reproducible, and goes away the moment I
  downgrade back to 1.2.2-0ubuntu0.16.04.3.

  Was there some change to how network-manager handles VPN
  interfaces/tap0 in the new version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1672491/+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 376982] Re: gpg hangs in mlock, cannot be killed

[Launchpad Bug Tracker]

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

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

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

Title:
  gpg hangs in mlock, cannot be killed

Status in gnupg package in Ubuntu:
  Confirmed

Bug description:
  I've noticed (by running "htop") a number of processes whose state is "D" -- 
uninterruptible sleep.  This is unusual.  A few of them are gpg.
  gnupg version 1.4.9-3ubuntu1

  I've also noticed that whenever I run gpg, it hangs, and I cannot kill
  it: not by typing Control C, nor Control Z; nor by switching to a
  different terminal, becoming root, and trying "kill -9" on the
  process' PID.

  I can no longer do any encryption or decryption.  This rather sucks
  :-|

  I ran "strace -f -o yow gpg < some-file" and captured the output; the
  last lines are

  10076 fstat64(3, {st_mode=S_IFREG|0644, st_size=256316, ...}) = 0
  10076 mmap2(NULL, 256316, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7c9b000
  10076 close(3)  = 0
  10076 mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0xb7c93000
  10076 getuid32()= 1000
  10076 mlock(0xb7c93000, 32768

  So it's hanging in "mlock".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/376982/+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 1674746] Re: url-dispacher!

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1668212, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1674746/+attachment/4841756/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1674746/+attachment/4841757/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 1668212

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  url-dispacher!

Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: url-dispatcher 0.1+17.04.20170314-0ubuntu1
  Uname: Linux 4.10.4-041004-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Tue Mar 21 19:05:49 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/url-dispatcher/url-dispatcher
  InstallationDate: Installed on 2017-03-14 (7 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/url-dispatcher/url-dispatcher
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: url-dispatcher
  URLDispatcherDB:
   scope,"",/usr/share/url-dispatcher/urls/unity8-dash.url-dispatcher
   
settings,"",/usr/share/url-dispatcher/urls/ubuntu-system-settings.url-dispatcher
   http,"",/usr/share/url-dispatcher/urls/webbrowser-app.url-dispatcher
   https,"",/usr/share/url-dispatcher/urls/webbrowser-app.url-dispatcher
   content,"",/usr/share/url-dispatcher/urls/content-hub-send.url-dispatcher
  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/url-dispatcher/+bug/1674746/+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 1674680] Re: Deprecated rfcomm.conf still mentioned

[Ubuntu Foundations Team Bug Bot]

The attachment "zesty_bluez_5.43-0ubuntu2.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Deprecated rfcomm.conf still mentioned

Status in bluez package in Ubuntu:
  New

Bug description:
  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Éric Paul]

Thanks to Eric for suggesting the workaround.

It works if there's no virtual hosting on the mirror. As I manage a
local mirror, I changed my apache configuration and I can install with
my PXE.

Eric.

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1671658] Re: Software & Updates has duplicate entries when installed in Ubuntu Software

[Jeremy Bicha]

** Tags added: appstream

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

Title:
  Software & Updates has duplicate entries when installed in Ubuntu
  Software

Status in software-properties package in Ubuntu:
  New

Bug description:
  Ubuntu Software lists two duplicate entries for Software & Updates
  when installed.

  I believe this is because software-properties ships two desktop files:
  software-properties-gnome.desktop and software-properties-gtk.desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1671658/+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 1674679] Re: lxc autopkgtest fails if http_proxy not set

[Stéphane Graber]

Packaging branches updated, will be in the next round of bugfix
releases.

** Changed in: lxc (Ubuntu)
   Status: New => Fix Committed

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

Title:
  lxc autopkgtest fails if http_proxy not set

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  debian/tests/exercise fails if http_proxy is not set, e.g.:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/l/lxc/20170320_194539_28897@/log.gz

  Since the script uses 'set -e' the expression 'if [ -n "${http_proxy}"
  ]' causes the script to terminate when http_proxy isn't set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1674679/+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 1674296] Re: In Terminal app, when settings window is already opened clicking on the settings icon does not raise it

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-terminal-app (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/1674296

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  Confirmed

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1674296/+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 1673350] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From mauri...@br.ibm.com 2017-03-21 11:39 EDT---
> AFAICT there wouldn't really be any change required to initramfs-tools --
> everything is contained in multipath-tools-boot.

Right. That seems to have been set for screening/triaging purposes
during bug mirroring / initially reporting the bug on LP, but this is
definitely only multipath-tools and linux (plus some d-i updates, I
guess, for the version number of the linux kernel).

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in multipath-tools source package in Xenial:
  New
Status in hw-detect source package in Yakkety:
  New
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  New
Status in multipath-tools source package in Yakkety:
  New

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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 1673817] Re: update-secure-boot-policy behaving badly with unattended-upgrades

[Brian Murray]

** Tags added: rls-z-incoming

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

Title:
  update-secure-boot-policy behaving badly with unattended-upgrades

Status in shim-signed package in Ubuntu:
  Incomplete
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Currently, unattended-upgrades will automatically install all updates
  for those running development releases of Ubuntu (LP: #1649709)

  Today, my computer was acting very sluggish. Looking at my process
  list, I saw/ usr/sbin/update-secureboot-policy was using a log of CPU.

  I killed the process. I have a /var/crash/shim-signed.0.crash but
  since it's 750 MB, I didn't bother submitting it or looking at it
  more. Maybe it crashed because I killed the process. Also, I see that
  unattended-upgrades-dpkg.log is 722 MB.

  Today's update included both VirtualBox and the linux kernel.

  I am attaching an excerpt of /var/log/unattended-upgrades/unattended-
  upgrades-dpkg.log

  This message was repeated a very large number of times (but I only
  included it once in the attachment:

  "Invalid password

  The Secure Boot key you've entered is not valid. The password used must be 
  between 8 and 16 characters."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: shim-signed 1.23+0.9+1474479173.6c180c6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 17 11:15:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-23 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  SourcePackage: shim-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1673817/+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 1674296] Re: In Terminal app, when settings window is already opened clicking on the settings icon does not raise it

[Gerry Boland]

Ok, no need for separate bug, the updated description shows me what you
want.

** Package changed: qtmir (Ubuntu) => qtubuntu (Ubuntu)

** 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/1674296

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  New

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1674296/+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 1674296] Re: In Terminal app, when settings window is already opened clicking on the settings icon does not raise it

[Florian Boucault]

Test app is a QML app that reproduces the behaviour. Click on the
content of the root window and observe that the child window is not
raised.

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

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  New

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1674296/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Eric Horne]

I believe changing the preseed.cfg file to use an IP address for the
archive instead of the domain name will work around this; it's not a
good long term solution since it messes up ubuntu's dns load balancing,
but if you need to perform an install this might work. I'm in the
process of verifying this.

d-i mirror/http/hostname string archive.ubuntu.com

to

d-i mirror/http/hostname string (looked up ip address)

and... thank you all for quickly investigating the issue! :)

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters

[Łukasz Zemczak]

Hello Mitsuya! Thank you for preparing the debdiff. I checked upstream
and the bug in mention was indeed fixed there - but it seems that their
fix for mkutable (at upstream) is different. I would prefer if Ubuntu
didn't diverge from upstream if possible. Is it because the way it's
done in 487 is not applicable on top of 481? Or what is the reason for
the differences?

Thanks!

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

Title:
  missing or duplicate lines caused by a wrapped line with wide
  characters

Status in less package in Ubuntu:
  Confirmed

Bug description:
  When you scroll down text with "j" key and encounter a wrapped line
  with wide characters (such as UTF8-encoded Japanese characters),
  "less" seems to show the whole wrapped line at a single "j" key,
  causing the view scroll down by 2 lines at once. Strangely, if you
  type "k" to scroll up, it does that by only 1 line. As a result, there
  is a missing line that should have been shown.

  Even stranger stuff (i.e., duplicate lines) happens when you type "j"
  and "k" alternately when a wrapped line with wide characters is at the
  bottom of the view.

  
  # Steps to reproduce

  1. Open xterm.
  2. Set the geometory of xterm to 71x22.
  3. Open the attached lesstest.long_jap.txt with less (maybe you need
 environment variable LANG=ja_JP.UTF-8)
  4. Type "j", then you will see "003" at the top, and a long wrapped
 line with Japanese characters at the bottom.
  5. Type "k", then you will see "001" and "003" at the top. "002" is
 missing.

  # Expected behavior

  In step 4, only the first part of the wrapped line should be shown.

  In step 5, all "001", "002" and "003" should be shown.

  
  # Test Environment

  - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04)
  - less: 481-2.1
  - xterm: 322-1ubuntu1
  - Japanese environment (LANG=ja_JP.UTF-8)

  
  # Note

  - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1)
  - lv (4.51-2.3build1) doesn't have such problem.
  - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't
exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package

[Brian Murray]

I don't think many people are still upgrading from Xenial to Yakkety but
this'll likely be important to fix for people upgrading from 16.04 to
18.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/1673625

Title:
  10-globally-managed-devices.conf contained in wrong package

Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is
  installed from network-manager but without nplan it has no benefit,
  and breaks networking until you override it.  Since the config is
  there to change how NetworkManager behaves in the presence of nplan,
  the configuration file itself should actually be contained in the
  nplan package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1674296] Re: In Terminal app, when settings window is already opened clicking on the settings icon does not raise it

[Michał Sawicz]

** Package changed: unity8 (Ubuntu) => qtmir (Ubuntu)

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

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  New

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1674296/+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 1674296] Re: When preference window is already opened clicking on the settings icon does not raise it

[Gerry Boland]

Could you log separate bug about QWindow::raise/QWindow::requestActivate
against qtubuntu. Mir has an api for that, but we've not implemented it.

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

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  New

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1674296/+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 1674296] Re: When preference window is already opened clicking on the settings icon does not raise it

[Florian Boucault]

** Description changed:

  Steps:
  
+ 0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon
  
  Expected:
  Settings window is raised and focused

** Summary changed:

- When preference window is already opened clicking on the settings icon does 
not raise it
+ In Terminal app, when settings window is already opened clicking on the 
settings icon does not raise it

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

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  New

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

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