[Touch-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]

[Bug Watch Updater]

** Changed in: gtk
   Status: Unknown => Confirmed

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

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_style_provider_private_get_settings(provider=0x0)
  [gtkstyleproviderprivate.c:123]

Status in Apport:
  New
Status in GTK+:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347

  ---

  Crash displayed after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 22:13:24 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi
   PC (0x7f3a0219cb89) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1552577/+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 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]

[Daniel van Vugt]

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

** Bug watch added: GNOME Bug Tracker #791647
   https://bugzilla.gnome.org/show_bug.cgi?id=791647

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=791647
   Importance: Unknown
   Status: Unknown

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_style_provider_private_get_settings(provider=0x0)
  [gtkstyleproviderprivate.c:123]

Status in Apport:
  New
Status in GTK+:
  Unknown
Status in apport package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347

  ---

  Crash displayed after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 22:13:24 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi
   PC (0x7f3a0219cb89) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1552577/+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 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]

[Daniel van Vugt]

** Summary changed:

- apport-gtk crashed with SIGSEGV in 
_gtk_style_provider_private_get_settings(provider=0x0)
+ apport-gtk crashed with SIGSEGV in 
_gtk_style_provider_private_get_settings(provider=0x0) 
[gtkstyleproviderprivate.c:123]

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_style_provider_private_get_settings(provider=0x0)
  [gtkstyleproviderprivate.c:123]

Status in Apport:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347

  ---

  Crash displayed after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 22:13:24 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi
   PC (0x7f3a0219cb89) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1552577/+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 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0)

[Daniel van Vugt]

This looks like the same issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1395968

** Bug watch added: Red Hat Bugzilla #1395968
   https://bugzilla.redhat.com/show_bug.cgi?id=1395968

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_style_provider_private_get_settings(provider=0x0)

Status in Apport:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347

  ---

  Crash displayed after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 22:13:24 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi
   PC (0x7f3a0219cb89) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1552577/+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 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

[Launchpad Bug Tracker]

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

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

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Confirmed
Status in apport source package in Zesty:
  Confirmed
Status in apport source package in Artful:
  Confirmed
Status in apport source package in Bionic:
  Fix Released

Bug description:
  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1733366/+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 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

[Launchpad Bug Tracker]

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

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

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Confirmed
Status in apport source package in Zesty:
  Confirmed
Status in apport source package in Artful:
  Confirmed
Status in apport source package in Bionic:
  Fix Released

Bug description:
  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1733366/+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 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Yuan-Chen Cheng]

@Lukasz, if it's hard for you to pick one, can you just proceed with
zesty SRU ?

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+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 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

[Launchpad Bug Tracker]

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

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

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Confirmed
Status in apport source package in Zesty:
  Confirmed
Status in apport source package in Artful:
  Confirmed
Status in apport source package in Bionic:
  Fix Released

Bug description:
  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1733366/+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 1738343] [NEW] /usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@367:is_container_pid

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.8-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b7382bd4275be67d7f2b0429c3bd6c949b375f47 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic kylin-17.10 xenial zesty

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

Title:
  
/usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@367:is_container_pid

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.8-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b7382bd4275be67d7f2b0429c3bd6c949b375f47 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738343/+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 1738344] Re: /usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@308:is_container_pid

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1733366
   apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No 
such file or directory: '/proc/11102/ns/pid'

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

Title:
  
/usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@308:is_container_pid

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.14.1-0ubuntu3.27, the problem page at 
https://errors.ubuntu.com/problem/385d2e8ecf335dc2cdd7216506bbf2b6e6b8751c 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738344/+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 1738343] Re: /usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@367:is_container_pid

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1733366
   apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No 
such file or directory: '/proc/11102/ns/pid'

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

Title:
  
/usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@367:is_container_pid

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.8-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b7382bd4275be67d7f2b0429c3bd6c949b375f47 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738343/+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 1738342] [NEW] /usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@424:is_same_ns

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.8-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/afc555abf6aa0fc0746b26827cb71081655736f0 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic kylin-17.10 xenial zesty

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

Title:
  
/usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@424:is_same_ns

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.8-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/afc555abf6aa0fc0746b26827cb71081655736f0 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738342/+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 1738342] Re: /usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@424:is_same_ns

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1733366
   apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No 
such file or directory: '/proc/11102/ns/pid'

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

Title:
  
/usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@424:is_same_ns

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.8-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/afc555abf6aa0fc0746b26827cb71081655736f0 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738342/+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 1738344] [NEW] /usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@308:is_container_pid

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.14.1-0ubuntu3.27, the problem page at 
https://errors.ubuntu.com/problem/385d2e8ecf335dc2cdd7216506bbf2b6e6b8751c 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: trusty xenial

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

Title:
  
/usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@308:is_container_pid

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.14.1-0ubuntu3.27, the problem page at 
https://errors.ubuntu.com/problem/385d2e8ecf335dc2cdd7216506bbf2b6e6b8751c 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738344/+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 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  New

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] 

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[NoOne]

Sorry, I can't test it...

I enabled artful-proposed.

I created a file in /etc/apt/preferences.d/proposed-updates with this
content:

Package: libgweather
Pin: release a=artful-proposed
Pin-Priority: 400

But when I test it with : sudo apt-get upgrade -s

I get lots of packages to upgrade.

I guess I'm doing something wrong... Not used to do that.

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1738205] Re: no sound while playing audio/video

[Arsath]

** Summary changed:

- no sound while playing audio
+ no sound while playing audio/video

** Description changed:

- Not able to hear audio through headset on ubuntu 14.04. Volume icon is
- not visible..
+ Not able to hear audio through headset on ubuntu 14.04. Also, volume
+ icon is not visible..
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Dec 14 18:47:12 2017
  InstallationDate: Installed on 2016-02-04 (679 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton M6610
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton Series
  dmi.sys.vendor: Acer

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

Title:
  no sound while playing audio/video

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not able to hear audio through headset on ubuntu 14.04. Also, volume
  icon is not visible..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Dec 14 18:47:12 2017
  InstallationDate: Installed on 2016-02-04 (679 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton M6610
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton Series
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738205/+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 1738205] Re: no sound while playing audio

[Arsath]

I could not find any files in var/crash/ folder.

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

Title:
  no sound while playing audio

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not able to hear audio through headset on ubuntu 14.04. Volume icon is
  not visible..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Dec 14 18:47:12 2017
  InstallationDate: Installed on 2016-02-04 (679 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton M6610
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton Series
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738205/+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 1738205] Re: no sound while playing audio

[Daniel van Vugt]

It appears you have no sound or volume icon because your 'pulseaudio'
process is missing (probably crashed).

Please have a look in /var/crash for any relevant files. If you find one
upload it using this command:

  ubuntu-bug /var/crash/YOURFILE.crash

and tell us the ID of the new bug that creates.

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

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

Title:
  no sound while playing audio

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not able to hear audio through headset on ubuntu 14.04. Volume icon is
  not visible..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Dec 14 18:47:12 2017
  InstallationDate: Installed on 2016-02-04 (679 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton M6610
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton Series
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738205/+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 1726320] Re: suggested and destructive colours are too bright

[Daniel van Vugt]

I agree, leaving the green would be fine IMHO. But let's keep this bug
open because I'm sure those of us who don't mind the green too much also
would not mind it changing, depending on what it changed to.

** Changed in: ubuntu-themes
   Importance: Undecided => Low

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

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

Title:
  suggested and destructive colours are too bright

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  IMO, so feel free to close this if you disagree, the suggested and
  destructive (green and red) colours that are used in GTK UIs are too
  bright.

  Attached is a screenshot from Marco that shows them both. (It's a
  faked up example, usually you don't see them together like that.)

  They draw the eye too much I think. It should be a hint for where you
  might or might not want to click, but not something that grabs your
  attention.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1726320/+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 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

[Daniel van Vugt]

Yes the bug title changed but the problem the original reporter was
describing in the bug description did not. The original description and
the current description both say:

  "On 15:10 after the bluetooth service has been stopped and restarted
it is not possible to scan or connect to devices:"

Thus the original bug title was just a mistake, which has been
corrected.

It is inappropriate to commandeer and change the direction of a bug from
the intent of the original reporter because at any stage they do have
the right to change it back, or to proclaim that some eventual fix does
or does not resolve the original problem.

There are only 28 people, not 128, really subscribed to this bug. I'm
sure one of you could just follow this link and open a new bug:
https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug

It is actually pretty common for people to say "hey that bug you closed
doesn't fix the problem for me". However the bug should still remain
closed unless those people happen to be the original reporter. So in
that case, yes, if TJ was willing to change the description of this bug
to be about the problem you describe rather than the original problem
s/he reported then that's possibly OK.

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

Title:
  15:10 and 16.04: bluetoothd "Failed to start discovery:
  org.bluez.Error.NotReady" after bluetoothd restarted

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl restart bluetooth

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Daniel van Vugt]

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

Jamie, it sounds like you should subscribe to bug 1710637 and request a
fix for that be released for 16.04 (it's presently fixed only in 17.10
and later).

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on

[Treviño]

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  Copy-paste and text selection doesn't work when caps-lock is on

Status in nux package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps 
Lock is on

  [Test case]
  0) Set Caps-Lock on in your keyboard
  1) Open dash, and write something
  2) Ctrl+A should select all the text, Ctrl+C should copy,
     Ctrl+V should paste and Ctrl+X should cut

  Currently they don't work unless caps-lock is turned off

  [Possible regression]
  Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling 
won't work anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 1735960] Re: Merge avahi 0.7 with Debian

[Jeremy Bicha]

** Tags added: ftbfs

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

Title:
  Merge avahi 0.7 with Debian

Status in avahi package in Ubuntu:
  Triaged

Bug description:
  avahi 0.7 is in Debian.

  This merge is blocked by this FTBFS issue:
  https://bugs.debian.org/878911
  https://bugs.debian.org/880036

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1735960/+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 1738155] Re: Calling reboot or poweroff on a node-red snap is fail

[zhangyang]

Note:
I also add plugs: "shutdown,core-support, process-control",but it is no longer 
effective.

Thanks for any help!

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

Title:
  Calling reboot or poweroff on a node-red snap is fail

Status in apparmor package in Ubuntu:
  New

Bug description:
  OS:Ubuntu 16.04.3-amd64

  when I run command "reboot" or "poweroff" in the node-red snap.It is
  no longer effective.

  my snapcraft.yaml:

  name: nodered
  version: 1.00
  summary: A visual tool for wiring the Internet of Things
  description: Node-RED is a tool for wiring together hardware devices, APIs 
and online services in new and interesting ways.
  confinement: strict
  grade: stable

  apps:
red:
  daemon: simple
  command: bin/launch
  plugs:
- network-bind
- network
- network-observe

  parts:
red:
  plugin: nodejs
  node-packages:
- node-red
- node-red-dashboard
  filesets:
othermodules: [ -lib/node_modules/npm ]
  stage: [ $othermodules ]
settings:
  plugin: dump
  source: settings
  filesets:
settings:
  - .
  organize:
start.sh : bin/launch
  snap:
- .
  filesets:
all: [ . ]
  
  when I run "poweroff" in the node-red snap, the syslog will show:

  Dec 14 04:07:34 zy-PR-VR4 bor.red[1905]: 14 Dec 04:07:34 - [info] 
[exec:command]  poweroff
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.060923] kauditd_printk_skb: 25 
callbacks suppressed
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.060927] audit: type=1400 
audit(1513242454.177:329): apparmor="ALLOWED" operation="exec" 
profile="snap.bor.red" name="/bin/systemctl" pid=2453 comm="sh" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0 
target="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061474] audit: type=1400 
audit(1513242454.177:330): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061480] audit: type=1400 
audit(1513242454.181:331): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061483] audit: type=1400 
audit(1513242454.181:332): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061487] audit: type=1400 
audit(1513242454.181:333): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061489] audit: type=1400 
audit(1513242454.181:334): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061493] audit: type=1400 
audit(1513242454.181:335): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061496] audit: type=1400 
audit(1513242454.181:336): apparmor="ALLOWED" operation="file_mmap" 
profile="snap.bor.red//null-/bin/systemctl" name="/bin/systemctl" pid=2453 
comm="poweroff" requested_mask="rm" denied_mask="rm" fsuid=0 ouid=0

  it looks the command is runing in the ubuntu 16.04.3, but it does not 
effective.
  ---
  when I run "dmesg" in the node-red snap, the syslog will show:

  bor.red[1905]: 14 Dec 04:10:02 - [info] [exec:command]  dmesg
  Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739205] kauditd_printk_skb: 90 
callbacks suppressed
  Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739207] audit: type=1400 
audit(1513242602.837:463): apparmor="ALLOWED" operation="exec" 
profile="snap.bor.red" name="/bin/dmesg" pid=2552 comm="sh" requested_mask="x" 
denied_mask="x" 

[Touch-packages] [Bug 1738307] Re: Can not move icons in dash

[jimav]

Now this is strange.  I used Settings->Dock to fiddle with the doc,
changing it's size and moving it to the bottom and back to the left side
(no net change).   Lo and behold, miving the icons now works!

So maybe this is a one-time glitch.  I upgraded, so there is Unity cruft
in my environment.

-> If anyone else observes the problem, please click the "affects me"
button at top left.  Let's see if I'm the only one.

For now, setting Status to Invalid.


P.S. I do live in California but have not been smoking anything
anything.

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

Title:
  Can not move icons in dash

Status in dash package in Ubuntu:
  Invalid

Bug description:
  The icons in the new 17.10 dash side-bar can not be re-arranged.  You
  can left-click and drag them sideways and then vertically to a new
  position, but when you un-click the icon snaps back to it's original
  position.

  In Ubuntu 11.10 this apparently worked in gnome-shell: There are
  instructions and a short video animation here:

    https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in-
  the-gnome-shell-favourites-bar

  That animation shows the other icons moving out of the way so that the
  one being dragged has a place to land.  But in Ubuntu 17.10 the other
  icons don't move at all.   Even dragging to empty space below all
  existing icons does not work (the dragged icon still snaps back).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: dash 0.5.8-2.3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 14 17:02:39 2017
  InstallationDate: Installed on 2017-12-13 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: dash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1738307/+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 1738307] [NEW] Can not move icons in dash

[jimav]

Public bug reported:

The icons in the new 17.10 dash side-bar can not be re-arranged.  You
can left-click and drag them sideways and then vertically to a new
position, but when you un-click the icon snaps back to it's original
position.

In Ubuntu 11.10 this apparently worked in gnome-shell: There are
instructions and a short video animation here:

  https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in-
the-gnome-shell-favourites-bar

That animation shows the other icons moving out of the way so that the
one being dragged has a place to land.  But in Ubuntu 17.10 the other
icons don't move at all.   Even dragging to empty space below all
existing icons does not work (the dragged icon still snaps back).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: dash 0.5.8-2.3ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 14 17:02:39 2017
InstallationDate: Installed on 2017-12-13 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: dash
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dash (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug artful

** Description changed:

- The icons in the dash side-bar can not be re-arranged.  You can left-
- click and drag them sideways and then vertically to a new position, but
- when you un-click the icon snaps back to it's original position.
+ The icons in the new 17.10 dash side-bar can not be re-arranged.  You
+ can left-click and drag them sideways and then vertically to a new
+ position, but when you un-click the icon snaps back to it's original
+ position.
  
  In Ubuntu 11.10 this apparently worked in gnome-shell: There are
  instructions and a short video animation here:
  
-   https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in-
+   https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in-
  the-gnome-shell-favourites-bar
  
  That animation shows the other icons moving out of the way so that the
  one being dragged has a place to land.  But in Ubuntu 17.10 the other
  icons don't move at all.   Even dragging to empty space below all
  existing icons does not work (the dragged icon still snaps back).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: dash 0.5.8-2.3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 14 17:02:39 2017
  InstallationDate: Installed on 2017-12-13 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: dash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  Can not move icons in dash

Status in dash package in Ubuntu:
  Invalid

Bug description:
  The icons in the new 17.10 dash side-bar can not be re-arranged.  You
  can left-click and drag them sideways and then vertically to a new
  position, but when you un-click the icon snaps back to it's original
  position.

  In Ubuntu 11.10 this apparently worked in gnome-shell: There are
  instructions and a short video animation here:

    https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in-
  the-gnome-shell-favourites-bar

  That animation shows the other icons moving out of the way so that the
  one being dragged has a place to land.  But in Ubuntu 17.10 the other
  icons don't move at all.   Even dragging to empty space below all
  existing icons does not work (the dragged icon still snaps back).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: dash 0.5.8-2.3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 14 17:02:39 2017
  InstallationDate: Installed on 2017-12-13 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: dash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1738307/+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 1738039] Re: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1735997
   package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 239

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

Title:
  package apport 2.20.1-0ubuntu2.14 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 239

Status in apport package in Ubuntu:
  New

Bug description:
  The normal update failed to finish properly.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.14
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Uname: Linux 4.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CrashReports:
   640:0:116:100989:2017-12-10 09:09:24.099369764 +0200:2017-12-10 
09:09:25.099369764 +0200:/var/crash/_usr_bin_atop.0.crash
   640:1000:116:5469774:2017-12-07 18:53:05.238692741 +0200:2017-12-09 
09:04:37.246543187 +0200:/var/crash/_usr_bin_compiz.1000.crash
   644:0:116:0:2017-12-10 09:09:25.703367143 +0200:2017-12-10 
09:09:25.703367143 +0200:/var/crash/_usr_bin_atop.0.upload
   600:0:116:84324:2017-12-10 09:10:03.171132802 +0200:2017-12-10 
09:10:04.171132802 +0200:/var/crash/apport.0.crash
   600:109:116:0:2017-12-10 09:09:26.815362361 +0200:2017-12-10 
09:09:26.815362361 +0200:/var/crash/_usr_bin_atop.0.uploaded
  Date: Sun Dec 10 09:10:04 2017
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.14
   Setting up apport (2.20.1-0ubuntu2.14) ...
   Segmentation fault
   dpkg: error processing package apport (--configure):
subprocess installed post-installation script returned error exit status 239
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 239
  InstallationDate: Installed on 2016-04-23 (599 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 239
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738039/+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 1738214] Re: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 239 zurück

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1735997
   package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 239

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

Title:
  package apport 2.20.1-0ubuntu2.14 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  239 zurück

Status in apport package in Ubuntu:
  New

Bug description:
  Happened at startup.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.14
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CrashReports: 600:0:117:123503:2017-12-12 14:32:48.437080383 +0100:2017-12-12 
14:32:49.437080383 +0100:/var/crash/apport.0.crash
  Date: Tue Dec 12 14:32:49 2017
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 239 zurück
  InstallationDate: Installed on 2017-10-26 (49 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 239 
zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738214/+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 1738051] Re: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1735997
   package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 239

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

Title:
  package apport 2.20.1-0ubuntu2.14 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 239

Status in apport package in Ubuntu:
  New

Bug description:
  error installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.14
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CrashReports:
   640:0:117:360050:2017-12-13 12:08:24.439189427 -0300:2017-12-13 
12:08:24.443189481 -0300:/var/crash/_usr_lib_xorg_Xorg.0.crash
   600:0:117:200154:2017-12-13 14:18:13.689794540 -0300:2017-12-13 
14:18:14.689794540 -0300:/var/crash/apport.0.crash
  Date: Wed Dec 13 14:18:14 2017
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.14
   Installing new version of config file /etc/init/apport.conf ...
   Segmentation fault
   dpkg: error processing package apport (--configure):
subprocess installed post-installation script returned error exit status 239
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 239
  InstallationDate: Installed on 2017-11-03 (40 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 239
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738051/+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 1738204] Re: error updating apport with apt

[Brian Murray]

** Tags added: plymouth-ping

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

Title:
  error updating apport with apt

Status in apport package in Ubuntu:
  New

Bug description:
  apt log session:

  ...
  Configuring python3-apport (2.20.8-0ubuntu4) ...
  Configuring apport (2.20.8-0ubuntu4) ...
  Job for apport.service failed because timeout was exceeded.
  See "systemctl status apport.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript apport, action "start" failed.
  ● apport.service - LSB: automatic crash report generation
      Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
      Active: failed (Result: timeout) since Thu 2017-12-14 08:43:36 -02; 7ms 
ago
    Docs: man: systemd-sysv-generator (8)
     Process: 9187 ExecStart = / etc / init.d / apport start (code = killed, 
signal = TERM)
   Tasks: 2 (limit: 4915)
      CGroup: /system.slice/apport.service
      └─9190 plymouth --ping

  ...

  $ systemctl status apport.service

  ● apport.service - LSB: automatic crash report generation
 Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
 Active: failed (Result: timeout) since Thu 2017-12-14 08:43:36 -02; 2h 
35min ago
   Docs: man:systemd-sysv-generator(8)
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/apport.service
 └─9190 plymouth --ping

  dez 14 08:38:36 etm systemd[1]: Starting LSB: automatic crash report 
generation...
  dez 14 08:43:36 etm systemd[1]: apport.service: Start operation timed out. 
Terminating.
  dez 14 08:43:36 etm systemd[1]: apport.service: Failed with result 'timeout'.
  dez 14 08:43:36 etm systemd[1]: Failed to start LSB: automatic crash report 
generation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu4
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 14 11:02:39 2017
  InstallationDate: Installed on 2017-09-29 (75 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738204/+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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on

[dinamic]

FIXED FOR ME

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

Title:
  Copy-paste and text selection doesn't work when caps-lock is on

Status in nux package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps 
Lock is on

  [Test case]
  0) Set Caps-Lock on in your keyboard
  1) Open dash, and write something
  2) Ctrl+A should select all the text, Ctrl+C should copy,
     Ctrl+V should paste and Ctrl+X should cut

  Currently they don't work unless caps-lock is turned off

  [Possible regression]
  Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling 
won't work anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 1526956] Re: klibc does not support rfc3442; needed for netboot

[Benjamin Drung]

I implemented classless routes support. I will publish the patch next
week.

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

Title:
  klibc does not support rfc3442; needed for netboot

Status in klibc package in Ubuntu:
  Confirmed

Bug description:
  klibc does not support classless static routes. If classes routing is
  used for a netboot device (NFS, iscsi) these devices will fail to
  boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1526956/+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 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Brian Murray]

Hello Andres, or anyone else affected,

Accepted resolvconf into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu4.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags removed: verification-done
** Tags added: verification-needed verification-needed-zesty

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Released
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in resolvconf source package in Trusty:
  Fix Released
Status in resolvconf source package in Xenial:
  Fix Released
Status in resolvconf source package in Zesty:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.

  MAAS 2.3 uses this for the installation environment and also the rescue
  environment.  In most cases the 14.04 specific fix will only apply
  to installation as 16.04 is most likely to be used in rescue mode.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.
    trusty uses 'running-in-container' to determine this.
    xenial uses 'systemd-detect-virt'

  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]

  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 

[Touch-packages] [Bug 1718487] Re: package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade: пакет dnsmasq-base не готов к настройке настройка невозможна (текущее состояние: «half-install

[Andreas Hasenack]

Thanks for filing this but in Ubuntu, and sorry for the late reply.

If you are still experiencing this problem, could you please try the
following commands:

sudo apt update
sudo apt install --reinstall dnsmasq-base

If that complains it cannot find the right dnsmasq-base package to reinstall, 
then just run:
sudo apt install dnsmasq-base

Thanks


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

Title:
  package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade:
  пакет dnsmasq-base не готов к настройке  настройка невозможна (текущее
  состояние: «half-installed»)

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  LTS 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 20 15:09:22 2017
  ErrorMessage: пакет dnsmasq-base не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
  InstallationDate: Installed on 2016-09-22 (362 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: dnsmasq
  Title: package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade: 
пакет dnsmasq-base не готов к настройке  настройка невозможна (текущее 
состояние: «half-installed»)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1718487/+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 1725680] Re: DNS name resolution doesn't work on Artful

[Jan Rathmann]

@Sebastien
Well, hmmm, it is possible that #1727237 is the same bug. The wifi I was using 
at that time was a bit weird in regards of having a captive portal: It seemed 
to me that it was implemented to show a captive portal in principle when 
connecting to it. But while some other people around were directed to that 
captive portal everytime they connected to the wifi, I saw it on my devices 
(Android phone and the laptop where I send this report from) only at the first 
connection - then I regularily connected to this wifi for months(!) and the 
captive portal was never shown again to me! And that's the reason why I even 
forgot to metion it at all in this bug report.

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

Title:
  DNS name resolution doesn't work on Artful

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  If I boot my laptop with a live image or an installation of Ubuntu
  17.10, DNS name resolution doesn't work (which means I can't access
  any website).

  Steps to reproduce:
  - Boot laptop with Ubuntu 17.10 live image
  - Connect to my wireless network
  - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with 
the error message "Name or service not known"
  - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.

  As a workaround, I can get a temporarily working DNS resolution by
  manually editing /etc/resolv.conf (symlink to /run/systemd/resolve
  /stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or
  some other known DNS server.

  On Ubuntu 17.04 this bug is not present.

  The original address in /run/systemd/resolve/stub-resolve.conf is
  127.0.0.53 . I get immediate replies if I ping this address, but
  nevertheless DNS resolution doesn't work.

  It seems that the service systemd-networkd isn't active by default:
  $ sudo systemctl status systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendo
 Active: inactive (dead)
   Docs: man:systemd-networkd.service(8)

  Manually starting it doesn't seem to help for this bug.

  systemd-resolved is active:

  $ sudo systemctl status systemd-resolved
  ● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor
 Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
   Docs: man:systemd-resolved.service(8)
 https://www.freedesktop.org/wiki/Software/systemd/resolved
 
https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
 
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
   Main PID: 1095 (systemd-resolve)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/systemd-resolved.service
 └─1095 /lib/systemd/systemd-resolved

  Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors:
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 
49aac11d7b6f644
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 
e06d44b80b8f1d3
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 
10.in-add
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'.
  Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  Date: Sat Oct 21 12:26:00 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Acer Extensa 5635Z
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V0.3305
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 

[Touch-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language

[Brian Murray]

Hello sojusnik, or anyone else affected,

Accepted gnome-control-center into artful-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.26.2-0ubuntu0.2 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: gnome-control-center (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Gnome's Activities Overview search is always in English, regardless of
  the system language

Status in gnome-control-center:
  Fix Released
Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gettext package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gettext source package in Artful:
  Invalid
Status in gnome-control-center source package in Artful:
  Fix Committed
Status in gnome-shell source package in Artful:
  Invalid

Bug description:
  [ Description ]

  In GNOME's activities overview, search entries from gnome-control-
  center aren't translated.

  [ Fix ]

  setlocale() wasn't being called until after the model that supplies
  search results was constructed. We fix the initialisation code to run
  slightly later, after setlocale() has been called.

  [ QA ]

  1. Open a session in a non-English locale which has gnome-control-center 
translations (French works).
  2. Hit super and type an "a"
  3. There should be some results from "Settings". They should be in French (or 
whatever language you're using).

  [ Regression potential ]

  If we misunderstood when the initialisation phases in GtkApplication
  ran then there could be a race condition. You'd see that manifesting
  as either a crash in the search provider or no results being returned.
  Make sure there aren't crahes reported in errors.u.c.

  [ Original description ]

  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1491787/+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 1718029] Re: cloudstack and azure datasources broken when using netplan/systemd-networkd

[Scott Moser]

This bug is believed to be fixed in cloud-init in 1705804. If this is
still a problem for you, please make a comment and set the state back to
New

Thank you.

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

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

Title:
  cloudstack and azure datasources broken when using netplan/systemd-
  networkd

Status in cloud-init:
  Fix Released
Status in netplan:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu artful, cloud-init renders network configuration through netplan.
  This means that there is no dhclient and thus no /var/lib/dhclient/*.leases.

  Azure and CloudStack both are reading those leases file to get useful
  information about the platform.

  Specifically:
   * Azure reads option-245 from the dhclient response to find the IP address 
of the metadata service.
   * CloudStack reads the 'dhcp-server-identifier' option in the dhclient 
response to get the address of the virtual router (metadata service). [1]

  In ubuntu this happens to be done with systemd-networkd, so cloud-init
  can possibly probably interact over the dbus with systemd-networkd to
  get information.  However that is less than ideal, as ultimately
  cloud-init should not need to know that it systemd-networkd is
  involved.  It should be hidden via netplan.  So there should be an
  interface to get current networking configuratoin information from
  netplan including dhcp lease response info.

  
  --
  [1] 
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/virtual_machines/user-data.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cloud-init 0.7.9-280-ge626966e-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CloudName: Amazon - Ec2
  Date: Mon Sep 18 19:56:40 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  user_data.txt:
   #cloud-config
   {}

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1718029/+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 1723956] Re: busybox-static: several network applets segfaulting

[Steve Langasek]

Thanks, adding a systemd task to this bug for libnss-resolve.

It may be that this bug is only reproducible in 17.04 because that was
the only release in which libnss-resolve was installed by default.  (We
dropped this package from ubuntu-standard in 17.10.)

This also may not be fixable on the systemd side, since the failure
happens with a static binary calling into an NSS module that calls into
pthreads.

And it may not be fixable in busybox without substantial rework of the
'nslookup' applet, which appears to only front onto the glibc resolver
apis instead of actually talking to the specified nameserver... which is
what nslookup is defined to do.

** Changed in: busybox (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  busybox-static: several network applets segfaulting

Status in busybox package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  On a fully up-to-date Ubuntu 17.04, running most applets from busybox-
  static that are network-related lead to a segfault. Example:

  $ busybox nslookup google.com 8.8.8.8
  Server:8.8.8.8
  Segmentation fault

  $ busybox
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) multi-call binary.
  [...]

  $ apt-cache policy busybox
  busybox:
Installed: (none)
Candidate: 1:1.22.0-19ubuntu2
Version table:
   1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/universe amd64 Packages

  $ dpkg -S /bin/busybox 
  busybox-static: /bin/busybox

  $ apt-cache policy busybox-static
  busybox-static:
Installed: 1:1.22.0-19ubuntu2
Candidate: 1:1.22.0-19ubuntu2
Version table:
   *** 1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status


  This even happens when passing invalid domains or DNS servers to use
  that don't actually run any DNS service. (like "busybox nslookup
  google.com 1.2.3.4" or "busybox nslookup bar.foof00 8.8.8.8"), so it
  seems to be early in the network setup.

  I could not reproduce the problem on the very same system when compiling 
stock busybox 1.22.1 (why even? we're at 1.27.x!) myself, neither with a recent 
git clone. Also two VMs I had at hand running Ubuntu 14.04 and 16.04 didn't 
show this problem with busybox-static. Installing the package "busybox" (which 
removes busybox-static) fixes the problem on 17.04.
  The only thing that might be related in any way about my system is that it 
has no IPv6 connectivity (apart from the link-local address).

  I also sent a crash report when the apport window popped up, but I
  have no idea where this ends up and how to add further information,
  hence this report here. Please let me know if this seemingly trivial
  bug cannot be reproduced instantly, so I can try to assist with
  further information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1723956/+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 1723956] Re: busybox-static: several network applets segfaulting

[Steve Langasek]

btw, the bug description says 'several network applets'.  Which besides
nslookup do you see this with?

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

Title:
  busybox-static: several network applets segfaulting

Status in busybox package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  On a fully up-to-date Ubuntu 17.04, running most applets from busybox-
  static that are network-related lead to a segfault. Example:

  $ busybox nslookup google.com 8.8.8.8
  Server:8.8.8.8
  Segmentation fault

  $ busybox
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) multi-call binary.
  [...]

  $ apt-cache policy busybox
  busybox:
Installed: (none)
Candidate: 1:1.22.0-19ubuntu2
Version table:
   1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/universe amd64 Packages

  $ dpkg -S /bin/busybox 
  busybox-static: /bin/busybox

  $ apt-cache policy busybox-static
  busybox-static:
Installed: 1:1.22.0-19ubuntu2
Candidate: 1:1.22.0-19ubuntu2
Version table:
   *** 1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status


  This even happens when passing invalid domains or DNS servers to use
  that don't actually run any DNS service. (like "busybox nslookup
  google.com 1.2.3.4" or "busybox nslookup bar.foof00 8.8.8.8"), so it
  seems to be early in the network setup.

  I could not reproduce the problem on the very same system when compiling 
stock busybox 1.22.1 (why even? we're at 1.27.x!) myself, neither with a recent 
git clone. Also two VMs I had at hand running Ubuntu 14.04 and 16.04 didn't 
show this problem with busybox-static. Installing the package "busybox" (which 
removes busybox-static) fixes the problem on 17.04.
  The only thing that might be related in any way about my system is that it 
has no IPv6 connectivity (apart from the link-local address).

  I also sent a crash report when the apport window popped up, but I
  have no idea where this ends up and how to add further information,
  hence this report here. Please let me know if this seemingly trivial
  bug cannot be reproduced instantly, so I can try to assist with
  further information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1723956/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Jamie Hutber]

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

I moved from a AMD Radeon onto a GeForce and setting up the graphics
cards, I've never seen this issue before. But now, as others have said.
i get the same thing.

Running 16.04 Kernal 4.4.0-97

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+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 1577168] Re: Browser hangs Ubuntu 16.04

[VanillaMozilla]

"@Roberto: can you please run webbrowser-app in a terminal and paste
here the output? Is the application crashing, or hanging?"

No, he can't get the output, because the system is completely
unresponsive.  I tried to redirect terminal output to a file, but the
file was empty.  I did, however, take a very good picture of the screen,
and can send you an image if it will help.

There are several error messages, including:
(webbrowser-app:2541): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf: Permission denied.  dconf will not work properly.

libGL errors
MESA-LOADER: failed to retrieve device information
Version 4 or later of flush extension not found
failed to load driver: i915

There are many other errors--too many to type unless I'm certain it will
help.


I have the identical symptoms as in comment 13.  System is similar except I 
have Inspiron with i5 processor.  Same Intel graphics.  I am running Ubuntu 
16.04 64 bit.

The system draws the frame for the window, but the app does not draw its
own space.

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

Title:
  Browser hangs Ubuntu 16.04

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When I activate Browser or click on Amazon button (which activates Browser), 
Ubuntu 16.04 hangs. This occurrence should not happen.
  An exception to this problem is that the mouse pointer is movable initially. 
In the extreme case, the mouse pointer hangs also. 

  This problem does not occur when activating Firefox or Chromium.
  Occurs in a freshly installed Ubuntu 16.04 system.
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  N: Unable to locate package pkgname

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1577168/+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 1723956] Re: busybox-static: several network applets segfaulting

[Steve Langasek]

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

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

Title:
  busybox-static: several network applets segfaulting

Status in busybox package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  On a fully up-to-date Ubuntu 17.04, running most applets from busybox-
  static that are network-related lead to a segfault. Example:

  $ busybox nslookup google.com 8.8.8.8
  Server:8.8.8.8
  Segmentation fault

  $ busybox
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) multi-call binary.
  [...]

  $ apt-cache policy busybox
  busybox:
Installed: (none)
Candidate: 1:1.22.0-19ubuntu2
Version table:
   1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/universe amd64 Packages

  $ dpkg -S /bin/busybox 
  busybox-static: /bin/busybox

  $ apt-cache policy busybox-static
  busybox-static:
Installed: 1:1.22.0-19ubuntu2
Candidate: 1:1.22.0-19ubuntu2
Version table:
   *** 1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status


  This even happens when passing invalid domains or DNS servers to use
  that don't actually run any DNS service. (like "busybox nslookup
  google.com 1.2.3.4" or "busybox nslookup bar.foof00 8.8.8.8"), so it
  seems to be early in the network setup.

  I could not reproduce the problem on the very same system when compiling 
stock busybox 1.22.1 (why even? we're at 1.27.x!) myself, neither with a recent 
git clone. Also two VMs I had at hand running Ubuntu 14.04 and 16.04 didn't 
show this problem with busybox-static. Installing the package "busybox" (which 
removes busybox-static) fixes the problem on 17.04.
  The only thing that might be related in any way about my system is that it 
has no IPv6 connectivity (apart from the link-local address).

  I also sent a crash report when the apport window popped up, but I
  have no idea where this ends up and how to add further information,
  hence this report here. Please let me know if this seemingly trivial
  bug cannot be reproduced instantly, so I can try to assist with
  further information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1723956/+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 1692561] Re: Version 4.5 has been released

[Launchpad Bug Tracker]

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

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

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

Title:
  Version 4.5 has been released

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  Version 4.5 has just been released so it would be nice to get it into
  the repositories some time soon: https://github.com/shadow-
  maint/shadow/releases/tag/4.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1692561/+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 1475094] Re: Warning because an already existing user is tried to be created

[Amr Ibrahim]

** Changed in: adduser (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Warning because an already existing user is tried to be created

Status in adduser package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in adduser package in Debian:
  Fix Released

Bug description:
  I'm using Ubuntu 15.10 dev with systemd/udev 222-1ubuntu4 and on the
  last upgrades I have noticed that these packages are trying to create
  users which already exists. On reinstalling them udev shows on setting
  up "addgroup: The group `input' already exists as a system group.
  Exiting." and systemd shows on setting up "addgroup: The group
  `systemd-journal' already exists as a system group. Exiting." and
  "addgroup: The group `systemd-journal-remote' already exists as a
  system group. Exiting.". Maybe it could be checked if a user exists to
  avoid showing a warning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1475094/+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 1700753] Re: Merge adduser 3.116 (main) from Debian unstable (main)

[Amr Ibrahim]

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

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

Title:
  Merge adduser 3.116 (main) from Debian unstable (main)

Status in adduser package in Ubuntu:
  Fix Released

Bug description:
  Please merge adduser 3.116 (main) from Debian unstable (main)

  Sorry, I cannot work on the merge myself. I am filing this for
  reference.

  Explanation of the Ubuntu delta:
    * testsuite/runsuite.sh: Add the testsuite directory to @INC, so it can find
  the tests.
    * extrausers support for adduser (LP: #1323732)
    * Add autopkgtest. (LP: #1246331)
    * Move ecryptfs-utils from recommends, to suggests. (LP: #1188108)
  Adduser has moved from required to minimal set, and thus started to
  pull ecryptfs-utils and cryptsetup into minimal installs, which is an
  undesired effect.
    * Merge from Debian unstable, remaining changes:
  - AdduserCommon.pm, adduser, adduser.8, adduser.conf.5: Allow uppercase
    letters in the names of system users. This is done by having a separate
    NAME_REGEX_SYSTEM configuration setting which applies when --system is
    specified. (Soren Hansen)
  - Add support for encrypting home directories:
    + adduser: Add --encrypt-home option, which calls ecryptfs-setup-private
  for the hard work.
    + doc/adduser.8: document the --encrypt-home option
    + debian/control: recommend ecryptfs-utils >= 67-1
    + deluser: remove all of /var/lib/ecryptfs/$user with --remove-home
    * Dropped changes, included in Debian:
  - Mark adduser Multi-Arch: foreign.

  Changelog entries since current artful version 3.113+nmu3ubuntu5:

  adduser (3.116) unstable; urgency=medium

    * Advise installation of 'perl' rather than 'perl-modules'
  (Closes: #840982)
    * Improve distinction between informational and essential messages
  (Closes: #763055)
    * Improve message accompanying error code for creating system user
  (Closes: #708073, #759740)
    * testsuite: add current directory to Perl module search path
    * Use /usr/sbin/nologin instead of /bin/false for default system shell
  (Closes: #845791)
    * Bump Standards-Version to 4.0.1

   -- Afif Elghraoui   Sat, 12 Aug 2017 16:05:34 -0400

  adduser (3.115) unstable; urgency=medium

    [ Afif Elghraoui ]
    * Adopt package (Closes: #811411)
    * Set Vcs-* fields to point to Git repository
    * Bump Standards-Version to 3.9.8
    * Extend last_{u,g}id to 5 to match policy update from 3.9.0
  (Closes: #776203)
    * Note to work on the lintian error for debconf template.
    * Fix path to rpcinfo, used for NIS support.
  (Thanks to Nis Martensen for report and patch).
    * Update Vietnamese translations (Closes: #825610)
  Thanks to all translators for providing updates

    [ Helge Kreutzmann ]
    * Debconf:
    * Update Turkish translation. Closes: #676356.
    * Fix language field in Norwegian translation. Closes: #695997.
    * Program (translation):
    * Use "--previous" when generating the updated po files.
    * Mention "--add_extra_groups" in --help output. Closes: #547911.
    * Update Japanese translation. Closes: #697109.
    * Update Czech translation. Closes: #825734.
    * Update Slovak translation. Closes: #825770.
    * Updated Danish translation. Closes: #825778.
    * Update Portuguese translation. Closes: #825867.
    * Update Russian translation. Closes: #825876.
    * Update Japanese translation. Closes: #825973.
    * Update Swedish translation. Closes: #826947.
    * Update Brazilian Portuguese translation. Closes: #826965.
    * Update Italian translation. Closes: #827011.
    * Update French translation. Closes: #827140.
    * Update Hungarian translation.
    * Update Polish translation.
    * Update Basque translation.
    * Update Norwegian translation.
    * Manpage:
    * Improve pointer to customization files. Closes: #611898.
    * Improve pointer to NAME_REGEX. Closes: #508740.
    * Document --only-if-empty in delgroup.8. Closes: #722583.
    * Format SEE ALSO section correctly in all man pages.
    * Various formatting and minor language updates noted by the German
  translator(s).
    * Fixes in the German translation. Closes: #685529, #698483.
    * Update Portuguese translation. Closes: #756180, #825867.
    * Update Danish translation. Closes: #825777.
    * Update Russian translation. Closes: #825944.
    * Update Italian translation. Closes: #827012.
    * Update Polish translation.
    * Update French translation.
    * Update German translation.
    * Update example from John Zaitseff  to version 4.9.
  Thanks. 

[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Brian Murray]

Hello Victor, or anyone else affected,

Accepted maas into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/maas/1.9.5+bzr4599-0ubuntu1~14.04.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed verification-needed-trusty

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

Status in MAAS:
  Won't Fix
Status in MAAS 1.9 series:
  In Progress
Status in maas package in Ubuntu:
  Won't Fix
Status in snapd package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  New
Status in maas source package in Trusty:
  Fix Committed
Status in snapd source package in Trusty:
  Invalid
Status in systemd source package in Trusty:
  New

Bug description:
  [impact]
  Since Trusty uses upstart by default, MAAS manages its services with upstart. 
However, when a user installs systemd (even if it is not used as the init 
system), MAAS detects systemd installed and tries to manage its services via 
systemd. This obviously creates issues and prevents MAAS from working.

  [Test Case]
  1. Install & configure MAAS
  2. Add machines
  3. install systemd
  4. MAAS will fail to manage machines

  [Regression potential]
  Minimal. This just ensures that upstart is detected correctly even if systemd 
is installed (but not used).

  [Original bug report]
  Trusty uses upstart by default, and installing snapd (e.g. for livepatch 
purposes), pulls systemd too. In this setup, upstart is _not_ replaced by 
systemd, but MAAS "detects" systemd as init because of the existence of 
/run/systemd/system:

  @src/provisioningserver/utils/__init__.py:505

  SYSTEMD_RUN_PATH = '/run/systemd/system'

  def get_init_system():
  """Returns 'upstart' or 'systemd'."""
  if os.path.exists(SYSTEMD_RUN_PATH):
  return 'systemd'
  else:
  return 'upstart'

  One possible solution would be to check if /sbin/init is a symlink
  pointing to /lib/systemd/systemd:

  def get_init_system():
  """Returns 'upstart' or 'systemd'."""
  initpath = os.readlink("/sbin/init")
  if (initpath == "/lib/systemd/systemd"):
  return 'systemd'
  else:
  return 'upstart'

  Other affected parts of the code are the postinst files for maas-proxy
  and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst),
  throwing an error if maas is installed after systemd in Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+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 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Andres Rodriguez]

@I've uploaded the new package. I've tested an upgrade to Xenial to
ensure there are no issues and confirm it is good to go.

** Changed in: maas/1.9
 Assignee: Andres Rodriguez (andreserl) => (unassigned)

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

Status in MAAS:
  Won't Fix
Status in MAAS 1.9 series:
  In Progress
Status in maas package in Ubuntu:
  Won't Fix
Status in snapd package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  New
Status in maas source package in Trusty:
  Triaged
Status in snapd source package in Trusty:
  Invalid
Status in systemd source package in Trusty:
  New

Bug description:
  [impact]
  Since Trusty uses upstart by default, MAAS manages its services with upstart. 
However, when a user installs systemd (even if it is not used as the init 
system), MAAS detects systemd installed and tries to manage its services via 
systemd. This obviously creates issues and prevents MAAS from working.

  [Test Case]
  1. Install & configure MAAS
  2. Add machines
  3. install systemd
  4. MAAS will fail to manage machines

  [Regression potential]
  Minimal. This just ensures that upstart is detected correctly even if systemd 
is installed (but not used).

  [Original bug report]
  Trusty uses upstart by default, and installing snapd (e.g. for livepatch 
purposes), pulls systemd too. In this setup, upstart is _not_ replaced by 
systemd, but MAAS "detects" systemd as init because of the existence of 
/run/systemd/system:

  @src/provisioningserver/utils/__init__.py:505

  SYSTEMD_RUN_PATH = '/run/systemd/system'

  def get_init_system():
  """Returns 'upstart' or 'systemd'."""
  if os.path.exists(SYSTEMD_RUN_PATH):
  return 'systemd'
  else:
  return 'upstart'

  One possible solution would be to check if /sbin/init is a symlink
  pointing to /lib/systemd/systemd:

  def get_init_system():
  """Returns 'upstart' or 'systemd'."""
  initpath = os.readlink("/sbin/init")
  if (initpath == "/lib/systemd/systemd"):
  return 'systemd'
  else:
  return 'upstart'

  Other affected parts of the code are the postinst files for maas-proxy
  and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst),
  throwing an error if maas is installed after systemd in Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+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 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1737662

** Tags added: iso-testing

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in busybox package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?  ?  

Re: [Touch-packages] [Bug 1737662] Comment bridged from LTC Bugzilla

[Steve Langasek]

On Thu, Dec 14, 2017 at 05:09:56PM -, bugproxy wrote:
> --- Comment From bren...@br.ibm.com 2017-12-14 12:05 EDT---
> Can we consider this fixed in the daily images already?

When you this is fixed, the daily images should again pass their smoketests
and you should see updated images at
http://cdimage.ubuntu.com/ubuntu-server/daily/current/

The fix has only just landed in the bionic release, so will take time to
publish and make it into a daily image.

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in busybox package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?

[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: New => Fix Committed

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in busybox package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?  ?  ?
?   ?   ?  ?
?  ? 

[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

[Launchpad Bug Tracker]

This bug was fixed in the package busybox - 1:1.27.2-2ubuntu3

---
busybox (1:1.27.2-2ubuntu3) bionic; urgency=medium

  * debian/patches/CVE-2011-5325-2.patch: disable patch for now as the
behaviour is relied upon by debootstrap. (LP: #1737662)

 -- Marc Deslauriers   Tue, 12 Dec 2017
12:58:01 -0500

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

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  New
Status in busybox package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?  

[Touch-packages] [Bug 1737662] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From bren...@br.ibm.com 2017-12-14 12:05 EDT---
Can we consider this fixed in the daily images already?

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  New
Status in busybox package in Ubuntu:
  Confirmed

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?  ?  ?
?   ?   ?  ?

[Touch-packages] [Bug 1728069] Re: glmark2-es2-wayland hangs

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.29.0-0ubuntu1

---
mir (0.29.0-0ubuntu1) bionic; urgency=medium

  [ Alan Griffiths ]
  * New upstream release 0.29.0(https://launchpad.net/mir/+milestone/0.29.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . miral ABI unchanged at 2
  . mirserver ABI bumped to 46
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 61
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 13
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 7
  . mircore ABI unchanged at 1
- Enhancements:
  . Update docs to reflect recent changes
  . Initial cut at integrating Wayland conformance tests
  . Fix Wayland conformance test failures
  . Fix build & runtime issues on Fedora 26, 27 & rawhide
  . benchmarks: Use standard options to install perf framework on
non-Debian distros
  . Test (and fix) SeatObserver
  . Added the "smoke test" script from old CI
- Bugs fixed:
  . [mir_demo_server] extend (not replace) the default error reporting.
(LP: #1728581)
  . Releasing Wayland buffers must occur on the executor thread.
(LP: #1728069)
  . [miral-desktop] Check that user is logged into the VT before using it
(LP: #1728574)
  . Allow alternative cursor themes to be specified in a list. (Fixes #16)
  . Enable screen capture to SHM buffers. (Fixes #47)
  . Get mirscreencast working on Fedora. (Fixes #38)
  . [miral-shell] Check for titlebars when placing windows. (Fixes #37)
  . Create a mir_performance_tests executable (Fixes #69, #70)

  [ Mir CI Bot ]
  * Automatic build of revision 07295eacb3

 -- Christopher James Halse Rogers   Thu, 14 Dec 2017
12:40:56 +1100

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

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

Title:
  glmark2-es2-wayland hangs

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I've seen this in the following benchmarks:

  effects2d hangs (showing cube)
  function  hangs (showing pattern)
  texture   hangs (showing cube)

  It is most easy to reproduce with "texture"

  I've also saw it on "shading" after using --run-forever and leaving it
  for over ten minutes.

  While the test isn't important in itself, this does suggests we may be
  hitting a racy scenario.

  
  Note:

  I've also seen other glmark benchmarks fail in ways that are probably
  unrelated to Mir wayland support:

  ideas   => "Failed to link program" => "Set up failed"
  terrain => "Failed to link program" => segfault

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1728069/+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 1728581] Re: "mir_demo_server --help" does not show help text

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.29.0-0ubuntu1

---
mir (0.29.0-0ubuntu1) bionic; urgency=medium

  [ Alan Griffiths ]
  * New upstream release 0.29.0(https://launchpad.net/mir/+milestone/0.29.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . miral ABI unchanged at 2
  . mirserver ABI bumped to 46
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 61
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 13
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 7
  . mircore ABI unchanged at 1
- Enhancements:
  . Update docs to reflect recent changes
  . Initial cut at integrating Wayland conformance tests
  . Fix Wayland conformance test failures
  . Fix build & runtime issues on Fedora 26, 27 & rawhide
  . benchmarks: Use standard options to install perf framework on
non-Debian distros
  . Test (and fix) SeatObserver
  . Added the "smoke test" script from old CI
- Bugs fixed:
  . [mir_demo_server] extend (not replace) the default error reporting.
(LP: #1728581)
  . Releasing Wayland buffers must occur on the executor thread.
(LP: #1728069)
  . [miral-desktop] Check that user is logged into the VT before using it
(LP: #1728574)
  . Allow alternative cursor themes to be specified in a list. (Fixes #16)
  . Enable screen capture to SHM buffers. (Fixes #47)
  . Get mirscreencast working on Fedora. (Fixes #38)
  . [miral-shell] Check for titlebars when placing windows. (Fixes #37)
  . Create a mir_performance_tests executable (Fixes #69, #70)

  [ Mir CI Bot ]
  * Automatic build of revision 07295eacb3

 -- Christopher James Halse Rogers   Thu, 14 Dec 2017
12:40:56 +1100

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

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

Title:
  "mir_demo_server --help" does not show help text

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ mir_demo_server --help

  Expect: help text output to console
  Actual: platforms are listed and program exits

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1728581/+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 934291] Re: Deleting or stopping print jobs does not work

[Till Kamppeter]

I use Artful and I have added your PPA now. I have also removed "root"
as member of the "lpadmin" group in /etc/group, to have only your fix
active.

What did you change in your PPA compared to your patch from comment #36?

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in cups-pk-helper package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 1422679] Re: glitch viewing svg

[Bug Watch Updater]

** Changed in: librsvg
   Status: Confirmed => Expired

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

Title:
  glitch viewing svg

Status in librsvg:
  Expired
Status in librsvg package in Ubuntu:
  Confirmed

Bug description:
  open any libreoffice icons in eog in 
/usr/share/icons/gnome/scalable/mimetypes/
  this shows phantom white rectangle rescaling at different zoom levels
  opening in browsers produces no glitch

To manage notifications about this bug go to:
https://bugs.launchpad.net/librsvg/+bug/1422679/+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 1736770] Re: debian-installer/main-menu changes priority

[Joshua Powers]

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  debian-installer/main-menu changes priority

Status in debconf package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  During a test install of Bionic it appears that the debian-installer
  /main-menu option changes priority from medium to critical part way
  through the test:

  Dec  6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu
  Dec  6 04:18:55 debconf: <-- 30 question skipped
  Dec  6 04:18:55 debconf: --> GO
  ...
  Dec  6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title 
Description
  Dec  6 04:19:54 debconf: <-- 0 Install the system
  Dec  6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system
  Dec  6 04:19:54 debconf: <-- 0 value set
  Dec  6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu
  Dec  6 04:19:54 debconf: <-- 0 question will be asked
  Dec  6 04:19:54 debconf: --> GO

  Working test on Dec 1:
  https://paste.ubuntu.com/26126878/

  Failing test on Dec 6:
  https://paste.ubuntu.com/26126090/

  
  Steps to reproduce:
  1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/

  2. Pull out the kernel and initrd
  $ mkdir iso
  $ bsdtar xfp bionic-server-amd64.iso -C iso
  $ cp iso/install/vmlinuz .
  $ cp iso/install/initrd.gz .

  3. Create QEMU disk
  $ qemu-img create -f qcow2 vdisk.img 4G

  4. Launch ISO via QEMU
  $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \
  -initrd initrd.gz -kernel vmlinuz -display none -nographic \
  -hda vdisk.img -cdrom bionic-server-amd64.iso \
  -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical'

  5. Proceed with the install by 1) enter user info and 2) select disk

  6. Eventually the "Ubuntu installer main menu" will appear. Even if
  you click on "Install the system" the installation step will fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1738234] [NEW] package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped

[David-John Miller]

Public bug reported:

Installing 18.07 on WSL using do-distribution-upgrade -d

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1.2
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Dec 14 17:46:10 2017
Dmesg:
 
ErrorMessage: new bash package pre-installation script subprocess was killed by 
signal (Aborted), core dumped
RelatedPackageVersions:
 dpkg 1.19.0.4ubuntu1
 apt  1.2.24
SourcePackage: bash
Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash package 
pre-installation script subprocess was killed by signal (Aborted), core dumped
UpgradeStatus: Upgraded to xenial on 2017-12-14 (0 days ago)

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


** Tags: amd64 apport-package uec-images xenial

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

Title:
  package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash
  package pre-installation script subprocess was killed by signal
  (Aborted), core dumped

Status in bash package in Ubuntu:
  New

Bug description:
  Installing 18.07 on WSL using do-distribution-upgrade -d

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Dec 14 17:46:10 2017
  Dmesg:
   
  ErrorMessage: new bash package pre-installation script subprocess was killed 
by signal (Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.2.24
  SourcePackage: bash
  Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash 
package pre-installation script subprocess was killed by signal (Aborted), core 
dumped
  UpgradeStatus: Upgraded to xenial on 2017-12-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1738234/+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 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

[Jason Owen]

The original bug title was '15:10: bluetoothd reports "Not enough
handles to register service" at start', and the original bug description
described both the "Not enough free handles to register service" problem
and the "Failed to start discovery" problem[1]. Between #47 and #48, the
title and description were changed to focus on the "Failed to start
discovery" problem.

It seems to me that most of the people in the thread are focused on the
"Not enough free handles to register service", and aside from the close
message in #48, the only mention of the "Failed to start discovery"
problem was in the original description. Perhaps it would be useful to
split the "Failed to start discovery" problem off into its own bug and
keep this bug focused on "Not enough free handles to register service"?
That way the history and relevant log files are all kept in one place,
subscribers won't have to subscribe to another bug, and links pointing
to this bug for the "Not enough free handles to register service"
problem won't need to be updated.

[1]
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/comments/0

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

Title:
  15:10 and 16.04: bluetoothd "Failed to start discovery:
  org.bluez.Error.NotReady" after bluetoothd restarted

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl restart bluetooth

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1736757] Re: [PATCH] Avahi does not support local-only services via the loopback interface

[Till Kamppeter]

Done.

Thank you, Ken.

https://launchpad.net/ubuntu/+source/avahi/0.6.32-1ubuntu2

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

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

Title:
  [PATCH] Avahi does not support local-only services via the loopback
  interface

Status in avahi package in Ubuntu:
  Fix Released

Bug description:
  To allow the more sophisticated functionality of IPP network printers (web 
admin interface, query printer capabilities and job status from printer) also 
on USB printers, newer USB printers support the IPP-over-USB standard which is 
supported under Linux via the ippusbxd package from OpenPrinting. The ippusbxd 
daemon connects to the USB printer and mirrors it into a virtual IPP network 
printer on localhost, port 6.
  CUPS and cups-browsed find IPP printers by the printer's DNS-SD broadcasts. 
On Linux systems avahi-daemon is handling the registration of local services 
and also the discovery of remote services. This works well with local services 
shared to the network as Avahi does appropriate broadcasts on network 
interfaces (eth0, wlan0, ...) but Avahi does not handle the loopback device lo 
for local services ("localhost"). So the local-only IPP-over-USB printer on 
localhost:6, registered by ippusbxd does not get advertised, not even 
locally.
  The attached patchfor the Ubuntu package of Avahi adds support for such 
services.
  See also the upstream bug report https://github.com/lathiat/avahi/issues/125

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1736757/+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 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

We concluded that this isn't a snapd bug, except in so far as it depends
on systemd.

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

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

Status in MAAS:
  Won't Fix
Status in MAAS 1.9 series:
  In Progress
Status in maas package in Ubuntu:
  Won't Fix
Status in snapd package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  New
Status in maas source package in Trusty:
  Triaged
Status in snapd source package in Trusty:
  Invalid
Status in systemd source package in Trusty:
  New

Bug description:
  [impact]
  Since Trusty uses upstart by default, MAAS manages its services with upstart. 
However, when a user installs systemd (even if it is not used as the init 
system), MAAS detects systemd installed and tries to manage its services via 
systemd. This obviously creates issues and prevents MAAS from working.

  [Test Case]
  1. Install & configure MAAS
  2. Add machines
  3. install systemd
  4. MAAS will fail to manage machines

  [Regression potential]
  Minimal. This just ensures that upstart is detected correctly even if systemd 
is installed (but not used).

  [Original bug report]
  Trusty uses upstart by default, and installing snapd (e.g. for livepatch 
purposes), pulls systemd too. In this setup, upstart is _not_ replaced by 
systemd, but MAAS "detects" systemd as init because of the existence of 
/run/systemd/system:

  @src/provisioningserver/utils/__init__.py:505

  SYSTEMD_RUN_PATH = '/run/systemd/system'

  def get_init_system():
  """Returns 'upstart' or 'systemd'."""
  if os.path.exists(SYSTEMD_RUN_PATH):
  return 'systemd'
  else:
  return 'upstart'

  One possible solution would be to check if /sbin/init is a symlink
  pointing to /lib/systemd/systemd:

  def get_init_system():
  """Returns 'upstart' or 'systemd'."""
  initpath = os.readlink("/sbin/init")
  if (initpath == "/lib/systemd/systemd"):
  return 'systemd'
  else:
  return 'upstart'

  Other affected parts of the code are the postinst files for maas-proxy
  and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst),
  throwing an error if maas is installed after systemd in Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+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 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

> I would accept a version of this SRU that hard-codes the choice of
upstart as the init system on 14.04, because that is the only init
system supported in that version of Ubuntu.

OK, that sounds like a reasonable way forward. I've rejected the current
upload in the queue, and I believe Andres has agreed to upload a revised
version shortly.

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

Status in MAAS:
  Won't Fix
Status in MAAS 1.9 series:
  In Progress
Status in maas package in Ubuntu:
  Won't Fix
Status in snapd package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  New
Status in maas source package in Trusty:
  Triaged
Status in snapd source package in Trusty:
  Invalid
Status in systemd source package in Trusty:
  New

Bug description:
  [impact]
  Since Trusty uses upstart by default, MAAS manages its services with upstart. 
However, when a user installs systemd (even if it is not used as the init 
system), MAAS detects systemd installed and tries to manage its services via 
systemd. This obviously creates issues and prevents MAAS from working.

  [Test Case]
  1. Install & configure MAAS
  2. Add machines
  3. install systemd
  4. MAAS will fail to manage machines

  [Regression potential]
  Minimal. This just ensures that upstart is detected correctly even if systemd 
is installed (but not used).

  [Original bug report]
  Trusty uses upstart by default, and installing snapd (e.g. for livepatch 
purposes), pulls systemd too. In this setup, upstart is _not_ replaced by 
systemd, but MAAS "detects" systemd as init because of the existence of 
/run/systemd/system:

  @src/provisioningserver/utils/__init__.py:505

  SYSTEMD_RUN_PATH = '/run/systemd/system'

  def get_init_system():
  """Returns 'upstart' or 'systemd'."""
  if os.path.exists(SYSTEMD_RUN_PATH):
  return 'systemd'
  else:
  return 'upstart'

  One possible solution would be to check if /sbin/init is a symlink
  pointing to /lib/systemd/systemd:

  def get_init_system():
  """Returns 'upstart' or 'systemd'."""
  initpath = os.readlink("/sbin/init")
  if (initpath == "/lib/systemd/systemd"):
  return 'systemd'
  else:
  return 'upstart'

  Other affected parts of the code are the postinst files for maas-proxy
  and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst),
  throwing an error if maas is installed after systemd in Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+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 1738224] [NEW] Suspend broken after kernel upgrade

[Jeffrey Bouter]

Public bug reported:

My machine (XPS 13 9360) won't go into suspend properly after upgrading
from linux-image-4.13.0-17-generic to linux-image-4.13.0-19-generic.

This affects both suspend through lid close and "systemctl suspend".
Screen goes off, power led remains lit. Then after some time the screen
comes back on, is stuck and lets me wait for a few before becoming
responsive again.

Booting back into 4.13.0-17 resolved the issue.

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


** Tags: kernel-bug suspend systemd

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  Suspend broken after kernel upgrade

Status in linux package in Ubuntu:
  New

Bug description:
  My machine (XPS 13 9360) won't go into suspend properly after
  upgrading from linux-image-4.13.0-17-generic to linux-
  image-4.13.0-19-generic.

  This affects both suspend through lid close and "systemctl suspend".
  Screen goes off, power led remains lit. Then after some time the
  screen comes back on, is stuck and lets me wait for a few before
  becoming responsive again.

  Booting back into 4.13.0-17 resolved the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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 1738212] [NEW] Add GUI to enable/disable canonical-livepatch

[Andrea Azzarone]

Public bug reported:

Add a way to enable/disable canonical-livepatch from software-
properties-gtk as per
https://wiki.ubuntu.com/SoftwareUpdates?action=recall=224

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Changed in: software-properties (Ubuntu)
   Status: New => In Progress

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Branch linked: lp:~azzar1/software-properties/canonical-livepatch

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

Title:
  Add GUI to enable/disable canonical-livepatch

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Add a way to enable/disable canonical-livepatch from software-
  properties-gtk as per
  https://wiki.ubuntu.com/SoftwareUpdates?action=recall=224

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1738212/+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 1738214] [NEW] package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 239 zurück

[Urmel]

Public bug reported:

Happened at startup.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.14
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CrashReports: 600:0:117:123503:2017-12-12 14:32:48.437080383 +0100:2017-12-12 
14:32:49.437080383 +0100:/var/crash/apport.0.crash
Date: Tue Dec 12 14:32:49 2017
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 239 zurück
InstallationDate: Installed on 2017-10-26 (49 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 239 
zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package apport 2.20.1-0ubuntu2.14 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  239 zurück

Status in apport package in Ubuntu:
  New

Bug description:
  Happened at startup.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.14
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CrashReports: 600:0:117:123503:2017-12-12 14:32:48.437080383 +0100:2017-12-12 
14:32:49.437080383 +0100:/var/crash/apport.0.crash
  Date: Tue Dec 12 14:32:49 2017
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 239 zurück
  InstallationDate: Installed on 2017-10-26 (49 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 239 
zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738214/+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 530191] Re: Incorrect timezone selected in gnome clock applet

[Bug Watch Updater]

** Changed in: libgweather
   Status: New => Confirmed

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

Title:
  Incorrect timezone selected in gnome clock applet

Status in libgweather:
  Confirmed
Status in libgweather package in Ubuntu:
  Triaged

Bug description:
  In gnome clock applet when I add Astana, Kazakstan as a location, it
  automatically selects "Western Kazakhstan (GMT +5)" timezone. The
  correct value should be "Eastern Kazakhstan (GMT +6)", same as for
  Almaty.

  This problem persisted through at least three generations of Ubuntu and still 
present in alpha 10.4.
  Would be good if it finally gets resolved.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/530191/+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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up

[Dimitri John Ledkov]

Given https://bugs.freedesktop.org/show_bug.cgi?id=98254 and
https://github.com/systemd/systemd/pull/7609 and
https://bugs.launchpad.net/ubuntu/artful/+source/systemd/+bug/1734167
this is not solved, is it?

we cannot pull dbus earlier, and pulling resolved earlier means it will
not reconnect to the bus.

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

Title:
  resolve service in nsswitch.conf adds 25 seconds to failed lookups
  before systemd-resolved is up

Status in cloud-init:
  Fix Released
Status in D-Bus:
  Unknown
Status in cloud-init package in Ubuntu:
  Fix Released
Status in dbus package in Ubuntu:
  Won't Fix
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact] 
  In cases where cloud-init used dns during early boot and system was
  configured in nsswitch.conf to use systemd-resolvd, the system would
  timeout on dns attempts making system boot terribly slow.

  [Test Case]
  Boot a system on GCE.
  check for WARN in /var/log/messages
  check that time to boot is reasonable (<30 seconds).  In failure case the
  times would be minutes.

  [Regression Potential]
  Changing order in boot can be dangerous.  There is real chance for 
  regression here, but it should be fairly small as xenial does not include
  systemd-resolved usage.  This was first noticed on yakkety where it did.

  [Other Info]
  It seems useful to SRU this in the event that systemd-resolvd is used
  on 16.04 or the case where user upgrades components (admittedly small use
  case).

  === End SRU Template ===


  
  During boot, cloud-init does DNS resolution checks to if particular metadata 
services are available (in order to determine which cloud it is running on).  
These checks happen before systemd-resolved is up[0] and if they resolve 
unsuccessfully they take 25 seconds to complete.

  This has substantial impact on boot time in all contexts, because
  cloud-init attempts to resolve three known-invalid addresses ("does-
  not-exist.example.com.", "example.invalid." and a random string) to
  enable it to detect when it's running in an environment where a DNS
  server will always return some sort of redirect.  As such, we're
  talking a minimum impact of 75 seconds in all environments.  This
  increases when cloud-init is configured to check for multiple
  environments.

  This means that yakkety is consistently taking 2-3 minutes to boot on
  EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
  seconds thereafter in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Artful)
   Status: Confirmed => In Progress

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

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  In Progress
Status in cloud-init source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://;

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Artful)
   Status: New => In Progress

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

Title:
  systemd: handle undelegated cgroup2 hierarchy

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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 1737570] Re: Add support for RequiredForOnline in networkd

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Artful)
   Status: New => In Progress

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

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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 1708409] Re: kdump service does not start after configure/reboot

[Dimitri John Ledkov]

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

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => In Progress

** Changed in: systemd (Ubuntu Artful)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  New
Status in systemd source package in Artful:
  In Progress
Status in makedumpfile source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+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 1736955] Re: dep8 test systemd-fsckd fails on s390

[Dimitri John Ledkov]

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

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

Title:
  dep8 test systemd-fsckd fails on s390

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  In Progress

Bug description:
  The systemd-fsckd test has a constraint of isolation-machine, among
  others. Until recently, that actually prevented it from running on
  s390 because we were using containers for it.

  About 3 weeks ago, apparently we started using VMs for s390 dep8
  tests, so that constraint was finally satisfied and systemd-fsckd
  started to run. And to fail consistently, as can be see in
  http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x:

  Traceback (most recent call last):
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 267, in 
  boot_with_systemd_distro()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 243, in boot_with_systemd_distro
  enable_plymouth()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 224, in enable_plymouth
  plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read()
  FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg'

  There is no grub for s390, so this test must be adjusted or skipped in
  that architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1736955/+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 1738205] [NEW] no sound while playing audio

[Arsath]

Public bug reported:

Not able to hear audio through headset on ubuntu 14.04. Volume icon is
not visible..

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11.1
ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-80-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
Date: Thu Dec 14 18:47:12 2017
InstallationDate: Installed on 2016-02-04 (679 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/26/2011
dmi.bios.vendor: Acer
dmi.bios.version: P01-A4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Veriton M6610
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Veriton Series
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug trusty

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

Title:
  no sound while playing audio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not able to hear audio through headset on ubuntu 14.04. Volume icon is
  not visible..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Dec 14 18:47:12 2017
  InstallationDate: Installed on 2016-02-04 (679 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton M6610
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton Series
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738205/+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 1738204] [NEW] error updating apport with apt

[Edson T. Marques]

Public bug reported:

apt log session:

...
Configuring python3-apport (2.20.8-0ubuntu4) ...
Configuring apport (2.20.8-0ubuntu4) ...
Job for apport.service failed because timeout was exceeded.
See "systemctl status apport.service" and "journalctl -xe" for details.
invoke-rc.d: initscript apport, action "start" failed.
● apport.service - LSB: automatic crash report generation
    Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
    Active: failed (Result: timeout) since Thu 2017-12-14 08:43:36 -02; 7ms ago
  Docs: man: systemd-sysv-generator (8)
   Process: 9187 ExecStart = / etc / init.d / apport start (code = killed, 
signal = TERM)
 Tasks: 2 (limit: 4915)
    CGroup: /system.slice/apport.service
    └─9190 plymouth --ping

...

$ systemctl status apport.service

● apport.service - LSB: automatic crash report generation
   Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
   Active: failed (Result: timeout) since Thu 2017-12-14 08:43:36 -02; 2h 35min 
ago
 Docs: man:systemd-sysv-generator(8)
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/apport.service
   └─9190 plymouth --ping

dez 14 08:38:36 etm systemd[1]: Starting LSB: automatic crash report 
generation...
dez 14 08:43:36 etm systemd[1]: apport.service: Start operation timed out. 
Terminating.
dez 14 08:43:36 etm systemd[1]: apport.service: Failed with result 'timeout'.
dez 14 08:43:36 etm systemd[1]: Failed to start LSB: automatic crash report 
generation.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.8-0ubuntu4
ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
Uname: Linux 4.14.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportLog:
 
ApportVersion: 2.20.8-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 14 11:02:39 2017
InstallationDate: Installed on 2017-09-29 (75 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  error updating apport with apt

Status in apport package in Ubuntu:
  New

Bug description:
  apt log session:

  ...
  Configuring python3-apport (2.20.8-0ubuntu4) ...
  Configuring apport (2.20.8-0ubuntu4) ...
  Job for apport.service failed because timeout was exceeded.
  See "systemctl status apport.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript apport, action "start" failed.
  ● apport.service - LSB: automatic crash report generation
      Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
      Active: failed (Result: timeout) since Thu 2017-12-14 08:43:36 -02; 7ms 
ago
    Docs: man: systemd-sysv-generator (8)
     Process: 9187 ExecStart = / etc / init.d / apport start (code = killed, 
signal = TERM)
   Tasks: 2 (limit: 4915)
      CGroup: /system.slice/apport.service
      └─9190 plymouth --ping

  ...

  $ systemctl status apport.service

  ● apport.service - LSB: automatic crash report generation
 Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
 Active: failed (Result: timeout) since Thu 2017-12-14 08:43:36 -02; 2h 
35min ago
   Docs: man:systemd-sysv-generator(8)
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/apport.service
 └─9190 plymouth --ping

  dez 14 08:38:36 etm systemd[1]: Starting LSB: automatic crash report 
generation...
  dez 14 08:43:36 etm systemd[1]: apport.service: Start operation timed out. 
Terminating.
  dez 14 08:43:36 etm systemd[1]: apport.service: Failed with result 'timeout'.
  dez 14 08:43:36 etm systemd[1]: Failed to start LSB: automatic crash report 
generation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu4
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 14 11:02:39 2017
  InstallationDate: Installed on 2017-09-29 (75 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

[shemgp]

Hello,

Are you using Artful?  I've tested it again in Ubuntu 17.10 and the UI
doesn't get updated immediately but it does pause, resume, and cancel
jobs just fine: https://youtu.be/Z5IuAAtKlnI.

Could you test using this PPA:
https://launchpad.net/~shemgp/+archive/ubuntu/other-apps?

I'll test it in Xenial tomorrow in the office if it works there
(https://launchpad.net/~shemgp/+archive/ubuntu/xenial).

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in cups-pk-helper package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 1723956] Re: busybox-static: several network applets segfaulting

[Simon Rettberg]

Sure, here we go. It might be worth to note that this system was
installed as 12.04 or 12.10 and dist-upgraded ever since, so maybe this
would explain some oddities, although in general everything works just
fine.

libc6:
  Installed: 2.24-9ubuntu2.2
  Candidate: 2.24-9ubuntu2.2
  Version table:
 *** 2.24-9ubuntu2.2 500
500 http://ftp.fau.de/ubuntu zesty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages
100 /var/lib/dpkg/status
 2.24-9ubuntu2 500
500 http://ftp.fau.de/ubuntu zesty/main amd64 Packages


With trial and error I could identify that libnss-resolve seems to be the 
problem. Removing it from the hosts line in nsswitch fixes the issue. Probably 
not the best fix but at least it can fall back to the resolver stub via the 
localhost resolv.conf entry for some caching. Unfortunately I can't upgrade to 
17.10 yet until end of January to do additional testing.

** Attachment added: "original (faulty) nsswitch.conf"
   
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1723956/+attachment/5022596/+files/nsswitch.conf

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

Title:
  busybox-static: several network applets segfaulting

Status in busybox package in Ubuntu:
  Incomplete

Bug description:
  On a fully up-to-date Ubuntu 17.04, running most applets from busybox-
  static that are network-related lead to a segfault. Example:

  $ busybox nslookup google.com 8.8.8.8
  Server:8.8.8.8
  Segmentation fault

  $ busybox
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) multi-call binary.
  [...]

  $ apt-cache policy busybox
  busybox:
Installed: (none)
Candidate: 1:1.22.0-19ubuntu2
Version table:
   1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/universe amd64 Packages

  $ dpkg -S /bin/busybox 
  busybox-static: /bin/busybox

  $ apt-cache policy busybox-static
  busybox-static:
Installed: 1:1.22.0-19ubuntu2
Candidate: 1:1.22.0-19ubuntu2
Version table:
   *** 1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status


  This even happens when passing invalid domains or DNS servers to use
  that don't actually run any DNS service. (like "busybox nslookup
  google.com 1.2.3.4" or "busybox nslookup bar.foof00 8.8.8.8"), so it
  seems to be early in the network setup.

  I could not reproduce the problem on the very same system when compiling 
stock busybox 1.22.1 (why even? we're at 1.27.x!) myself, neither with a recent 
git clone. Also two VMs I had at hand running Ubuntu 14.04 and 16.04 didn't 
show this problem with busybox-static. Installing the package "busybox" (which 
removes busybox-static) fixes the problem on 17.04.
  The only thing that might be related in any way about my system is that it 
has no IPv6 connectivity (apart from the link-local address).

  I also sent a crash report when the apport window popped up, but I
  have no idea where this ends up and how to add further information,
  hence this report here. Please let me know if this seemingly trivial
  bug cannot be reproduced instantly, so I can try to assist with
  further information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1723956/+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 1726320] Re: suggested and destructive colours are too bright

[Merlijn Sebrechts]

I actually think the colors are good as they are. At least the green
color should be very bright because of it's unusual placement (on the
top of the window instead of on the bottom). We need to draw the user's
attention to it.

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

Title:
  suggested and destructive colours are too bright

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  IMO, so feel free to close this if you disagree, the suggested and
  destructive (green and red) colours that are used in GTK UIs are too
  bright.

  Attached is a screenshot from Marco that shows them both. (It's a
  faked up example, usually you don't see them together like that.)

  They draw the eye too much I think. It should be a hint for where you
  might or might not want to click, but not something that grabs your
  attention.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1726320/+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 1731417] Re: Installed printer removed after suspend/resume

[Alberto Donato]

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

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

Title:
  Installed printer removed after suspend/resume

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  After installing artful, I configured my HP LaserJet M1212nf via network as 
usual via hp-setup.
  Installation worked and I could print/scan via network, but next time I 
needed to print, the printer was gone from the system.
  Basically, every time I need to print, I have to install the printer again.
  I'm not sure when the printer disappears, but I can reproduce consistently.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:33:12 2017
  InstallationDate: Installed on 2017-07-30 (102 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1207538] Re: misrendering of SVG files (clipping paths)

[Bug Watch Updater]

** Changed in: librsvg
   Status: Confirmed => Expired

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

Title:
  misrendering of SVG files (clipping paths)

Status in librsvg:
  Expired
Status in cairosvg package in Ubuntu:
  Fix Released
Status in librsvg package in Ubuntu:
  Fix Released

Bug description:
  Generating an SVG file using matplotlib,

  from pylab import *

  x = linspace(0,2,101)
  plot(x,x)
  xlim(0,1)
  savefig('test.svg')

  gives the SVG file attached. This file views fine in Inkscape,
  Firefox, Chromium. However in Ristretto the blue line is not clipped
  properly and extends past the right side of the plot. The file's XML
  is pretty simple, with just one clip rectangle.

  It seems there are a few image viewers with this problem including
  Ristretto but also gpicview, comix, gthumb. I'm not sure why they all
  share this issue (same library?). I'll submit the bug report here in
  hopes it gets forwarded upstream to the right place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/librsvg/+bug/1207538/+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 839157] Re: Bluetooth applet (OBEX send/browse) does not work since Natty (after bluetoothd 4.84 exactly)

[Colin Watson]

** Attachment removed: "0D5EAE0F25F0BA20.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+attachment/4920575/+files/0D5EAE0F25F0BA20.jpg

** Attachment removed: "A7435C9644AEB554.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+attachment/4994317/+files/A7435C9644AEB554.jpg

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

Title:
  Bluetooth applet (OBEX send/browse) does not work since Natty (after
  bluetoothd 4.84 exactly)

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Invalid

Bug description:
  I have Ubuntu Natty 11.04 and a Nokia N81 (Symbian S60v3.1). In Ubuntu
  10.04 (Lucid) and 10.10 (Maverick) bluetooth file transfers do work
  fast and stable on my hardware. Since Natty it stopped working all
  together!

  UPDATE 26-2-2012: everything works again if the executable
  /usr/sbin/bluetoothd (4.91 in Natty) is replaced with 4.84 or earlier.
  I verified this workaround on several machines and with the Live-CD of
  Natty. Precise alpha 2 is affected too. (see also my comment 30 below)

  The attachment shows  the output of "sudo hcidump -XYt" when browsing
  fails (bluetooth-applet - menu -  - Browse files...)

  Running " bluetooth-applet -d" in a terminal and trying to browse and send 
files shows this:
  ** Message: adding killswitch idx 1 state KILLSWITCH_STATE_UNBLOCKED
  ** Message: adding killswitch idx 4 state KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitch 4 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
  ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 
111b--1000-8000-00805f9b34fb (0x111b)
  ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 
5005--1000-8000-0002ee01 (0x5005)
  ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 
5601--1000-8000-0002ee01 (0x5601)
  ** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitch 4 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
  ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 
111b--1000-8000-00805f9b34fb (0x111b)
  ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 
5005--1000-8000-0002ee01 (0x5005)
  ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 
5601--1000-8000-0002ee01 (0x5601)

  And I saw interesting lines in /var/log/auth.log:
  oliverhp dbus-daemon: [system] Rejected send message, 2 matched rules; 
type="method_return", sender=":1.99" (uid=0 pid=3356 comm="/usr/sbin/bluetoothd 
--udev ") interface="(unset)" member="(unset)" error name="(unset)" 
requested_reply=0 destination=":1.139" (uid=1000 pid=3768 
comm="bluetooth-applet -d "))

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: bluez 4.91-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic i686
  Architecture: i386
  Date: Fri Sep  2 00:10:38 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
  MachineType: Hewlett-Packard HP Compaq nx8220 (PY517EA#ABD)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   LANGUAGE=de_CH:en
   PATH=(custom, user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=a4380962-8df8-486d-a8e3-2232227f97aa ro nosplash elevator=deadline
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DTV Ver. F.18
  dmi.board.name: 0934
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 43.1D
  dmi.chassis.asset.tag: oliverhp
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DTVVer.F.18:bd07/24/2009:svnHewlett-Packard:pnHPCompaqnx8220(PY517EA#ABD):pvrF.18:rvnHewlett-Packard:rn0934:rvrKBCVersion43.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx8220 (PY517EA#ABD)
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 00:16:41:7C:AC:64  ACL MTU: 377:10  SCO MTU: 16:0
    UP RUNNING PSCAN ISCAN
    RX bytes:11936 acl:127 sco:0 events:287 errors:0
    TX bytes:3254 acl:110 sco:0 commands:102 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+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 1735134] Re: ModemManager uses a wrong plugin for Dell DW5818/5819

[Robert Liu]

[hide the comment #12, update the DEP-3 headers inside the patch]

Hi @Łukasz
the comments were addressed. and re-upload the debdiff.
Thanks.


** Patch added: "gobi-set-dell-modules-as-forbidden-devices.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5022553/+files/gobi-set-dell-modules-as-forbidden-devices.debdiff

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

Title:
  ModemManager uses a wrong plugin for Dell DW5818/5819

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  * Dell Wireless DW5818/5819 modems showed an incorrect signal strength
  and were using a ttyUSB* port for data connections instead of the MBIM
  device (which provides better performance).

  Since linux-4.4.0-98, the kernel additionally loads gcserial driver
  for Dell Wireless DW5818/5819. The reason behind it is to support
  firmware switching and upgrading. However, the change makes
  ModemManager use Gobi plugin for this two modules. With Gobi plugin,
  the modules could establish data links, but it failed to retrieve the
  signal state. And it caused the mmcli and nm-applet giving wrong
  signal strength. The modules support the MBIM protocol, so
  ModemManager should use Dell plugin for these two modules.

  I have worked out a patch to forbid these two modules in Gobi plugin,
  and it does work well.

  [Test Case]

  Current MM:
  * Create connection with 
  $ nmcli c add type gsm ifname ttyUSB2 con-name gsmconn apn 
  * Without the patched package, mmcli shows, with an active connection (see 
comment #2):
  primary port: 'ttyUSB2'
  signal quality: '0' (recent)

  Patched MM:
  * Create connection with 
  $ nmcli c add type gsm ifname cdc-wdm0 con-name gsmconn apn 
  * With the patched package, mmcli shows, with an active connection (see 
comment #7):
  primary port: 'cdc-wdm0'
  signal quality: '38' (cached)

  [Regression Potential]

  The patch simply adds the Sierra modems VID/PIDs to the list of
  forbidden ids in the Gobi plugin, so the possibility of a regression
  is very small: only products with said VID/PID will be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+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 1723198] Re: package ca-certificates 20170717~16.04.1 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

** Changed in: ca-certificates (Ubuntu)
   Importance: Undecided => Critical

** Package changed: ca-certificates (Ubuntu) => dpkg (Ubuntu)

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

Title:
  package ca-certificates 20170717~16.04.1 failed to install/upgrade:
  triggers looping, abandoned

Status in dpkg package in Ubuntu:
  Confirmed

Bug description:
  Test Case:
  1. Install Ubuntu server 14.04.5 + all the updates
  2. Install ca-certificates-java and man-db
  3. Reboot
  4. Upgrade to 16.04 LTS with do-release-upgrade and proceed with the upgrade

  Actual Result
  Upgrade fails with
  Removing ca-certificates-java (20130815ubuntu1) ...
  Removing openjdk-7-jre-headless:amd64 (7u151-2.6.11-2ubuntu0.14.04.1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
man-db -> ca-certificates
   packages' pending triggers which are or may be unresolvable:
ca-certificates: update-ca-certificates
man-db: /usr/share/man
  dpkg: error processing package ca-certificates (--remove):
   triggers looping, abandoned



  
  I have no further information to give at this time except to say that there 
were several errors during the upgrade process from 14.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20170717~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Oct 12 17:52:19 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2013-11-16 (1425 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-10-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1723198/+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 1709989] Re: No audio jack output on Lenovo Thinkpad T470s docking station. Maybe related to (Bug 893611)?

[Viser]

The same for Thinkpad t470

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

Title:
  No audio jack output on Lenovo Thinkpad T470s docking station. Maybe
  related to (Bug 893611)?

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I guess this T470s model needs to be added to the driver according to the 
comment on
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/893611/comments/12

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nyga   1758 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 10 21:39:17 2017
  InstallationDate: Installed on 2017-08-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET25W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HGS0A600
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HGS0A600:pvrThinkPadT470s:rvnLENOVO:rn20HGS0A600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HGS0A600
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-08-10T21:15:25.735875

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1709989/+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 1738155] Re: Calling reboot or poweroff on a node-red snap is fail

[zhangyang]

Note:
In the node-red snap to run "poweroff" is meaning:
I post a flow into web(node-red client) to run "poweroff" command, but it is no 
longer effective.

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

Title:
  Calling reboot or poweroff on a node-red snap is fail

Status in apparmor package in Ubuntu:
  New

Bug description:
  OS:Ubuntu 16.04.3-amd64

  when I run command "reboot" or "poweroff" in the node-red snap.It is
  no longer effective.

  my snapcraft.yaml:

  name: nodered
  version: 1.00
  summary: A visual tool for wiring the Internet of Things
  description: Node-RED is a tool for wiring together hardware devices, APIs 
and online services in new and interesting ways.
  confinement: strict
  grade: stable

  apps:
red:
  daemon: simple
  command: bin/launch
  plugs:
- network-bind
- network
- network-observe

  parts:
red:
  plugin: nodejs
  node-packages:
- node-red
- node-red-dashboard
  filesets:
othermodules: [ -lib/node_modules/npm ]
  stage: [ $othermodules ]
settings:
  plugin: dump
  source: settings
  filesets:
settings:
  - .
  organize:
start.sh : bin/launch
  snap:
- .
  filesets:
all: [ . ]
  
  when I run "poweroff" in the node-red snap, the syslog will show:

  Dec 14 04:07:34 zy-PR-VR4 bor.red[1905]: 14 Dec 04:07:34 - [info] 
[exec:command]  poweroff
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.060923] kauditd_printk_skb: 25 
callbacks suppressed
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.060927] audit: type=1400 
audit(1513242454.177:329): apparmor="ALLOWED" operation="exec" 
profile="snap.bor.red" name="/bin/systemctl" pid=2453 comm="sh" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0 
target="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061474] audit: type=1400 
audit(1513242454.177:330): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061480] audit: type=1400 
audit(1513242454.181:331): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061483] audit: type=1400 
audit(1513242454.181:332): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061487] audit: type=1400 
audit(1513242454.181:333): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061489] audit: type=1400 
audit(1513242454.181:334): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061493] audit: type=1400 
audit(1513242454.181:335): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061496] audit: type=1400 
audit(1513242454.181:336): apparmor="ALLOWED" operation="file_mmap" 
profile="snap.bor.red//null-/bin/systemctl" name="/bin/systemctl" pid=2453 
comm="poweroff" requested_mask="rm" denied_mask="rm" fsuid=0 ouid=0

  it looks the command is runing in the ubuntu 16.04.3, but it does not 
effective.
  ---
  when I run "dmesg" in the node-red snap, the syslog will show:

  bor.red[1905]: 14 Dec 04:10:02 - [info] [exec:command]  dmesg
  Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739205] kauditd_printk_skb: 90 
callbacks suppressed
  Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739207] audit: type=1400 
audit(1513242602.837:463): apparmor="ALLOWED" operation="exec" 
profile="snap.bor.red" name="/bin/dmesg" pid=2552 comm="sh" 

[Touch-packages] [Bug 1738155] [NEW] Calling reboot or poweroff on a node-red snap is fail

[zhangyang]

Public bug reported:

OS:Ubuntu 16.04.3-amd64

when I run command "reboot" or "poweroff" in the node-red snap.It is no
longer effective.

my snapcraft.yaml:

name: nodered
version: 1.00
summary: A visual tool for wiring the Internet of Things
description: Node-RED is a tool for wiring together hardware devices, APIs and 
online services in new and interesting ways.
confinement: strict
grade: stable

apps:
  red:
daemon: simple
command: bin/launch
plugs:
  - network-bind
  - network
  - network-observe

parts:
  red:
plugin: nodejs
node-packages:
  - node-red
  - node-red-dashboard
filesets:
  othermodules: [ -lib/node_modules/npm ]
stage: [ $othermodules ]
  settings:
plugin: dump
source: settings
filesets:
  settings:
- .
organize:
  start.sh : bin/launch
snap:
  - .
filesets:
  all: [ . ]

when I run "poweroff" in the node-red snap, the syslog will show:

Dec 14 04:07:34 zy-PR-VR4 bor.red[1905]: 14 Dec 04:07:34 - [info] 
[exec:command]  poweroff
Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.060923] kauditd_printk_skb: 25 
callbacks suppressed
Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.060927] audit: type=1400 
audit(1513242454.177:329): apparmor="ALLOWED" operation="exec" 
profile="snap.bor.red" name="/bin/systemctl" pid=2453 comm="sh" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0 
target="snap.bor.red//null-/bin/systemctl"
Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061474] audit: type=1400 
audit(1513242454.177:330): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061480] audit: type=1400 
audit(1513242454.181:331): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061483] audit: type=1400 
audit(1513242454.181:332): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061487] audit: type=1400 
audit(1513242454.181:333): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061489] audit: type=1400 
audit(1513242454.181:334): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061493] audit: type=1400 
audit(1513242454.181:335): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061496] audit: type=1400 
audit(1513242454.181:336): apparmor="ALLOWED" operation="file_mmap" 
profile="snap.bor.red//null-/bin/systemctl" name="/bin/systemctl" pid=2453 
comm="poweroff" requested_mask="rm" denied_mask="rm" fsuid=0 ouid=0

it looks the command is runing in the ubuntu 16.04.3, but it does not effective.
---
when I run "dmesg" in the node-red snap, the syslog will show:

bor.red[1905]: 14 Dec 04:10:02 - [info] [exec:command]  dmesg
Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739205] kauditd_printk_skb: 90 
callbacks suppressed
Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739207] audit: type=1400 
audit(1513242602.837:463): apparmor="ALLOWED" operation="exec" 
profile="snap.bor.red" name="/bin/dmesg" pid=2552 comm="sh" requested_mask="x" 
denied_mask="x" fsuid=0 ouid=0 target="snap.bor.red//null-/bin/dmesg"
Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739385] audit: type=1400 
audit(1513242602.837:464): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/dmesg" pid=2552 comm="dmesg" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none
Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739387] audit: type=1400 
audit(1513242602.837:465): apparmor="ALLOWED" operation="file_inherit" 

[Touch-packages] [Bug 1738058] Re: vlan usage requires an intermediate step

[Dimitri John Ledkov]

That sounds like a bug.

I have only previously used vlans on top of bonds.

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  vlan usage requires an intermediate step

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  If I try to apply vlans directly:

  
  network:
version: 2
renderer: networkd
ethernets:
  eth0: {}
vlans:
  vlan1:
id: 1
link: eth0
addresses: [ 192.168.0.10/23 ]
  vlan10:
id: 10
link: eth0
addresses: [ 10.0.0.5/24 ]

  The vlan devices never come up, they are left in degraded state by
  networkd. If I define an address for eth0, then eth0 and all of the
  vlans will have the same address. Needless to say, this doesn't work.

  If I use an intermediary device instead, such as a bond:

  network:
version: 2
renderer: networkd
ethernets:
  eth0: {}
bonds:
  vmaster:
interfaces: [ eth0 ]
vlans:
  vlan1:
id: 1
link: vmaster
addresses: [ 192.168.0.10/23 ]
  vlan10:
id: 10
link: vmaster
addresses: [ 10.0.0.5/24 ]

  Then the vlans are correctly applied and brought up by systemd.

  I think this is either a systemd bug or a netplan bug; it's possible
  we don't generate the config quite in the way that systemd expects it
  (even though it looks straightforward enough).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1738058/+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 1738039] Re: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239

[Jaap]

I had the same "segmentation fault" error after (manually) running "apt-
get upgrade":

[]
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
Setting up libxml2:amd64 (2.9.3+dfsg1-1ubuntu0.5) ...
Setting up python3-problem-report (2.20.1-0ubuntu2.14) ...
Setting up python3-apport (2.20.1-0ubuntu2.14) ...
Setting up apport (2.20.1-0ubuntu2.14) ...
Segmentation fault
dpkg: error processing package apport (--configure):
 subprocess installed post-installation script returned error exit status 239
dpkg: dependency problems prevent configuration of apport-gtk:
 apport-gtk depends on apport (>= 0.41); however:
  Package apport is not configured yet.

dpkg: error processing package apport-gtk (--configure):
 dependency problems - leaving unconfigured
Setting up libnm-util2:amd64 (1.2.6-0ubuntu0.16.04.2) ...
Setting up libnm-glib-vpn1:amd64 (1.2.6-0ubuntu0.16.04.2) ...
No apport report written because the error message indicates its a followup 
error from a previous failure.

  Setting up libnm-glib4:amd64 (1.2.6-0ubuntu0.16.04.2) 
...
Setting up libnm0:amd64 (1.2.6-0ubuntu0.16.04.2) ...
Setting up libpulse0:amd64 (1:8.0-0ubuntu3.7) ...
Setting up libpulsedsp:amd64 (1:8.0-0ubuntu3.7) ...
Setting up pulseaudio-utils (1:8.0-0ubuntu3.7) ...
Setting up pulseaudio (1:8.0-0ubuntu3.7) ...
Setting up pulseaudio-module-x11 (1:8.0-0ubuntu3.7) ...
[]


Ubuntu 16.04.3 LTS
Linux TR 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  package apport 2.20.1-0ubuntu2.14 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 239

Status in apport package in Ubuntu:
  New

Bug description:
  The normal update failed to finish properly.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.14
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Uname: Linux 4.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CrashReports:
   640:0:116:100989:2017-12-10 09:09:24.099369764 +0200:2017-12-10 
09:09:25.099369764 +0200:/var/crash/_usr_bin_atop.0.crash
   640:1000:116:5469774:2017-12-07 18:53:05.238692741 +0200:2017-12-09 
09:04:37.246543187 +0200:/var/crash/_usr_bin_compiz.1000.crash
   644:0:116:0:2017-12-10 09:09:25.703367143 +0200:2017-12-10 
09:09:25.703367143 +0200:/var/crash/_usr_bin_atop.0.upload
   600:0:116:84324:2017-12-10 09:10:03.171132802 +0200:2017-12-10 
09:10:04.171132802 +0200:/var/crash/apport.0.crash
   600:109:116:0:2017-12-10 09:09:26.815362361 +0200:2017-12-10 
09:09:26.815362361 +0200:/var/crash/_usr_bin_atop.0.uploaded
  Date: Sun Dec 10 09:10:04 2017
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.14
   Setting up apport (2.20.1-0ubuntu2.14) ...
   Segmentation fault
   dpkg: error processing package apport (--configure):
subprocess installed post-installation script returned error exit status 239
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 239
  InstallationDate: Installed on 2016-04-23 (599 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 239
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738039/+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 1725333] Re: do-release-upgrade broke WSL

[Launchpad Bug Tracker]

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

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

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

Title:
  do-release-upgrade broke WSL

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1725333/+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 1709989] Re: No audio jack output on Lenovo Thinkpad T470s docking station. Maybe related to (Bug 893611)?

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  No audio jack output on Lenovo Thinkpad T470s docking station. Maybe
  related to (Bug 893611)?

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I guess this T470s model needs to be added to the driver according to the 
comment on
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/893611/comments/12

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nyga   1758 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 10 21:39:17 2017
  InstallationDate: Installed on 2017-08-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET25W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HGS0A600
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HGS0A600:pvrThinkPadT470s:rvnLENOVO:rn20HGS0A600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HGS0A600
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-08-10T21:15:25.735875

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1709989/+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 1738144] [NEW] Monitor locked to low-res when using EFI/Secure Boot on Coffee Lake

[jimav]

Public bug reported:

Booting with EFI, as opposed to legacy BIOS booting, somehow prevents
detecting the resolutions supported by a VESA-compliant monitor; instead
a single low resolution mode is used, and no other choices are available
in the "Displays" setting dialog.

At least that's what happens using built-in Intel graphics on a i7-8700K
/ Z370 (Coffee Lake), with a 1920x1200 DVI monitor.

This effectively prevents enabling Secure Boot with Ubuntu on this
platform.

I don't know if older hardware has the same problem (this is the first
UEFI-capable system I've owned)

The problem is visible when booting from the installer DVD in "try
Ubuntu" mode (the install DVDs are set up to boot either way).   If you
boot in EFI mode, the desktop comes up at 1024x768.  But if you boot in
legacy BIOS mode, it comes up normally (1920x1200 in my case).  Ditto
for installed systems.

STEPS TO REPRODUCE:

1. Go out and buy a new Coffee Lake system with ASUS Z370-A PRIME motherboard 
and i7-8700K cpu
2. Enable Secure Boot in the "bios" (disable legacy booting)
3. Boot the 17.10 or 16.04 Ubuntu Desktop DVD in "try Ubuntu" mode

RESULTS: Resolution abnormally low, and can not be changed

4. Turn off Secure Boot and enable legacy or "Compatibility" support (CSM in 
ASUS-speak).
5. Boot the same Desktop installer DVD

RESULTS: Normal resolution

Installing in legacy BIOS mode is a work-around, but preventing use of
Secure Boot is a security problem (the system is potentially vulnerable
to bootstrap malware)

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

** Information type changed from Private Security to Public

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

Title:
  Monitor locked to low-res when using EFI/Secure Boot on Coffee Lake

Status in upstart package in Ubuntu:
  New

Bug description:
  Booting with EFI, as opposed to legacy BIOS booting, somehow prevents
  detecting the resolutions supported by a VESA-compliant monitor;
  instead a single low resolution mode is used, and no other choices are
  available in the "Displays" setting dialog.

  At least that's what happens using built-in Intel graphics on a
  i7-8700K / Z370 (Coffee Lake), with a 1920x1200 DVI monitor.

  This effectively prevents enabling Secure Boot with Ubuntu on this
  platform.

  I don't know if older hardware has the same problem (this is the first
  UEFI-capable system I've owned)

  The problem is visible when booting from the installer DVD in "try
  Ubuntu" mode (the install DVDs are set up to boot either way).   If
  you boot in EFI mode, the desktop comes up at 1024x768.  But if you
  boot in legacy BIOS mode, it comes up normally (1920x1200 in my case).
  Ditto for installed systems.

  STEPS TO REPRODUCE:

  1. Go out and buy a new Coffee Lake system with ASUS Z370-A PRIME motherboard 
and i7-8700K cpu
  2. Enable Secure Boot in the "bios" (disable legacy booting)
  3. Boot the 17.10 or 16.04 Ubuntu Desktop DVD in "try Ubuntu" mode

  RESULTS: Resolution abnormally low, and can not be changed

  4. Turn off Secure Boot and enable legacy or "Compatibility" support (CSM in 
ASUS-speak).
  5. Boot the same Desktop installer DVD

  RESULTS: Normal resolution

  Installing in legacy BIOS mode is a work-around, but preventing use of
  Secure Boot is a security problem (the system is potentially
  vulnerable to bootstrap malware)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1738144/+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 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

[Jb]

I have a work around for Lubuntu Alternate installer 64 Bit fix (same
console installer as Ubuntu Server).

Might work on server.

https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1736309

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  New
Status in busybox package in Ubuntu:
  Confirmed

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?  ?  ?
?

[Touch-packages] [Bug 1733557] Re: Login screen showing Authentication Failed Switch to greeter...

[Andrew Neeson]

My issues began shortly after upgrading from 16.10 -> 17.10.  Most of my
issues related to graphical components so perhaps it was related to the
switch to Wayland?

...as for a fix - I ended up reformatting my machine with a fresh 17.10.
Haven't seen any of the issues since.


See: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1733318
for a list of other issues to happen at the same time.

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

Title:
  Login screen showing Authentication Failed Switch to greeter...

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I lock my machine, the login screen shows my current user with
  the message: "Authentication Failed"

  ..and in the position when the password normally exists, the option
  "Switch to greeter..."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 21 10:28:47 2017
  InstallationDate: Installed on 2017-04-17 (217 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1733557/+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 1735134] Re: ModemManager uses a wrong plugin for Dell DW5818/5819

[Robert Liu]

Hi @Łukasz
the comments were addressed. and re-upload the debdiff.
Thanks.

** Patch added: "gobi-set-dell-modules-as-forbidden-devices.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5022490/+files/gobi-set-dell-modules-as-forbidden-devices.debdiff

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

Title:
  ModemManager uses a wrong plugin for Dell DW5818/5819

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  * Dell Wireless DW5818/5819 modems showed an incorrect signal strength
  and were using a ttyUSB* port for data connections instead of the MBIM
  device (which provides better performance).

  Since linux-4.4.0-98, the kernel additionally loads gcserial driver
  for Dell Wireless DW5818/5819. The reason behind it is to support
  firmware switching and upgrading. However, the change makes
  ModemManager use Gobi plugin for this two modules. With Gobi plugin,
  the modules could establish data links, but it failed to retrieve the
  signal state. And it caused the mmcli and nm-applet giving wrong
  signal strength. The modules support the MBIM protocol, so
  ModemManager should use Dell plugin for these two modules.

  I have worked out a patch to forbid these two modules in Gobi plugin,
  and it does work well.

  [Test Case]

  Current MM:
  * Create connection with 
  $ nmcli c add type gsm ifname ttyUSB2 con-name gsmconn apn 
  * Without the patched package, mmcli shows, with an active connection (see 
comment #2):
  primary port: 'ttyUSB2'
  signal quality: '0' (recent)

  Patched MM:
  * Create connection with 
  $ nmcli c add type gsm ifname cdc-wdm0 con-name gsmconn apn 
  * With the patched package, mmcli shows, with an active connection (see 
comment #7):
  primary port: 'cdc-wdm0'
  signal quality: '38' (cached)

  [Regression Potential]

  The patch simply adds the Sierra modems VID/PIDs to the list of
  forbidden ids in the Gobi plugin, so the possibility of a regression
  is very small: only products with said VID/PID will be affected.

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