[Touch-packages] [Bug 1735356] [NEW] package libperl5.22:amd64 5.22.1-9 [modified: usr/bin/perl5.22-x86_64-linux-gnu usr/lib/x86_64-linux-gnu/libperl.so.5.22.1 usr/lib/x86_64-linux-gnu/perl/5.22.1/COR

[farnam homayounfar]

Public bug reported:

when installing google chrome

ProblemType: Package
DistroRelease: Ubuntu 16.04
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Nov 30 11:49:10 2017
ErrorMessage: package libperl5.22:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-11-30 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: perl
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libperl5.22:amd64 5.22.1-9 [modified: usr/bin/perl5.22-x86_64
  -linux-gnu usr/lib/x86_64-linux-gnu/libperl.so.5.22.1 usr/lib/x86_64
  -linux-gnu/perl/5.22.1/CORE/config.h usr/lib/x86_64-linux-
  gnu/perl/5.22.1/CORE/patchlevel-debian.h usr/lib/x86_64-linux-
  gnu/perl/5.22.1/Config_heavy.pl usr/lib/x86_64-linux-
  gnu/perl/5.22.1/_h2ph_pre.ph usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/B/B.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Compress/Raw/Bzip2/Bzip2.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Compress/Raw/Zlib/Zlib.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Cwd/Cwd.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/DB_File/DB_File.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Data/Dumper/Dumper.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Devel/PPPort/PPPort.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Devel/Peek/Peek.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Digest/MD5/MD5.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Digest/SHA/SHA.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/Byte/Byte.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/CN/CN.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/EBCDIC/EBCDIC.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/Encode.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/JP/JP.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/KR/KR.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/Symbol/Symbol.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/TW/TW.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/Unicode/Unicode.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Fcntl/Fcntl.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/File/DosGlob/DosGlob.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/File/Glob/Glob.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Filter/Util/Call/Call.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/GDBM_File/GDBM_File.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Hash/Util/FieldHash/FieldHash.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/Hash/Util/Util.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/I18N/Langinfo/Langinfo.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/IO/IO.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/IPC/SysV/SysV.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/List/Util/Util.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/MIME/Base64/Base64.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Math/BigInt/FastCalc/FastCalc.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/NDBM_File/NDBM_File.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/ODBM_File/ODBM_File.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/Opcode/Opcode.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/POSIX/POSIX.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/PerlIO/encoding/encoding.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/PerlIO/mmap/mmap.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/PerlIO/scalar/scalar.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/PerlIO/via/via.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/SDBM_File/SDBM_File.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Socket/Socket.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Storable/Storable.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Sys/Hostname/Hostname.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Sys/Syslog/Syslog.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Tie/Hash/NamedCapture/NamedCapture.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/Time/HiRes/HiRes.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/Time/Piece/Piece.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/Unicode/Collate/Collate.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/arybase/arybase.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/attributes/attributes.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/mro/mro.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/re/re.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/threads/shared/shared.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/threads/threads.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/bits/sig

[Touch-packages] [Bug 1735356] Re: package libperl5.22:amd64 5.22.1-9 [modified: usr/bin/perl5.22-x86_64-linux-gnu usr/lib/x86_64-linux-gnu/libperl.so.5.22.1 usr/lib/x86_64-linux-gnu/perl/5.22.1/CORE/

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libperl5.22:amd64 5.22.1-9 [modified: usr/bin/perl5.22-x86_64
  -linux-gnu usr/lib/x86_64-linux-gnu/libperl.so.5.22.1 usr/lib/x86_64
  -linux-gnu/perl/5.22.1/CORE/config.h usr/lib/x86_64-linux-
  gnu/perl/5.22.1/CORE/patchlevel-debian.h usr/lib/x86_64-linux-
  gnu/perl/5.22.1/Config_heavy.pl usr/lib/x86_64-linux-
  gnu/perl/5.22.1/_h2ph_pre.ph usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/B/B.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Compress/Raw/Bzip2/Bzip2.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Compress/Raw/Zlib/Zlib.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Cwd/Cwd.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/DB_File/DB_File.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Data/Dumper/Dumper.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Devel/PPPort/PPPort.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Devel/Peek/Peek.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Digest/MD5/MD5.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Digest/SHA/SHA.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/Byte/Byte.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/CN/CN.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/EBCDIC/EBCDIC.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/Encode.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/JP/JP.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/KR/KR.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/Symbol/Symbol.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/TW/TW.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Encode/Unicode/Unicode.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Fcntl/Fcntl.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/File/DosGlob/DosGlob.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/File/Glob/Glob.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Filter/Util/Call/Call.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/GDBM_File/GDBM_File.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Hash/Util/FieldHash/FieldHash.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/Hash/Util/Util.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/I18N/Langinfo/Langinfo.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/IO/IO.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/IPC/SysV/SysV.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/List/Util/Util.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/MIME/Base64/Base64.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Math/BigInt/FastCalc/FastCalc.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/NDBM_File/NDBM_File.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/ODBM_File/ODBM_File.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/Opcode/Opcode.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/POSIX/POSIX.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/PerlIO/encoding/encoding.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/PerlIO/mmap/mmap.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/PerlIO/scalar/scalar.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/PerlIO/via/via.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/SDBM_File/SDBM_File.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Socket/Socket.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Storable/Storable.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Sys/Hostname/Hostname.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Sys/Syslog/Syslog.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/Tie/Hash/NamedCapture/NamedCapture.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/Time/HiRes/HiRes.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/Time/Piece/Piece.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/Unicode/Collate/Collate.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/arybase/arybase.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/attributes/attributes.so
  usr/lib/x86_64-linux-gnu/perl/5.22.1/auto/mro/mro.so usr/lib/x86_64
  -linux-gnu/perl/5.22.1/auto/re/re.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/threads/shared/shared.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/auto/threads/threads.so usr/lib/x86_64-linux-
  gnu/perl/5.22.1/bits/siginfo.ph usr/lib/x86_64-linux-
  gnu/perl/5.22.1/bits/sockaddr.ph usr/lib/x86_64-linux-
  gnu/perl/5.22.1/bits/socket.ph usr/lib/x86_64-linux-
  gnu/perl/5.22.1/bits/timex.ph usr/lib/x86_64-linux-
  gnu/perl/5.22.1/bits/typesizes.ph usr/lib/x86_64-linux-
  gnu/perl/5.22.1/features.ph usr/lib/x86_64-linux-
  gnu/perl/5.22.1/gnu/stubs-64.ph usr/lib/x86_64-linux-
  gnu/perl/5.22.1/signal.ph usr/lib/x86_64-linux-gnu/perl/5.22.1/stdc-
  predef.ph usr/lib/x86_64-linux-gnu/perl/5.22.1/sys/cdefs.ph
  usr/lib/x86_64-linux-gnu/perl/debian-config-
  data-5.22.1/config.sh.debug.gz usr/lib/x86_64-linux-gnu/perl/debian-
  config-data-5.22.1/config.sh.shared.gz usr/lib/x86_64-linux-gnu/perl
  /debian-config-data-5.22.1/config.sh.static.gz
  usr/share/doc/libperl5.22/changel

[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added

[Kleber Sacilotto de Souza]

Yes, this has already been fixed in Bionic. The fix was applied upstream
on systemd v235, so it's shipped with systemd=235-3ubuntu2.

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

Title:
  systemd-rfkill service times out when a new rfkill device is added

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  The following issue was observed while running network-
  manager=1.8.4-1ubuntu3 autopkgtest on Artful with
  systemd=234-2ubuntu12.1:

  ---
  Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start 
operation timed out. Terminating.
  Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill 
Switch Status.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered 
failed state.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with 
result 'timeout'.
  ---

  This happens after the testcase inserts the fake-rfkill module (a
  module shipped with network-manager tests that registers a new fake
  device with the rfkill subsystem).

  On Artful, it causes the network-manager autopkgtest killswitches-no-
  urfkill to fail (see bug 1733321).

  
  [Fix]

  The issue is fixed by the following systemd upstream patches:

  ---
  
https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

  commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
  Author: S. Fan 
  Date:   Mon Jul 31 05:10:10 2017 -0500

  rfkill: fix erroneous behavior when polling the udev monitor
  (#6489)

  Comparing udev_device_get_sysname(device) and sysname will always return
  true. We need to check the device received from udev monitor instead.

  Also, fd_wait_for_event() sometimes never exits. Better set a timeout
  here.
  ---

  ---
  
https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac

  commit c7f6ca9379279affa8f22d15fa13063491f86a49
  Author: Xiang Fan 
  Date:   Wed Aug 9 05:51:53 2017 -0500

  rfkill: fix typo (#6574)
  ---

  With the fixes, the output from systemd-rfkill is:

  ---
  Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev 
monitor.
  Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch 
Status.
  ---

  The patches are needed to fix the ADT tests observed with Artful tests on 
ppc64el architecture:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  Regression potential is minimal, since the fix has been applied some
  months ago on upstream github repo and it's being shipped with systemd
  on Bionic (systemd=235-3ubuntu2)

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

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

[Touch-packages] [Bug 1735373] [NEW] package apport 2.20.7-0ubuntu3.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Nitin Sareen]

Public bug reported:

Cannot upgrade anything in my system.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportLog:
 
ApportVersion: 2.20.7-0ubuntu3.1
AptOrdering:
 python3-apport:amd64: Install
 apport:amd64: Install
 python-six:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Nov 30 15:01:08 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-04-22 (222 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: apport
Title: package apport 2.20.7-0ubuntu3.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package apport 2.20.7-0ubuntu3.1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  Cannot upgrade anything in my system.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  AptOrdering:
   python3-apport:amd64: Install
   apport:amd64: Install
   python-six:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Nov 30 15:01:08 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-04-22 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: apport
  Title: package apport 2.20.7-0ubuntu3.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1153671] Re: Port to python3-launchpadlib

[Matthias Klose]

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Ubuntu Foundations Bugs (foundations-bugs)

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

Title:
  Port to python3-launchpadlib

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Apport-cli depends on python3-launchpadlib for some actions, but it is
  not installable (currently). For example,

  apport-cli -u 542452
  ERROR: The launchpadlib Python module is not installed. This functionality is 
not available.

  The current candidates for installation on raring only include python-
  launchpadlib (which is python2 based).  I believe this bug is
  relevant:

  https://bugs.launchpad.net/launchpadlib/+bug/1060734

  I'm  filing this against apport in the event raring is shipped without
  a python3-launchpadlib package. I would recommend updating the error
  to make what is needing to be installed more clear. IE,

  ERROR: The launchpadlib Python3 module is not installed
  (python3-launchpadlib). This functionality is not available.

  Also consider adding the library as a suggested dependency.  In
  addition, should the package not land, further steps may be required.

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

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

[Touch-packages] [Bug 1153671] Re: Port to python3-launchpadlib

[Martin Pitt]

Once you do this, these fallbacks should be cleaned up:

http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L30
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L137

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

Title:
  Port to python3-launchpadlib

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Apport-cli depends on python3-launchpadlib for some actions, but it is
  not installable (currently). For example,

  apport-cli -u 542452
  ERROR: The launchpadlib Python module is not installed. This functionality is 
not available.

  The current candidates for installation on raring only include python-
  launchpadlib (which is python2 based).  I believe this bug is
  relevant:

  https://bugs.launchpad.net/launchpadlib/+bug/1060734

  I'm  filing this against apport in the event raring is shipped without
  a python3-launchpadlib package. I would recommend updating the error
  to make what is needing to be installed more clear. IE,

  ERROR: The launchpadlib Python3 module is not installed
  (python3-launchpadlib). This functionality is not available.

  Also consider adding the library as a suggested dependency.  In
  addition, should the package not land, further steps may be required.

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

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

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Kleber Sacilotto de Souza]

Although we haven't seen the failure in Bionic yet, it might be a good
idea to apply the fix on Bionic as well, which as of now has the same
package version as Artful.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in linux package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in network-manager source package in Artful:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

[Matthias Klose]

** Tags added: py2-demotion py2-removal

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

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

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

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  New
Status in tdb package in Ubuntu:
  New
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1732222] [NEW] Language support not installed matching locale

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When Ubuntu is installed with UK locale settings during setup, all of
the language support is not installed and some applications e.g.
LibreOffice display with non-UK English. The extra language support is
prompted to be installed *the first time* the user accesses the language
options (see screenshot attached).

When this language support is installed, these applications then
(correctly) display menus etc in UK English.

Ubuntu setup appears to not install the matching locale languages.

** Affects: language-pack-en (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment language support
-- 
Language support not installed matching locale
https://bugs.launchpad.net/bugs/173
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to language-pack-en in Ubuntu.

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

[Touch-packages] [Bug 1735032] Re: rebase iproute2 to newer version

[ChristianEhrhardt]

Interesting I came by the same conclusion just today.
I'll take a look at it.

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

Title:
  rebase iproute2 to newer version

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

Bug description:
  Ubuntu's iproute2 version [1] is still many kernel versions behind.
  It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

  iproute2 is developed alongside the kernel, so new kernel features
  will also get updates to iproute2 whenever they change related code.
  Meaning, these features cannot be used out of the box if the actual
  shipped iproute2 version here is not on par with the kernel version
  (the release tags have 1:1 mapping with kernel releases) [2].

  Please consider updating iproute2 package, and please also consider
  updating it regularly along with officially shipped kernels in Ubuntu,
  so that all the added networking features can be used there without
  forcing users to do a manual compilation of iproute2.

  Thanks,
  Daniel

[1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

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

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

[Touch-packages] [Bug 1732222] Re: Language support not installed matching locale

[Paul White]

** Package changed: ubuntu => language-pack-en (Ubuntu)

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

Title:
  Language support not installed matching locale

Status in language-pack-en package in Ubuntu:
  New

Bug description:
  When Ubuntu is installed with UK locale settings during setup, all of
  the language support is not installed and some applications e.g.
  LibreOffice display with non-UK English. The extra language support is
  prompted to be installed *the first time* the user accesses the
  language options (see screenshot attached).

  When this language support is installed, these applications then
  (correctly) display menus etc in UK English.

  Ubuntu setup appears to not install the matching locale languages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/173/+subscriptions

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

[Touch-packages] [Bug 1735032] Re: rebase iproute2 to newer version

[ChristianEhrhardt]

** Changed in: iproute2 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  rebase iproute2 to newer version

Status in iproute2 package in Ubuntu:
  Triaged
Status in iproute2 package in Debian:
  New

Bug description:
  Ubuntu's iproute2 version [1] is still many kernel versions behind.
  It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

  iproute2 is developed alongside the kernel, so new kernel features
  will also get updates to iproute2 whenever they change related code.
  Meaning, these features cannot be used out of the box if the actual
  shipped iproute2 version here is not on par with the kernel version
  (the release tags have 1:1 mapping with kernel releases) [2].

  Please consider updating iproute2 package, and please also consider
  updating it regularly along with officially shipped kernels in Ubuntu,
  so that all the added networking features can be used there without
  forcing users to do a manual compilation of iproute2.

  Thanks,
  Daniel

[1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

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

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

[Touch-packages] [Bug 1726730] Re: IPRoute pkg is in different version than kernel

[ChristianEhrhardt]

I'll try to update it for Bionic to closer match the upcoming kernel number.
That would at least make the upcoming LTS somewhat in sync with iproute.

But I'm not sure how reasonable and doable it is to doa bump e.g. 4.9->4.13 in 
Artful.
We can think about that after the former action.
I'm adding tasks for the older releases so that a close for Bionic won't 
totally close the bug.


** Also affects: iproute2 (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: iproute2 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: iproute2 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: iproute2 (Ubuntu Bionic)
   Status: New => Triaged

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

Title:
  IPRoute pkg is in different version than kernel

Status in iproute2 package in Ubuntu:
  Triaged
Status in iproute2 source package in Zesty:
  New
Status in iproute2 source package in Artful:
  New
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  Hello,

  At the moment there is a problem with Iproute package in Zesty and
  artful.

  In Zesty the kernel version is 4.10.0, and the Iproute package is 4.9.0. 
  In Artful the kernel version is 4.13, and the Iproute is 4.9.0 too. 

  This is causing some problems in the BPF/XDP setup, some code is in
  the kernel but doesn't have the same version in Iproute, so it'll
  fail.

  Found the problem using cilium project
   and the problem was
  validated by Daniel Borkmann (iproute mantainer)

  I didn't find any related bug related to updating. If you need help to
  test/update, I can help you.

  Regards and many thanks.

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

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

[Touch-packages] [Bug 1220782] Re: ip xfrm state add crashes when supplied an algo

[ChristianEhrhardt]

Hi,
I come by cleaning up old issues.
So first of all I beg your pardon that nobody seems to ever have looked at that.
Never the less I have to ask you if this would still happen on newer still 
supported releases?

If so, it would be great if you could add the steps to reproduce.
Essentially convert the sentence "when supplying enc, auth, comp, auth-trunc or 
aead and the following key argumentis given as a string" into a series of 
commands to ensure one does the same when trying to reproduce.

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

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

Title:
  ip xfrm state add crashes when supplied an algo

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  This is valid for iproute2-ss17 which is default on Ubuntu 12.04
  (LTS).

  The crash appends when supplying enc, auth, comp, auth-trunc or aead and the 
following key argumentis given as a string (as opposed to hexadecimal). When 
trying to copy the key, it generates a segfault:
  
  *** buffer overflow detected ***: /sbin/ip terminated
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x77921807]
  /lib/x86_64-linux-gnu/libc.so.6(+0x109700)[0x77920700]
  /lib/x86_64-linux-gnu/libc.so.6(+0x1089e6)[0x7791f9e6]
  /sbin/ip[0x420d84]  
  /sbin/ip(do_xfrm_state+0x7a1)[0x421951]
  /sbin/ip[0x405ad5]  
  /sbin/ip(main+0x2b4)[0x4056d4]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7783876d]
  /sbin/ip[0x405959]  
  

  
  This buffer overflow is actually preposterous since  __strncpy_chk is called 
with 0 as its last argument:
 0x00420d72:  mov0x68(%rsp),%rsi
 0x00420d77:  movslq %r12d,%rdx
 0x00420d7a:  xor%ecx,%ecx
 0x00420d7c:  mov%r9,%rdi
  => 0x00420d7f:  callq  0x404a10 <__strncpy_chk@plt>

  ("xor%ecx,%ecx" set the fourth argument to 0)

  Which is equivalent to: 
  __strncpy_chk(buf, key, len, 0);

  When obtaining the source package, the corresponding code looks like
  that (from ip/xfrm_state.c, line 113):

  static int xfrm_algo_parse(struct xfrm_algo *alg, enum xfrm_attr_type_t type,
 char *name, char *key, char *buf, int max)
  {
  int len;
  int slen = strlen(key);

  #if 0
  /* XXX: verifying both name and key is required! */
  fprintf(stderr, "warning: ALGO-NAME/ALGO-KEY will send to kernel 
promiscuously! (verifying them isn't implemented yet)\n");
  #endif

  strncpy(alg->alg_name, name, sizeof(alg->alg_name));

  if (slen > 2 && strncmp(key, "0x", 2) == 0) {
  
  } else {
  len = slen;
  if (len > 0) {
  if (len > max)
  invarg("\"ALGO-KEY\" makes buffer 
overflow\n", key);

  strncpy(buf, key, len); <- correct line which is 
faulty in the assembly
  }
  }

  alg->alg_key_len = len * 8;

  return 0;
  }

  This code is actually valid but doesn't match the assembly from the
  binary package.

  This is quite annoying since it prevents from setting keys in a string
  form, thus forcing the user to derivates itself the hexadecimal value
  for the key when trying to setup an IPsec tunnel for example.

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

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

[Touch-packages] [Bug 1371246] Re: netns ifconfig problem

[ChristianEhrhardt]

Per former comment closing the bug

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

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

Title:
  netns ifconfig problem

Status in iproute2 package in Ubuntu:
  Invalid

Bug description:
  I am using IP name space virtualization feature in Ubuntu 14.04. The simplest 
script for this is:
  #! /bin/sh
  ip netns add test
  ip link set dev eth1 netns test
  ip netns exec ip addr add 10.4.1.21/16 dev eth1
  ip netns exec test ip link set dev eth1 up

  The node has eth0 with 10.4.1.20/16 and connected eth0 to eth1 by
  external cable.

  All had worked fine during updating Ubuntu 14.04 at the 14th or 15th
  of September. All is OK in Ubuntu 12.04 LTS.

  After the starting script I have a wrong result for 'sudo ip netns
  exec test ifconfig eth1' output as zero's broadcast address in test IP
  name space. Command 'sudo ip netns exec test ping 10.4.21.1' has
  failed.

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

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

[Touch-packages] [Bug 1691214] Re: Consider enabling --color by default

[ChristianEhrhardt]

Hi Jeremy,
the difference of this and the tools we already do so is a hard enable vs auto 
mode.

The cases we already have are handling --color=auto to only add color if 
running on a terminal.
Instead the --color of ip is a hard enable.

So if you e.g. do:
$ ip --color a > /tmp/foo

Or if we would set up an alias
$ ip a > /tmp/foo

Then the file would contain control chars which no on wants (and could break 
parsing/monitoring).
I checked latest upstream git of iproute and it still is that way.

So I'd assume the best would be to file a bug upstream and link it here
- what do you think Jeremy?

** Tags added: needs-upstream-report

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

Title:
  Consider enabling --color by default

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  The output of

  ip --color a

  looks a lot nicer to me than

  ip a

  
  If you look in /etc/skel/.bashrc you can see that we already enable color for 
other commands:
   alias ls='ls --color=auto'
   alias grep='grep --color=auto'
   alias fgrep='fgrep --color=auto'
   alias egrep='egrep --color=auto'

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

-- 
Mailing list: https://launchpad.net/~touch-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]

Systemd regression introduced in:
$ git describe 2d058a87ffb2d31a50422a8aebd119bbb4427244
v232-626-g2d058a8

Reverted in:
$ git describe 9e4ea9cc34fa032a47c253ddd94ac6c7afda663e
v234-72-g9e4ea9c

Thus affected releases were artful and bionic.

Bionic is now on v235 and thus is fixed-release for the systemd portion
of the bug.

I fear there might be other packages that are also affected by this,
thus I'm going to cherrypick the revert into artful in systemd as well.

** Changed in: systemd (Ubuntu Bionic)
   Status: Triaged => 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/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:
  New
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 1708409] Re: kdump service does not start after configure/reboot

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Artful)
   Importance: Undecided => High

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

** Changed in: makedumpfile (Ubuntu Bionic)
   Importance: Undecided => Wishlist

** Changed in: makedumpfile (Ubuntu Artful)
   Importance: Undecided => Wishlist

-- 
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:
  Confirmed
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 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Dimitri John Ledkov]

Let's assume there is a systemd fault here too, thus marking systemd as
affected. I will try to play around with this, but may get to this by
December 14th the earliest.

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation Op

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Artful)
   Status: New => Won't Fix

** Description changed:

  [Impact]
  
  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.
  
  However, because other parts of the system rely on udev to load modules
  correctly, it is not acceptable for it to use an out of date module
  context.  For example, during a system installation:
  
  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date
  
  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and the
  nvme module is installed in the system.
  
+ The fix is to reload udevadm rules, as per upstream recommendation.
+ 
  [Test Case]
  
  This is reproducable when trying to install using debian-installer and a
  preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.
  
- However, the bug is easily reproducable on any system with a nvme drive
- using this script:
- 
- #!/bin/bash
- MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
- modprobe -rq nvme
- mv $MOD_DIR/nvme.ko .
- depmod -a
- sleep 3
- udevadm trigger
- sleep 1
- mv nvme.ko $MOD_DIR/
- depmod -a
- udevadm trigger
- sleep 3
- grep -q nvme /proc/partitions && echo PASS || echo FAIL
- 
- that script does:
- 1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
- 2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
- 3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
- 4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
- 5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
- 6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded
- 
- this script reproduces the error every time, due to the stale kmod
- context.  With a fixed udev, this should succeed in loading the nvme
- module.
+ Stale context in udevd is expected, and one is supposed to reload rules
+ via udevadm, which is the fix proposed in debian-installer-utils.
+ Removing the previous second test case that does not reload via udevadm.
  
  [Regression Potential]
  
- The most potential for regression with a fix to this involves slowing
- down udev due to validating the kmod context for every kmod load call.
- However, slightly higher performance does not make up for broken
- operation.
- 
- [Other Info]
- 
- This needs fixing upstream, which I'm in progress on.
+ Additional calls to udevadm reload will cause all udev rules to be re-
+ read correctly. This may lead to new devices
+ discovered/configured/symlink during d-i installer, which were
+ previously skipped/missed.

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Committed
Status in debian-installer-utils package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer-utils source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer-utils source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer-utils source package in Zesty:
  New
Status in debian-installer source package in Artful:
  New
Status in debian-installer-utils source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Won't Fix
Status in debian-installer source package in Bionic:
  Fix Committed
Status in debian-installer-utils source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix

Bug d

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Dmitrii Shcherbakov]

After booting with break=bottom kernel parameter I can see that symlinks
are in fact present at the initramfs stage.

They are gone afterwards post pivot_root & systemd start (the bcache dir
isn't even present while it was there)

ubuntu@maas-xenial4:~$ ls /dev/disk/
by-dname  by-id  by-label  by-path  by-uuid


** Attachment added: "bcache-symlinks-initramfs.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+attachment/5016556/+files/bcache-symlinks-initramfs.png

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Erro

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dimitri John Ledkov]

Whilst we can upload fixes for zesty and trusty; neither of those will
have a point release anymore to include a fix for this.

What is the rationale behind requesting a fix for trusty? How do you
expect it to get onto an .iso? A customized iso?

** Changed in: debian-installer-utils (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: debian-installer-utils (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: debian-installer-utils (Ubuntu Trusty)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: debian-installer-utils (Ubuntu Xenial)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: debian-installer-utils (Ubuntu Zesty)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: debian-installer-utils (Ubuntu Trusty)
   Status: New => Won't Fix

** Changed in: debian-installer (Ubuntu Trusty)
   Status: New => Won't Fix

** Changed in: debian-installer (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: debian-installer (Ubuntu Zesty)
   Status: New => Won't Fix

** No longer affects: debian-installer (Ubuntu Bionic)

** Changed in: debian-installer (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: debian-installer (Ubuntu)
Milestone: ubuntu-17.10 => None

** Changed in: debian-installer (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** No longer affects: debian-installer-utils (Ubuntu Bionic)

** No longer affects: systemd (Ubuntu)

** No longer affects: systemd (Ubuntu Artful)

** No longer affects: systemd (Ubuntu Bionic)

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in debian-installer-utils package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Won't Fix
Status in debian-installer-utils source package in Trusty:
  Won't Fix
Status in debian-installer source package in Xenial:
  New
Status in debian-installer-utils source package in Xenial:
  In Progress
Status in debian-installer source package in Zesty:
  Won't Fix
Status in debian-installer-utils source package in Zesty:
  In Progress
Status in debian-installer source package in Artful:
  Fix Released
Status in debian-installer-utils source package in Artful:
  Fix Released

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  The fix is to reload udevadm rules, as per upstream recommendation.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  Stale context in udevd is expected, and one is supposed to reload
  rules via udevadm, which is the fix proposed in debian-installer-
  utils. Removing the previous second test case that does not reload via
  udevadm.

  [Regression Potential]

  Additional calls to udevadm reload will cause all udev rules to be re-
  read correctly. This may lead to new devices
  discovered/configured/symlink during d-i installer, which were
  previously skipped/missed.

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

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

[Touch-packages] [Bug 1724013] Re: mount does not correctly process x-* options

[Phillip Susi]

mount.cifs is not part of util-linux, and it also is not supposed to
ignore unknown options.  This is only a feature of util-linux mount
since it is generic, and not expected to understand every possible
option supported by every possible filesystem.

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

Title:
  mount does not correctly process x-* options

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  According to the mount(8) man page:

  All options prefixed with "x-" are interpreted as comments or as
  userspace application-specific options.  These options are not stored
  in  the  mtab  file,  nor  sent  to  the mount.type helpers nor to the
  mount(2) system call.  The suggested format is x-appname.option (e.g.
  x-systemd.automount).

  However, adding any such option to cifs entry, such as "x-test.opt"
  (other than x-systemd.automount) results in:

  mount error(22): Invalid argument
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  No options starting with "x-" should be passed to mount.cifs, so the
  mount should succeed.

  Running Ubuntu 16.04.3 LTS
  mount package installed is 2.27.1-6ubuntu3.3

  This error always happens when such an option is specified. Here is an 
example fstab line that causes this failure:
  //192.168.1.3/Public/mnt/mybookcifs   
noauto,x-test.opt,rw,users,noperm,guest,soft,cache=none,sec=none  0  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mount 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 16 12:29:40 2017
  InstallationDate: Installed on 2016-04-22 (542 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1724013/+subscriptions

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

[Touch-packages] [Bug 1728560] Re: Cannot resolve smtp-mail.outlook.com

[Matevž Jekovec]

Another workaround is to add some other nameserver to /etc/resolv.conf
instead of 127.0.0.53.

For example:
nameserver 193.2.1.72

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

Title:
  Cannot resolve smtp-mail.outlook.com

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10, applications can no longer resolve smtp-
  mail.outlook.com, although host can:

  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com 25
  > telnet: could not resolve smtp-mail.outlook.com/25: Temporary failure in 
name resolution
  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com
  > telnet: could not resolve smtp-mail.outlook.com/telnet: Temporary failure 
in name resolution
  > mjg@payens:~/Projects/GNOME/geary$ host smtp-mail.outlook.com
  > smtp-mail.outlook.com is an alias for smtp.live.com.
  > smtp.live.com is an alias for smtp.glbdns2.microsoft.com.
  > smtp.glbdns2.microsoft.com is an alias for smtp.office365.com.
  > smtp.office365.com is an alias for smtp.outlook.office365.com.
  > smtp.outlook.office365.com is an alias for outlook.office365.com.
  > outlook.office365.com is an alias for lb.geo.office365.com.
  > lb.geo.office365.com is an alias for outlook.office365.com.g.office365.com.
  > outlook.office365.com.g.office365.com is an alias for 
outlook-au.office365.com.
  > outlook-au.office365.com has address 40.100.151.226
  > [many more replies snipped]

  Also reported on ask.ubuntu.com:
  https://askubuntu.com/questions/969689/dns-problem-trying-to-ping-or-
  send-email-using-smtp-mail-outlook-com-after-upgra

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  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.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 30 21:07:17 2017
  InstallationDate: Installed on 2015-07-22 (831 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
i915.fastboot=1 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B18.1610241407
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B18.1610241407:bd10/24/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1735434] [NEW] bug intel

[reno guacamole]

Public bug reported:

lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04


apt-cache policy pkgname
N: Unable to locate package pkgname


3) i wanted to fix intel driver so i could watch videos and audio normally 
without freeeze, the main issue is that i cant because is not sync together.

4)nothing happened it just freezes system and mouse and all the same ol'
continue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: i386
CurrentDesktop: LXDE
Date: Thu Nov 30 09:44:33 2017
InstallationDate: Installed on 2017-08-15 (106 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial

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

Title:
  bug intel

Status in xorg package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  apt-cache policy pkgname
  N: Unable to locate package pkgname

  
  3) i wanted to fix intel driver so i could watch videos and audio normally 
without freeeze, the main issue is that i cant because is not sync together.

  4)nothing happened it just freezes system and mouse and all the same
  ol' continue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Thu Nov 30 09:44:33 2017
  InstallationDate: Installed on 2017-08-15 (106 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

[Dimitri John Ledkov]

I believe caching is enabled by default, this might be a regression in
behaviour since switching to 127.0.0.53 caching resolver. It does drop
caches upon every new connection / re-connection.

It is freezing out there and snowing out there. But I guess I'll have to
make trek to Starbucks with my laptop tomorrow. Also will watch out for
this bug happening during my travels next week through different
airports.

int manager_new(Manager **ret) {
...
m->enable_cache = true;
...
r = manager_parse_config_file(m);
...
}

[Resolve]
...
#Cache=yes

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Eric Desrochers]

I have compile the php upstream source code from :
https://github.com/php/php-src

# php --version
PHP 7.3.0-dev (cli) (built: Nov 30 2017 14:52:31) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.3.0-dev, Copyright (c) 1998-2017 Zend Technologies

# date
Thu Nov 30 12:23:30 -03 2017

#php php_tz.php
UTC

I'll do a bisection, and will update the bug.

- Eric

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Dmitrii Shcherbakov]

Just in case also checked with this rule that creates links at /dev
/dev/disk/by-uuid /dev/bcache/by-uuid https://paste.ubuntu.com/26081756/

They are all there originally (see the screenshot).

But not there afterwards. So it's not just a problem with a different
path.

https://paste.ubuntu.com/26081775/

ubuntu@maas-xenial4:~$ tree /dev/ | grep bcache
├── bcache0
├── bcache1
├── bcache2
├── bcache3
│   ├── 251:0 -> ../bcache0
│   ├── 251:1 -> ../bcache1
│   ├── 251:2 -> ../bcache2
│   ├── 251:3 -> ../bcache3
│   │   ├── bcache0 -> ../../bcache0
│   │   ├── bcache1 -> ../../bcache1
│   │   ├── bcache2 -> ../../bcache2
│   │   ├── bcache3 -> ../../bcache3


** Attachment added: "bcache-multiple-links.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+attachment/5016592/+files/bcache-multiple-links.png

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arec

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Ihor Menshykov]

I'm upgraded to Ubuntu 18.04 prerelease and I still can't pair. I used
to fix the issue like this https://askubuntu.com/questions/833322/pair-
bose-quietcomfort-35-with-ubuntu-over-bluetooth on 16.04 once, it worked
for a while, but later stopped working and I couldn't pair my
headphones, donno why, maybe due to some updates, maybe "just because".
Decided to update and try if it maybe worked in a more recent version,
but it didn't work in 17.10 and still doesn't in current 18.04 dev
branch. Can't pair.

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

Title:
  Fails to pair with Bose QC35 headphones

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

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

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

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

Re: [Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Ryan Harper]

So, /dev/bcache/by-uuid is not getting created.

That's the same kernel bug I filed.

And, if they were, I think they'd get moved properly.

init-bottom/udev script does the following:

# Stop udevd, we'll miss a few events while we run init, but we catch up
udevadm control --exit

# move the /dev tmpfs to the rootfs
mount -n -o move /dev ${rootmnt}/dev

That "move" operation migrates the entire mounted directory to a new
location
so, if /dev/bcache/by-uuid  existed, it would be present when systemd init
runs.

AFAICT, there's not fix here without the kernel side.

On Thu, Nov 30, 2017 at 10:09 AM, Dmitrii Shcherbakov <
1729...@bugs.launchpad.net> wrote:

> Just in case also checked with this rule that creates links at /dev
> /dev/disk/by-uuid /dev/bcache/by-uuid https://paste.ubuntu.com/26081756/
>
> They are all there originally (see the screenshot).
>
> But not there afterwards. So it's not just a problem with a different
> path.
>
> https://paste.ubuntu.com/26081775/
>
> ubuntu@maas-xenial4:~$ tree /dev/ | grep bcache
> ├── bcache0
> ├── bcache1
> ├── bcache2
> ├── bcache3
> │   ├── 251:0 -> ../bcache0
> │   ├── 251:1 -> ../bcache1
> │   ├── 251:2 -> ../bcache2
> │   ├── 251:3 -> ../bcache3
> │   │   ├── bcache0 -> ../../bcache0
> │   │   ├── bcache1 -> ../../bcache1
> │   │   ├── bcache2 -> ../../bcache2
> │   │   ├── bcache3 -> ../../bcache3
>
>
> ** Attachment added: "bcache-multiple-links.png"
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+attachment/5016592/+files/bcache-multiple-links.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The 

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

[Dimitri John Ledkov]

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)

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

Title:
  systemd translations are not synced with upstream

Status in Ubuntu Translations:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1707898/+subscriptions

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

[Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Eric Desrochers]

At code inspection I have strong believe this commit is the one changing
the behaviour between comment #2 (America/Sao_Paulo) and comment#6 (UTC)

* 8e3260376c Update timezonemap.h, which needs to match

commit 8e3260376c65b762a51eee7c30ab560dadefa1f6
Author: Derick Rethans 
Date:   Tue Oct 24 14:55:13 2017 +0100

Update timezonemap.h, which needs to match the bundled TZ db

...
-   { "wgst",  1,  -7200, "America/Godthab"   },
-   { "wgt",   0, -10800, "America/Godthab"   },
...


$ git tag --contains  8e3260376c
php-7.0.26
php-7.0.26RC1
php-7.1.12
php-7.1.12RC1
php-7.2.0
php-7.2.0RC5
php-7.2.0RC6

It seems like this update has been backported in upstream 7.0, 7.1, ...
~1month ago.

This would possibly need an SRU to adapt our different PHP package
version where it applies to stay align with new tzdata package.

- Eric

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

[Jeremy Bicha]

** Changed in: systemd (Ubuntu)
 Assignee: Ubuntu Desktop (ubuntu-desktop) => Canonical Desktop Team 
(canonical-desktop-team)

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

Title:
  systemd translations are not synced with upstream

Status in Ubuntu Translations:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1707898/+subscriptions

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

[Touch-packages] [Bug 1733700] [NEW] aa-enforce fails due to syntax error in snapd.snap-confine profile

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On Ubuntu artful, I'm seeing the following behavior:

$ aa-enforce usr.bin.chromium-browser

ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
include "/var/lib/snapd/apparmor/snap-confine.d"   /etc/ld.so.cache r,

I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
This is snapd 2.28.5+17.10.

** Affects: apparmor (Ubuntu)
 Importance: Undecided
 Assignee: Jamie Strandboge (jdstrand)
 Status: Triaged

-- 
aa-enforce fails due to syntax error in snapd.snap-confine profile
https://bugs.launchpad.net/bugs/1733700
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apparmor in Ubuntu.

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

Re: [Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Ryan Harper]

Investigating why /dev doesn't have the correct links even if they're
present led me to look at
/usr/share/initramfs-tools/scripts/init-bottom/udev (provided via the udev
dpkg from systemd)

In there, the mount -n -o move is used to migrate the /dev from initramfs
to the rootfs/dev

This bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844775

Indicated that the initramfs may have util-linux version of mount which
needs to use
mount --move  instead.  This is addressed in newer systemd packages (in
bionic for sure)

And the mount line now looks like this:


# move the /dev tmpfs to the rootfs; fall back to util-linux mount that does
# not understand -o move
mount -n -o move /dev ${rootmnt}/dev || mount -n --move /dev ${rootmnt}/dev

Let's see if that helps resolve the "missing" symlinks.


On Thu, Nov 30, 2017 at 10:27 AM, Ryan Harper 
wrote:

> So, /dev/bcache/by-uuid is not getting created.
>
> That's the same kernel bug I filed.
>
> And, if they were, I think they'd get moved properly.
>
> init-bottom/udev script does the following:
>
> # Stop udevd, we'll miss a few events while we run init, but we catch up
> udevadm control --exit
>
> # move the /dev tmpfs to the rootfs
> mount -n -o move /dev ${rootmnt}/dev
>
> That "move" operation migrates the entire mounted directory to a new
> location
> so, if /dev/bcache/by-uuid  existed, it would be present when systemd init
> runs.
>
> AFAICT, there's not fix here without the kernel side.
>
> On Thu, Nov 30, 2017 at 10:09 AM, Dmitrii Shcherbakov <
> 1729...@bugs.launchpad.net> wrote:
>
>> Just in case also checked with this rule that creates links at /dev
>> /dev/disk/by-uuid /dev/bcache/by-uuid https://paste.ubuntu.com/26081756/
>>
>> They are all there originally (see the screenshot).
>>
>> But not there afterwards. So it's not just a problem with a different
>> path.
>>
>> https://paste.ubuntu.com/26081775/
>>
>> ubuntu@maas-xenial4:~$ tree /dev/ | grep bcache
>> ├── bcache0
>> ├── bcache1
>> ├── bcache2
>> ├── bcache3
>> │   ├── 251:0 -> ../bcache0
>> │   ├── 251:1 -> ../bcache1
>> │   ├── 251:2 -> ../bcache2
>> │   ├── 251:3 -> ../bcache3
>> │   │   ├── bcache0 -> ../../bcache0
>> │   │   ├── bcache1 -> ../../bcache1
>> │   │   ├── bcache2 -> ../../bcache2
>> │   │   ├── bcache3 -> ../../bcache3
>>
>>
>> ** Attachment added: "bcache-multiple-links.png"
>>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172914
>> 5/+attachment/5016592/+files/bcache-multiple-links.png
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1729145
>>
>> Title:
>>   /dev/bcache/by-uuid links not created after reboot
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145
>> /+subscriptions
>>
>
>

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache:

[Touch-packages] [Bug 1733700] Re: aa-enforce fails due to syntax error in snapd.snap-confine profile

[Jamie Strandboge]

Ok, the snapd issue is being tracked in bug #1734038 so I'm going to use
this one for the apparmor-utils python utilities upstream bug and Ubuntu
SRU. More details to come.

** Package changed: snapd (Ubuntu) => apparmor (Ubuntu)

** Changed in: apparmor (Ubuntu)
 Assignee: Zygmunt Krynicki (zyga) => Jamie Strandboge (jdstrand)

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

Title:
  aa-enforce fails due to syntax error in snapd.snap-confine profile

Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu artful, I'm seeing the following behavior:

  $ aa-enforce usr.bin.chromium-browser
  
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d"   /etc/ld.so.cache r,

  I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
  This is snapd 2.28.5+17.10.

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

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

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Ryan Harper]

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

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bas

[Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Eric Desrochers]

** Also affects: php7.1 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)

[Jamie Strandboge]

Since snapd is using this bug for its SRU blocker and we have bug
#1733700 that is the same issue, I'm going to use this bug as the snapd
one and for the apparmor one.

** Summary changed:

- utils don't understand «include "/where/ever"» (was: Potential regression 
found with apparmor test on Xenial/Zesty)
+ snap-confine profile uses 'include' instead of '#include' which breaks 
apparmor-utils python toolsnd with apparmor test on Xenial/Zesty)

** No longer affects: apparmor

** Summary changed:

- snap-confine profile uses 'include' instead of '#include' which breaks 
apparmor-utils python toolsnd with apparmor test on Xenial/Zesty)
+ snap-confine profile uses 'include' instead of '#include' which breaks 
apparmor-utils python tools

** No longer affects: apparmor (Ubuntu)

** No longer affects: linux (Ubuntu)

** Changed in: snapd (Ubuntu)
   Status: Invalid => In Progress

** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Michael Vogt (mvo)

** Also affects: snapd (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

** Also affects: snapd (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Michael Vogt (mvo)
   Status: In Progress

** Also affects: snapd (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  snap-confine profile uses 'include' instead of '#include' which breaks
  apparmor-utils python tools

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Trusty:
  New
Status in snapd source package in Xenial:
  New
Status in snapd source package in Zesty:
  New
Status in snapd source package in Artful:
  New
Status in snapd source package in Bionic:
  In Progress

Bug description:
  Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41,
  across different architectures

  Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error 
message:
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,

  (BTW the include and this ld.so.cache are not in the same line, please
  refer to comment #3 for attachment)

  This issue will gone if you downgrade the snapd and ubuntu-core-launcher 
package:
  sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5

  Debug information:
  ubuntu@kernel01:~$ snap version
  snap2.29.3
  snapd   2.29.3
  series  16
  ubuntu  16.04
  kernel  4.4.0-102-generic

  ubuntu@kernel01:~$ apt list snapd
  Listing... Done
  snapd/xenial-proposed,now 2.29.3 s390x [installed]
  N: There are 2 additional versions. Please use the '-a' switch to see them.

  ubuntu@kernel01:~$ apt list apparmor -a
  Listing... Done
  apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed]
  apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x
  apparmor/xenial 2.10.95-0ubuntu2 s390x

  Steps to run the Apparmor test from QA Regression testing suite:
1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing
2. sudo ./qa-regression-testing/scripts/test-apparmor.py

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-102-generic 4.4.0-102.125
  ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98
  Uname: Linux 4.4.0-102-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Thu Nov 23 01:36:31 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-102-generic N/A
   linux-backports-modules-4.4.0-102-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
htt

[Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Eric Desrochers]

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

** Also affects: php7.0 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883209
   Importance: Unknown
   Status: Unknown

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid
Status in php7.0 package in Debian:
  Unknown

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 1733700] Re: apparmor python tools do not understand 'include' rules

[Jamie Strandboge]

** Summary changed:

- aa-enforce fails due to syntax error in snapd.snap-confine profile
+ apparmor python tools do not understand 'include' rules

** Description changed:

+ The apparmor_parser now supports 'include' rules in addition to
+ '#include', but the python tools only understand '#include'. This
+ manifested itself in Ubuntu in bug #1734038 (see
+ https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15
+ of that bug for details).
+ 
+ Reproducer:
+ 
+ $ mkdir /tmp/test
+ 
+ $ cat /etc/apparmor.d/lp1733700
+ profile lp1733700 {
+   include "/tmp/test"
+ }
+ 
+ $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
+ ok
+ 
+ $ sudo aa-enforce /etc/apparmor.d/lp1733700
+ ERROR: Syntax Error: Missing '}' or ','. Reached end of file 
/etc/apparmor.d/lp1733700 while inside profile lp1733700
+ 
+ Changing the 'include' to '#include' results in:
+ $ sudo aa-enforce /etc/apparmor.d/lp1733700 
+ Setting /etc/apparmor.d/lp1733700 to enforce mode.
+ 
+ At least aa-logprof is also affected.
+ 
+ = Original report =
  On Ubuntu artful, I'm seeing the following behavior:
  
  $ aa-enforce usr.bin.chromium-browser
  
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d"   /etc/ld.so.cache r,
  
  I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
  This is snapd 2.28.5+17.10.

** Also affects: apparmor
   Importance: Undecided
   Status: New

** Changed in: apparmor (Ubuntu)
 Assignee: Jamie Strandboge (jdstrand) => (unassigned)

** Changed in: apparmor
   Status: New => Triaged

** Also affects: apparmor (Ubuntu Bionic)
   Importance: Undecided
   Status: Triaged

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

** Also affects: apparmor (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Also affects: apparmor (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

Title:
  apparmor python tools do not understand 'include' rules

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Zesty:
  New
Status in apparmor source package in Artful:
  New
Status in apparmor source package in Bionic:
  New

Bug description:
  The apparmor_parser now supports 'include' rules in addition to
  '#include', but the python tools only understand '#include'. This
  manifested itself in Ubuntu in bug #1734038 (see
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15
  of that bug for details).

  Reproducer:

  $ mkdir /tmp/test

  $ cat /etc/apparmor.d/lp1733700
  profile lp1733700 {
include "/tmp/test"
  }

  $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
  ok

  $ sudo aa-enforce /etc/apparmor.d/lp1733700
  ERROR: Syntax Error: Missing '}' or ','. Reached end of file 
/etc/apparmor.d/lp1733700 while inside profile lp1733700

  Changing the 'include' to '#include' results in:
  $ sudo aa-enforce /etc/apparmor.d/lp1733700 
  Setting /etc/apparmor.d/lp1733700 to enforce mode.

  At least aa-logprof is also affected.

  = Original report =
  On Ubuntu artful, I'm seeing the following behavior:

  $ aa-enforce usr.bin.chromium-browser
  
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d"   /etc/ld.so.cache r,

  I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
  This is snapd 2.28.5+17.10.

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

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

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

[AsciiWolf]

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

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=791035
   Importance: Unknown
   Status: Unknown

-- 
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:
  Unknown
Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gettext package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug 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 1733700] Re: apparmor python tools do not understand 'include' rules

[Jamie Strandboge]

@Felix Eckhofer - please see
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15

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

Title:
  apparmor python tools do not understand 'include' rules

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Zesty:
  New
Status in apparmor source package in Artful:
  New
Status in apparmor source package in Bionic:
  New

Bug description:
  The apparmor_parser now supports 'include' rules in addition to
  '#include', but the python tools only understand '#include'. This
  manifested itself in Ubuntu in bug #1734038 (see
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15
  of that bug for details).

  Reproducer:

  $ mkdir /tmp/test

  $ cat /etc/apparmor.d/lp1733700
  profile lp1733700 {
include "/tmp/test"
  }

  $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
  ok

  $ sudo aa-enforce /etc/apparmor.d/lp1733700
  ERROR: Syntax Error: Missing '}' or ','. Reached end of file 
/etc/apparmor.d/lp1733700 while inside profile lp1733700

  Changing the 'include' to '#include' results in:
  $ sudo aa-enforce /etc/apparmor.d/lp1733700 
  Setting /etc/apparmor.d/lp1733700 to enforce mode.

  At least aa-logprof is also affected.

  = Original report =
  On Ubuntu artful, I'm seeing the following behavior:

  $ aa-enforce usr.bin.chromium-browser
  
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d"   /etc/ld.so.cache r,

  I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
  This is snapd 2.28.5+17.10.

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

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

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Brian Murray]

There seems to be an autopkgtest failure on s390x which requires
investigation.

http://autopkgtest.ubuntu.com/packages/n/network-manager/xenial/s390x

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

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

Bug description:
  SRU REQUEST:

  Debdiff (nm-dhcp-helper.debdiff) attached.

  Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This
  bug was fixed upstream in 1.4.

  [Impact]

   * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
     lease renewal due to a DBus race condition.

   * Upstream NetworkManager 1.4 fixes the race condition by changing
     nm-dhcp-helper's DBus notification from signal "Event" to method
     "Notify".

   * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
     NM 1.2.x.

  [Test Case]

   * Not reliably reproducible. Out of hundreds of machines, only a
     dozen or so fail to notify NetworkManager of a DHCP lease
     renewal about 30-50% of the time. (i.e. It's always the same
     handful of machines that fail.)

   * All such machines with the patched packages have been fine for weeks,
     over many dozens of lease renewals.

  [Regression Potential]

  * The patch changes both nm-dhcp-helper and NetworkManager itself. As
  soon as the new packages are unpacked, the new nm-dhcp-helper will be
  used on DHCP lease renewals, with the new Notify mechanism. Since the
  running, old NetworkManager is still expecting Event notifications,
  the patched nm-dhcp-helper has fallback capability to Event.

  * Once NetworkManager is restarted and is running the patched version,
  it will have the new Notify support.

  [Other Info]

   * Upstream bug w/ patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=784636

   * RHEL bug with links to the 1.4 commits from which the patch was
     derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

   * NOTE:  The final comment on the upstream GNOME bug claims that the
  fix is incomplete.  However, it is possible that the running
  NetworkManager was not restarted (see Regression Potential notes
  above), which is why nm-dhcp-helper is falling back to Event.  The
  remainder of the log messages in that final comment are from a custom
  wrapper the submitter was running around nm-dhcp-helper.  I have
  deployed the exact same patch (without said wrapper) to real-world
  systems and tested extensively, and see nothing but successful DHCP
  lease renewal notifications using D-Bus Notify, not D-Bus Event.


  
  I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').

  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, 

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Dmitrii Shcherbakov]

Ryan,

As discussed in IRC, I tweaked locations for testing in #11 and added
all paths in #14.

Looks like after `mount -n -o move /dev ${rootmnt}/dev` ${rootmnt}/dev
has the proper content (see the bcache rule as well)

https://paste.ubuntu.com/26082611/
== before ==
lrwxrwxrwx113 
/dev/bcache/by-uuid/aa04ab39-a42c-446f-aff5-addbd9c80e06 -> ../../bcache0
lrwxrwxrwx113 
/dev/bcache/by-uuid/835afacf-6213-48a9-864c-43733822668b -> ../../bcache3
lrwxrwxrwx113 
/dev/bcache/by-uuid/727212eb-0f0b-4d20-9191-f0577a38454e -> ../../bcache1
lrwxrwxrwx113 
/dev/bcache/by-uuid/2963855b-3d2b-4387-abd1-3ae788919de4 -> ../../bcache2

== after ==
lrwxrwxrwx113 
/root/dev/bcache/by-uuid/aa04ab39-a42c-446f-aff5-addbd9c80e06 -> ../../bcache0
lrwxrwxrwx113 
/root/dev/bcache/by-uuid/835afacf-6213-48a9-864c-43733822668b -> ../../bcache3
lrwxrwxrwx113 
/root/dev/bcache/by-uuid/727212eb-0f0b-4d20-9191-f0577a38454e -> ../../bcache1
lrwxrwxrwx113 
/root/dev/bcache/by-uuid/2963855b-3d2b-4387-abd1-3ae788919de4 -> ../../bcache2

So the problem must be further down.

And about the only thing I see in the init script is run-init from
klibc:

# Chain to real filesystem
exec run-init ${drop_caps} ${rootmnt} ${init} "$@" 
${recovery:+--startup-event=recovery} <${rootmnt}/dev/console 
>${rootmnt}/dev/console 2>&1

So it's either somewhere in run-init code

https://git.launchpad.net/~usd-import-
team/ubuntu/+source/klibc/tree/usr/kinit/run-
init/runinitlib.c?h=applied/ubuntu/xenial-updates#n158

or in systemd.

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcach

[Touch-packages] [Bug 1733700] Re: apparmor python tools do not understand 'include' rules

[Tyler Hicks]

I took a quick look at this bug to attempt to locate the problem. I
originally thought it was due to the Python utils' parser not supporting
include rules that are missing a leading '#' but that's not the case
since the regex in utils/apparmor/regex.py supports such an include
rule:

  RE_INCLUDE = re.compile('^\s*#?include\s*<(?P.*)>' +
RE_EOL)

The problem here is due to the regex only supporting include paths that
are surrounded by <>. The apparmor_parser allows for absolute include
paths to be surrounded by "" or by nothing at all and that is what the
Python utils do not currently support.

Also note that there are existing, but commented out, tests for this
style of include rules in utils/test/test-regex_matches.py:

class Test_re_match_include(AATest):
tests = [
...
# ('include foo',   'foo'   
), # XXX not supported in tools yet
# ('include /foo/bar',  '/foo/bar'  
), # XXX not supported in tools yet
# ('include "foo"', 'foo'   
), # XXX not supported in tools yet
# ('include "/foo/bar"','/foo/bar'  
), # XXX not supported in tools yet

...
]

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

Title:
  apparmor python tools do not understand 'include' rules

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Zesty:
  New
Status in apparmor source package in Artful:
  New
Status in apparmor source package in Bionic:
  New

Bug description:
  The apparmor_parser now supports 'include' rules in addition to
  '#include', but the python tools only understand '#include'. This
  manifested itself in Ubuntu in bug #1734038 (see
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15
  of that bug for details).

  Reproducer:

  $ mkdir /tmp/test

  $ cat /etc/apparmor.d/lp1733700
  profile lp1733700 {
include "/tmp/test"
  }

  $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
  ok

  $ sudo aa-enforce /etc/apparmor.d/lp1733700
  ERROR: Syntax Error: Missing '}' or ','. Reached end of file 
/etc/apparmor.d/lp1733700 while inside profile lp1733700

  Changing the 'include' to '#include' results in:
  $ sudo aa-enforce /etc/apparmor.d/lp1733700 
  Setting /etc/apparmor.d/lp1733700 to enforce mode.

  At least aa-logprof is also affected.

  = Original report =
  On Ubuntu artful, I'm seeing the following behavior:

  $ aa-enforce usr.bin.chromium-browser
  
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d"   /etc/ld.so.cache r,

  I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
  This is snapd 2.28.5+17.10.

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

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

[Touch-packages] [Bug 1673717] Re: rsyslog GnuTLS error -50

[Bug Watch Updater]

** Changed in: rsyslog (Debian)
   Status: New => Fix Released

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

Title:
  rsyslog GnuTLS error -50

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog package in Debian:
  Fix Released

Bug description:
  Exactly the same as this:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995

  Error:

  > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The 
  > request is invalid.  [v8.16.0 try http://www.rsyslog.com/e/2078 ]

  Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works.

  Please apply patch or upgrade rsyslog.

  Ubuntu 16.04 AMD64
  Rsyslog 8.16.0-1ubuntu3

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

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

[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added

[Brian Murray]

Hello Kleber, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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, details of your
testing will help us make a better decision.

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

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

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

** Changed in: systemd (Ubuntu)
   Status: In Progress => 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/1734908

Title:
  systemd-rfkill service times out when a new rfkill device is added

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The following issue was observed while running network-
  manager=1.8.4-1ubuntu3 autopkgtest on Artful with
  systemd=234-2ubuntu12.1:

  ---
  Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start 
operation timed out. Terminating.
  Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill 
Switch Status.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered 
failed state.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with 
result 'timeout'.
  ---

  This happens after the testcase inserts the fake-rfkill module (a
  module shipped with network-manager tests that registers a new fake
  device with the rfkill subsystem).

  On Artful, it causes the network-manager autopkgtest killswitches-no-
  urfkill to fail (see bug 1733321).

  
  [Fix]

  The issue is fixed by the following systemd upstream patches:

  ---
  
https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

  commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
  Author: S. Fan 
  Date:   Mon Jul 31 05:10:10 2017 -0500

  rfkill: fix erroneous behavior when polling the udev monitor
  (#6489)

  Comparing udev_device_get_sysname(device) and sysname will always return
  true. We need to check the device received from udev monitor instead.

  Also, fd_wait_for_event() sometimes never exits. Better set a timeout
  here.
  ---

  ---
  
https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac

  commit c7f6ca9379279affa8f22d15fa13063491f86a49
  Author: Xiang Fan 
  Date:   Wed Aug 9 05:51:53 2017 -0500

  rfkill: fix typo (#6574)
  ---

  With the fixes, the output from systemd-rfkill is:

  ---
  Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev 
monitor.
  Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch 
Status.
  ---

  The patches are needed to fix the ADT tests observed with Artful tests on 
ppc64el architecture:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  Regression potential is minimal, since the fix has been applied some
  months ago on upstream github repo and it's being shipped with systemd
  on Bionic (systemd=235-3ubuntu2)

To manage notifications about this 

[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

[LaurentP]

hello, 
i have got sound on Line out, rear jack, by applied the proccess documented in 
this forum : 
[url]https://ubuntuforums.org/showthread.php?t=2326126&p=13496676#post13496676[/url].

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1166529/+subscriptions

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

[Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Eric Desrochers]

I try to do more testing to conclude my assumption and see if anything
else is needed.

Meanwhile I have reported a bug in debbug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883209

- Eric

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid
Status in php7.0 package in Debian:
  Unknown

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Eric Desrochers]

I'll try to do more testing to conclude my assumption and see if
anything else is needed.

Meanwhile I have reported a bug in debbug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883209

- Eric

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid
Status in php7.0 package in Debian:
  Unknown

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[gldickens3]

One of the primary differences in freetype-2.8 and prior Ubuntu versions
of freetype is the introduction of TT_CONFIG_OPTION_SUBPIXEL_HINTING in
/include/freetype/config/ftoption.h in freetype-2.7.X and later. The
default value is:

#define TT_CONFIG_OPTION_SUBPIXEL_HINTING  2

This needs to be undefined (uncommented) in order for freetype-2.7 and
2.8 to render fonts identically to prior versions of Ubuntu freetype
(freetype-2.6.X and earlier).

The diff file (freetype_2.8-0.2ubuntu2.diff.gz) at
https://launchpad.net/ubuntu/+source/freetype/2.8-0.2ubuntu2 enables
FT_CONFIG_OPTION_SUBPIXEL_RENDERING in
/include/freetype/config/ftoption.h with:

#define FT_CONFIG_OPTION_SUBPIXEL_RENDERING

This properly enables subpixel rendering to render fonts identical to MS
cleartype, however, if TT_CONFIG_OPTION_SUBPIXEL_HINTING is also set
then the fonts are rendered differently than before.  So, this problem
is fixed simply by undefining TT_CONFIG_OPTION_SUBPIXEL_HINTING.

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[gldickens3]

In the first line of third paragraph of my prior post I meant to say
"(commented out)" instead of "(uncommented)"  So, that line should read:
"This needs to be undefined (commented out) in order for freetype-2.7
and 2.8 to render fonts identically to prior versions of Ubuntu freetype
(freetype-2.6.X and earlier)."

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1722313] Re: Enable auditing in util-linux.

[Brian Murray]

Hello Joy, or anyone else affected,

Accepted util-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.27.1-6ubuntu3.4 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

** Changed in: util-linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Changed in: util-linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Zesty:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.
   
  Only the hwclock and the login commands within util-linux package have source 
code for auditing. But that source code is disabled by default and requires the 
config option, --with-audit to enable it. The login command is not built nor 
shipped in util-linux. Ubuntu uses the login command from shadow instead. Thus, 
only hwclock command would be affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged if auditd daemon is running.
  Otherwise, nothing gets logged.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+subscriptions

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

[Touch-packages] [Bug 1722313] Please test proposed package

[Brian Murray]

Hello Joy, or anyone else affected,

Accepted util-linux into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.29-1ubuntu2.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-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, details of your testing
will help us make a better decision.

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

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Zesty:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.
   
  Only the hwclock and the login commands within util-linux package have source 
code for auditing. But that source code is disabled by default and requires the 
config option, --with-audit to enable it. The login command is not built nor 
shipped in util-linux. Ubuntu uses the login command from shadow instead. Thus, 
only hwclock command would be affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged if auditd daemon is running.
  Otherwise, nothing gets logged.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+subscriptions

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

[Touch-packages] [Bug 1731102] Re: Poor performance with Wayland

[Launchpad Bug Tracker]

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

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

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

Title:
  Poor performance with Wayland

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE
  env var) I see the following issues on this hardware:

  * Jerky animations (glxgears stutters noticably)
  * Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is 
under load, appearing to worsen over time (> 8 hours uptime)
  * High CPU usage when mousing over icons in left-hand side Unity dock 
(20-30%), also causing mouse cursor to stutter
  * 15fps in Kodi and poor video playback framerate
  * 30-40% CPU usage in Kodi when program idle
  * Gnome shell frequently using 25% of CPU or more

  All issues disappear when using x11 mode (again confirmed with
  XDG_SESSION_TYPE env var). Performance in that case seems as good as
  17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
* Restoring resolver state...    
[ OK ]
   Starting jabber server: ejabberd
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 13:03:08 2017
  DistUpgraded: 2017-11-07 09:38:15,448 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6310] 
[19da:a191]
  InstallationDate: Installed on 2011-12-05 (2165 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=e1bf9820-e70e-4e84-9037-621437cc90f1 ro radeon.audio=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-06 (2 days ago)
  dmi.bios.date: 10/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.name: AMD HUDSON-M1
  dmi.board.vendor: ZOTAC
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd10/28/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct 18 20:39:16 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputRiitek Micro Keyboard KEYBOARD, id 8
   inputRiitek Micro Keyboard MOUSE, id 9
   inputRiitek Micro Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: radeon

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Brian Murray]

Hello Marco, or anyone else affected,

Accepted nux into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nux/4.0.8+16.04.20170816-0ubuntu1
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

** Tags added: verification-needed verification-needed-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 961679] Re: gtkrc is producing light menus from dark elements

[Brian Murray]

I'll go ahead and accept this but the bug is missing an SRU test case
and regression potential.

** Changed in: ubuntu-themes (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  gtkrc is producing light menus from dark elements

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Committed

Bug description:
  Examples - 
  Right click on any window's title bar
  In app window menus of gtk 2 apps, examples -  synaptic, browsers where 
global menus aren't used, vlc with no global menu, ect.
  Right click in a browser's  menu bar
  Systray right click menus

  The in app window  context menu of gtk2 windows is correctly light,
  maybe there is no way to have both, ie., it's either all dark or all
  light?

  The choice here would be to go with all dark if there is no other way

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: light-themes 0.1.8.31-0ubuntu1 [modified: 
usr/share/themes/Ambiance/gtk-2.0/gtkrc 
usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css 
usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css 
usr/share/themes/Ambiance/gtk-3.0/gtk.css 
usr/share/themes/Ambiance/gtk-3.0/settings.ini 
usr/share/themes/Ambiance/metacity-1/close.png 
usr/share/themes/Ambiance/metacity-1/close_focused_normal.png 
usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png 
usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png 
usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml]
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
  Uname: Linux 3.2.0-19-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 21 17:42:27 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: light-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 961679] Please test proposed package

[Brian Murray]

Hello Doug, or anyone else affected,

Accepted ubuntu-themes into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/14.04+16.04.20171116-0ubuntu1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  gtkrc is producing light menus from dark elements

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Committed

Bug description:
  Examples - 
  Right click on any window's title bar
  In app window menus of gtk 2 apps, examples -  synaptic, browsers where 
global menus aren't used, vlc with no global menu, ect.
  Right click in a browser's  menu bar
  Systray right click menus

  The in app window  context menu of gtk2 windows is correctly light,
  maybe there is no way to have both, ie., it's either all dark or all
  light?

  The choice here would be to go with all dark if there is no other way

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: light-themes 0.1.8.31-0ubuntu1 [modified: 
usr/share/themes/Ambiance/gtk-2.0/gtkrc 
usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css 
usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css 
usr/share/themes/Ambiance/gtk-3.0/gtk.css 
usr/share/themes/Ambiance/gtk-3.0/settings.ini 
usr/share/themes/Ambiance/metacity-1/close.png 
usr/share/themes/Ambiance/metacity-1/close_focused_normal.png 
usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png 
usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png 
usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml]
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
  Uname: Linux 3.2.0-19-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 21 17:42:27 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: light-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[gldickens3]

Adding the attached patch to the diff file will cause freetype-2.8 to
render fonts exactly like in earlier Ubuntu versions (such as
freetype-2.4.X, 2.5.X and 2.6.X).

** Patch added: "Patch to disable #define TT_CONFIG_OPTION_SUBPIXEL_HINTING"
   
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+attachment/5016686/+files/hintingoff.patch

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 961679] Re: gtkrc is producing light menus from dark elements

[Treviño]

** Description changed:

- Examples - 
+ [Impact]
+ 
+ Menu items for apps using gtk2 use a light color, which is inconsistent
+ with all other system apps using gtk3 and that are using dark menus.
+ 
+ [Test case]
+ 
  Right click on any window's title bar
  In app window menus of gtk 2 apps, examples -  synaptic, browsers where 
global menus aren't used, vlc with no global menu, ect.
  Right click in a browser's  menu bar
  Systray right click menus
  
- The in app window  context menu of gtk2 windows is correctly light,
- maybe there is no way to have both, ie., it's either all dark or all
- light?
+ The in app window  context menu of gtk2 windows should be dark.
  
- The choice here would be to go with all dark if there is no other way
+ [Regression potential]
  
- ProblemType: Bug
- DistroRelease: Ubuntu 12.04
+ Menu items not usable or readable in some apps.
+ 
+ ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: light-themes 0.1.8.31-0ubuntu1 [modified: 
usr/share/themes/Ambiance/gtk-2.0/gtkrc 
usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css 
usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css 
usr/share/themes/Ambiance/gtk-3.0/gtk.css 
usr/share/themes/Ambiance/gtk-3.0/settings.ini 
usr/share/themes/Ambiance/metacity-1/close.png 
usr/share/themes/Ambiance/metacity-1/close_focused_normal.png 
usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png 
usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png 
usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml]
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
  Uname: Linux 3.2.0-19-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 21 17:42:27 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- SourcePackage: light-themes
+  TERM=xterm
+  PATH=(custom, user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bashSourcePackage: light-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gtkrc is producing light menus from dark elements

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Menu items for apps using gtk2 use a light color, which is
  inconsistent with all other system apps using gtk3 and that are using
  dark menus.

  [Test case]

  Right click on any window's title bar
  In app window menus of gtk 2 apps, examples -  synaptic, browsers where 
global menus aren't used, vlc with no global menu, ect.
  Right click in a browser's  menu bar
  Systray right click menus

  The in app window  context menu of gtk2 windows should be dark.

  [Regression potential]

  Menu items not usable or readable in some apps.

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: light-themes 0.1.8.31-0ubuntu1 [modified: 
usr/share/themes/Ambiance/gtk-2.0/gtkrc 
usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css 
usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css 
usr/share/themes/Ambiance/gtk-3.0/gtk.css 
usr/share/themes/Ambiance/gtk-3.0/settings.ini 
usr/share/themes/Ambiance/metacity-1/close.png 
usr/share/themes/Ambiance/metacity-1/close_focused_normal.png 
usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png 
usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png 
usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml]
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
  Uname: Linux 3.2.0-19-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 21 17:42:27 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: light-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Dmitrii Shcherbakov]

Looks like masking systemd-udevd removes this behavior. Need to figure
out where it actually clears everything out.

ubuntu@maas-xenial4:~$ sudo systemctl mask systemd-udevd
11:32 PM Created symlink from /etc/systemd/system/systemd-udevd.service to 
/dev/null.

# reboot

ubuntu@maas-xenial4:~$ ls /dev/bcache/by-uuid/
2963855b-3d2b-4387-abd1-3ae788919de4  727212eb-0f0b-4d20-9191-f0577a38454e  
835afacf-6213-48a9-864c-43733822668b  aa04ab39-a42c-446f-aff5-addbd9c80e06

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No su

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Jeremy Bicha]

Gordon, according to earlier comments, the Qt part of this bug will be
fixed before 18.04 LTS's release. Are you using Kubuntu or Qt apps?

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1735549] [NEW] WiFi password asked at every reboot for non-admin users (and LightDM)

[Robert Nurnberg]

Public bug reported:

Fresh install of Kubuntu 16.04.3 LTS.

network-manager:
  Installed: 1.2.6-0ubuntu0.16.04.1
  Candidate: 1.2.6-0ubuntu0.16.04.1
  Version table:
 *** 1.2.6-0ubuntu0.16.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.2.2-0ubuntu0.16.04.4 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 1.1.93-0ubuntu4 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Steps to reproduce the bug (first part):
1. After a fresh install, for an administrator account connect to a secure WiFi 
network.
   Store password (in my case WPA) and through NM GUI allow all users to use 
WiFi network.
2. Create non-administrator user, called dummy, say.
3. After every reboot, an error will appear for dummy on login that he does not 
have sufficient  
privileges to make changes to network settings.

After reading 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/comments/26,
 this can be fixed by changing the permissions= entry in 
/etc/NetworkManager/system-connections
for the affected WiFi network.

Steps to reproduce the bug (second part):
Now on every reboot, the user dummy will be asked for the WiFi password once he 
logs in. Nothing that can be done through GUI (either as administrator or as 
dummy) changes that. Similarly, LightDM asks for the WiFi password after every 
reboot.

In my case I could fix the issue by manually editing the following
entries in the SSID file in /etc/NetworkManager/system-connections/:

psk-flags=0
psk=

Note that psk-flags was set to 1 beforehand. The meaning of these values can be 
found with
man nm-settings.

Note that this bug may or may not be related to the following bugs:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270791
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924

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

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

Title:
  WiFi password asked at every reboot for non-admin users (and LightDM)

Status in network-manager package in Ubuntu:
  New

Bug description:
  Fresh install of Kubuntu 16.04.3 LTS.

  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Steps to reproduce the bug (first part):
  1. After a fresh install, for an administrator account connect to a secure 
WiFi network.
 Store password (in my case WPA) and through NM GUI allow all users to use 
WiFi network.
  2. Create non-administrator user, called dummy, say.
  3. After every reboot, an error will appear for dummy on login that he does 
not have sufficient  
  privileges to make changes to network settings.

  After reading 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/comments/26,
 this can be fixed by changing the permissions= entry in 
/etc/NetworkManager/system-connections
  for the affected WiFi network.

  Steps to reproduce the bug (second part):
  Now on every reboot, the user dummy will be asked for the WiFi password once 
he logs in. Nothing that can be done through GUI (either as administrator or as 
dummy) changes that. Similarly, LightDM asks for the WiFi password after every 
reboot.

  In my case I could fix the issue by manually editing the following
  entries in the SSID file in /etc/NetworkManager/system-connections/:

  psk-flags=0
  psk=

  Note that psk-flags was set to 1 beforehand. The meaning of these values can 
be found with
  man nm-settings.

  Note that this bug may or may not be related to the following bugs:
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270791
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924

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

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

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

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => Confirmed

** Changed in: gnome-control-center
   Importance: Unknown => Medium

-- 
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:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gettext package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug 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 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Ray Link]

The autopkgtest failure on s390x is in a test that checks rfkill
integration.  s390 kernels do not have CONFIG_RFKILL set.  Behavior
change might have something to do with the recent change to s390x
autopkgtest from LXC containers to VMs?

https://lists.ubuntu.com/archives/ubuntu-devel/2017-November/040052.html

Successful s390 autpkgtests of previous versions of network-manager
skipped this test (among others):

> urfkill-integration  SKIP Test requires machine-level isolation but
testbed does not provide that

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

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

Bug description:
  SRU REQUEST:

  Debdiff (nm-dhcp-helper.debdiff) attached.

  Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This
  bug was fixed upstream in 1.4.

  [Impact]

   * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
     lease renewal due to a DBus race condition.

   * Upstream NetworkManager 1.4 fixes the race condition by changing
     nm-dhcp-helper's DBus notification from signal "Event" to method
     "Notify".

   * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
     NM 1.2.x.

  [Test Case]

   * Not reliably reproducible. Out of hundreds of machines, only a
     dozen or so fail to notify NetworkManager of a DHCP lease
     renewal about 30-50% of the time. (i.e. It's always the same
     handful of machines that fail.)

   * All such machines with the patched packages have been fine for weeks,
     over many dozens of lease renewals.

  [Regression Potential]

  * The patch changes both nm-dhcp-helper and NetworkManager itself. As
  soon as the new packages are unpacked, the new nm-dhcp-helper will be
  used on DHCP lease renewals, with the new Notify mechanism. Since the
  running, old NetworkManager is still expecting Event notifications,
  the patched nm-dhcp-helper has fallback capability to Event.

  * Once NetworkManager is restarted and is running the patched version,
  it will have the new Notify support.

  [Other Info]

   * Upstream bug w/ patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=784636

   * RHEL bug with links to the 1.4 commits from which the patch was
     derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

   * NOTE:  The final comment on the upstream GNOME bug claims that the
  fix is incomplete.  However, it is possible that the running
  NetworkManager was not restarted (see Regression Potential notes
  above), which is why nm-dhcp-helper is falling back to Event.  The
  remainder of the log messages in that final comment are from a custom
  wrapper the submitter was running around nm-dhcp-helper.  I have
  deployed the exact same patch (without said wrapper) to real-world
  systems and tested extensively, and see nothing but successful DHCP
  lease renewal notifications using D-Bus Notify, not D-Bus Event.


  
  I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').

  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266

[Touch-packages] [Bug 1735556] [NEW] package libxcursor1:amd64 1:1.1.14-1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, be

[Björn Rathsack]

Public bug reported:

trying to install drivers for Optimus graphics at Lenovo T420,
additional fan control. After reboot the system does not work, so i have
to repair it with the console...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxcursor1:amd64 1:1.1.14-1
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Nov 30 22:41:41 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d0]
 NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d0]
MachineType: LENOVO 4236VML
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=05281740-a0da-4925-a99e-014a01c71f61 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: libxcursor
Title: package libxcursor1:amd64 1:1.1.14-1 failed to install/upgrade: Paket 
ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  nochmal 
installieren, bevor Sie die Konfiguration versuchen.
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 07/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET76WW (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4236VML
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236VML:pvrThinkPadT420:rvnLENOVO:rn4236VML:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4236VML
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Nov 30 22:34:48 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: modeset

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


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

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

Title:
  package libxcursor1:amd64 1:1.1.14-1 failed to install/upgrade: Paket
  ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es
  nochmal installieren, bevor Sie die Konfiguration versuchen.

Status in libxcursor package in Ubuntu:
  New

Bug description:
  trying to install drivers for Optimus graphics at Lenovo T420,
  additional fan control. After reboot the system does not work, so i
  have to repair it with the console...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxcursor1:amd64 1:1.1.14-1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Nov 30 22:41:41 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration ve

[Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Bug Watch Updater]

** Changed in: php7.0 (Debian)
   Status: Unknown => New

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid
Status in php7.0 package in Debian:
  New

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 304345] Re: File chooser dialog doesn't provide network access

[Pablo Fontoura]

Chrome file chooser doesn't show network locations too. 
Ubuntu 16.04 LTS.

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

Title:
  File chooser dialog doesn't provide network access

Status in GTK+:
  Fix Released
Status in One Hundred Papercuts:
  Fix Released
Status in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Baltix:
  Fix Released

Bug description:
  Binary package hint: audacious

  Audacious cannot open files samba shares. Just like Gringotts and
  Firefox it cannot open (save) to network share.

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=8.10
  DISTRIB_CODENAME=intrepid
  DISTRIB_DESCRIPTION="Ubuntu 8.10"

  ii  audacious  1.5.1-3ubuntu1.1
  small and fast audio player which supports

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Ubuntu Foundations Team Bug Bot]

The attachment "Patch to disable #define
TT_CONFIG_OPTION_SUBPIXEL_HINTING" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

Re: [Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Ryan Harper]

It looks like there is some ordering issues:

This is a grep through /run/udev/links ; these are checked by udev-dev

# find . -name 'b250*'
./\x2fdisk\x2fby-uuid\x2f0a270acb-56b8-4498-8bad-b3bb149fe869/b250:1
./\x2fdisk\x2fby-uuid\x2f92b0868d-7e56-4956-8e55-2c90ebee4a72/b250:0
./\x2fbcache\x2fby-uuid\x2f92d882d8-38cd-4537-847b-6f9c40ba67b4/b250:1
./\x2fbcache\x2fby-uuid\x2f57e009b1-6bf4-42ea-abe0-334b10941a0b/b250:0

So both /dev/bcache/by-uuid and /dev/disk/by-uuid both point to the bcache
device (b250:0)

udevd shows this:

Nov 30 23:39:10.738290 ubuntu systemd-udevd[465]: LINK
'disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869'
/lib/udev/rules.d/60-persistent-storage.rules:79
Nov 30 23:39:10.738304 ubuntu systemd-udevd[465]: update old name,
'/dev/bcache/by-uuid/92d882d8-38cd-4537-847b-6f9c40ba67b4' no longer
belonging to '/devices/virtual/block/bcache1'
Nov 30 23:39:10.738321 ubuntu systemd-udevd[465]: no reference left, remove
'/dev/bcache/by-uuid/92d882d8-38cd-4537-847b-6f9c40ba67b4'
Nov 30 23:39:10.738361 ubuntu systemd-udevd[465]: found 'b250:1' claiming
'/run/udev/links/\x2fdisk\x2fby-uuid\x2f0a270acb-56b8-4498-8bad-b3bb149fe869'
Nov 30 23:39:10.738370 ubuntu systemd-udevd[465]: creating link
'/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869' to '/dev/bcache1'
Nov 30 23:39:10.738380 ubuntu systemd-udevd[465]: preserve already existing
symlink '/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869' to
'../../bcache1'
Nov 30 23:39:10.743215 ubuntu systemd-udevd[487]: LINK
'disk/by-uuid/92b0868d-7e56-4956-8e55-2c90ebee4a72'
/lib/udev/rules.d/60-persistent-storage.rules:79
Nov 30 23:39:10.743228 ubuntu systemd-udevd[487]: update old name,
'/dev/bcache/by-uuid/57e009b1-6bf4-42ea-abe0-334b10941a0b' no longer
belonging to '/devices/virtual/block/bcache0'
Nov 30 23:39:10.743247 ubuntu systemd-udevd[487]: no reference left, remove
'/dev/bcache/by-uuid/57e009b1-6bf4-42ea-abe0-334b10941a0b'
Nov 30 23:39:10.743291 ubuntu systemd-udevd[487]: found 'b250:0' claiming
'/run/udev/links/\x2fdisk\x2fby-uuid\x2f92b0868d-7e56-4956-8e55-2c90ebee4a72'
Nov 30 23:39:10.743302 ubuntu systemd-udevd[487]: creating link
'/dev/disk/by-uuid/92b0868d-7e56-4956-8e55-2c90ebee4a72' to '/dev/bcache0'
Nov 30 23:39:10.743312 ubuntu systemd-udevd[487]: preserve already existing
symlink '/dev/disk/by-uuid/92b0868d-7e56-4956-8e55-2c90ebee4a72' to
'../../bcache0'

It would seem that the 'no longer belonging to ...bcache1' is the trigger
for the removal
however, 250:1 is indeed bcache1 device.


# ls -al /dev/bcache1
brw-rw 1 root disk 250, 1 Nov 30 23:39 /dev/bcache1

Looking at the systemd/udev/udev-event.c it appears that for entries in
the current udev database that don't have a new event associated with them
get the call to remove the old link

void udev_event_execute_rules()
  ...
  if (major(udev_device_get_devnum(dev)) > 0) {
bool apply;

/* remove/update possible left-over symlinks from
old database entry */
if (event->dev_db != NULL)
udev_node_update_old_links(dev,
event->dev_db);


Will need to crawl through the db to see what the the event->dev_db entry
is and where that get's set.


On Thu, Nov 30, 2017 at 2:41 PM, Dmitrii Shcherbakov <
1729...@bugs.launchpad.net> wrote:

> Looks like masking systemd-udevd removes this behavior. Need to figure
> out where it actually clears everything out.
>
> ubuntu@maas-xenial4:~$ sudo systemctl mask systemd-udevd
> 11:32 PM Created symlink from /etc/systemd/system/systemd-udevd.service
> to /dev/null.
>
> # reboot
>
> ubuntu@maas-xenial4:~$ ls /dev/bcache/by-uuid/
> 2963855b-3d2b-4387-abd1-3ae788919de4  727212eb-0f0b-4d20-9191-f0577a38454e
> 835afacf-6213-48a9-864c-43733822668b  aa04ab39-a42c-446f-aff5-addbd9c80e06
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache polic

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Konrad Zapałowicz]

Hey,

I just have tried to pair the QC35 using bluez 5.42 and 5.46 and it did
pair. Could you capture HCI trace for me while you are pairing?

Type:

$ sudo btmon --write ~/bose-qc35.snoop

Then start searching for the headset and try to pair. Once pairing fails
kill the btmon and attach the .snoop file to this bug report.

Thanks.

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

Title:
  Fails to pair with Bose QC35 headphones

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

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

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

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

[Touch-packages] [Bug 1735594] [NEW] ubuntu automatically logs out when hovering sidebar

[Falk Bay]

Public bug reported:

When I use the Unity session I automatically get logged out under these
conditions:

When I hover with my mouse over the sidebar or the top-bar.
When I press the alt+tab combination.
When I press the super key.

running dmesg after this unwanted logout happens I get following
information:

compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
error 4 in i965_dri.so[7fbca2af6000+7e4000]

When I log in the first thing I see is an error message showing
something like this:

Could not apply the configuration stored for the monitors

required virtual size does not fit available size:
requested=(1,1),minimum=(320,200),maximum=(8192,8192)

Sometimes this appears twice.

The info about my installed compiz:

compiz:
  Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1
  Candidat:   1:0.9.13.1+17.10.20170901-0ubuntu1
  Taula de versió:
 *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages
100 /var/lib/dpkg/status

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


** Tags: crash logout

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

Title:
  ubuntu automatically logs out when hovering sidebar

Status in nux package in Ubuntu:
  New

Bug description:
  When I use the Unity session I automatically get logged out under
  these conditions:

  When I hover with my mouse over the sidebar or the top-bar.
  When I press the alt+tab combination.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  When I log in the first thing I see is an error message showing
  something like this:

  Could not apply the configuration stored for the monitors

  required virtual size does not fit available size:
  requested=(1,1),minimum=(320,200),maximum=(8192,8192)

  Sometimes this appears twice.

  The info about my installed compiz:

  compiz:
Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1
Candidat:   1:0.9.13.1+17.10.20170901-0ubuntu1
Taula de versió:
   *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1707742] Re: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: le paquet binutils n'est pas prêt pour la configuration configuration impossible (état actuel «

[Matthias Klose]

not a binutils issue.

please see https://askubuntu.com/questions/490671/fix-half-installed-
package


** Package changed: binutils (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: le
  paquet binutils n'est pas prêt pour la configuration  configuration
  impossible (état actuel « half-installed »)

Status in Ubuntu:
  Invalid

Bug description:
  I only know that Ubuntu said that there is a problem durint the
  installation

  I'm sorry about that

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: binutils 2.26.1-1ubuntu1~16.04.3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  Date: Mon Jul 31 22:18:26 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4.1
  ErrorMessage: le paquet binutils n'est pas prêt pour la configuration  
configuration impossible (état actuel « half-installed »)
  LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: binutils
  Title: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: le 
paquet binutils n'est pas prêt pour la configuration  configuration impossible 
(état actuel « half-installed »)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1687312] Re: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installed'

[Matthias Klose]

not a binutils issue.

please see https://askubuntu.com/questions/490671/fix-half-installed-
package


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

** Package changed: binutils (Ubuntu) => ubuntu

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

Title:
  package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade:
  package binutils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in Ubuntu:
  Invalid

Bug description:
  It is failed to install. The Computer is lattitude d430

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: binutils 2.26.1-1ubuntu1~16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Sun Apr 30 20:45:54 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  DuplicateSignature:
   package:binutils:2.26.1-1ubuntu1~16.04.3
   Setting up libc6-dev:i386 (2.23-0ubuntu7) ...
   dpkg: error processing package binutils (--configure):
package binutils is not ready for configuration
  ErrorMessage: package binutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-03-08 (417 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: binutils
  Title: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: 
package binutils is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: Upgraded to xenial on 2017-01-02 (118 days ago)

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

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

[Touch-packages] [Bug 1700363] Re: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installed'

[Matthias Klose]

not a binutils issue.

please see https://askubuntu.com/questions/490671/fix-half-installed-
package


** Package changed: binutils (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade:
  package binutils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in Ubuntu:
  Invalid

Bug description:
  no idea

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: binutils 2.26.1-1ubuntu1~16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Sun Jun 25 16:05:29 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4.1
  DuplicateSignature:
   package:binutils:2.26.1-1ubuntu1~16.04.3
   Setting up libc6-dev:i386 (2.23-0ubuntu9) ...
   dpkg: error processing package binutils (--configure):
package binutils is not ready for configuration
  ErrorMessage: package binutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-03-08 (473 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: binutils
  Title: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: 
package binutils is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: Upgraded to xenial on 2017-01-02 (174 days ago)

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

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

[Touch-packages] [Bug 1734184] Re: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: apport (Ubuntu)
   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/1734184

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

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  dpkg: ошибка при обработке пакета apport-gtk (--configure):
   проблемы зависимостей — оставляем не настроенным
  Настраивается пакет dnsmasq-base (2.75-1ubuntu0.16.04.4) …
  Отчёты apport не записаны, так как сообщение об ошибке указывает на повторную 
ошибку от предыдущего отказа.
 При обработке следующих пакетов произошли ошибки:
   apport
   apport-gtk
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.13
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CrashReports:
   600:0:117:789919:2017-11-23 21:38:53.301890373 +0300:2017-11-23 
21:38:54.301890373 +0300:/var/crash/apport.0.crash
   600:109:117:0:2017-11-17 08:38:35.616198602 +0300:2017-11-17 
08:38:35.616198602 +0300:/var/crash/apport.0.uploaded
   644:0:117:0:2017-11-17 08:38:33.960180714 +0300:2017-11-17 
08:38:33.960180714 +0300:/var/crash/apport.0.upload
  Date: Thu Nov 23 23:38:54 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-10-20 (34 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Nish Aravamudan]

Is this already fixed in proposed (MRE to latest upstream php 7.0 and
7.1)?

On Dec 1, 2017 03:48, "Bug Watch Updater" <1734...@bugs.launchpad.net>
wrote:

> ** Changed in: php7.0 (Debian)
>Status: Unknown => New
>
> --
> You received this bug notification because you are subscribed to php7.1
> in Ubuntu.
> Matching subscriptions: PHP7.0
> https://bugs.launchpad.net/bugs/1734967
>
> Title:
>   tzdata info for WGT/WGST broken
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+subscriptions
>

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid
Status in php7.0 package in Debian:
  New

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 1200296] Re: [MIR] spice-vdagent

[Seth Arnold]

I reviewed spice-vdagent 0.17.0-1ubuntu1 as checked into zesty. This
shouldn't be considered a full audit but rather a quick gauge of
maintainability.

spice-vdagent provides some services between virtual machine host and
guests to make the experience less jarring.

One CVE is in our database for the Windows client.

- Build-Depends: debhelper, pkg-config, dh-systemd, libspice-protocol-dev,
  libdbus-1-dev, libx11-dev, libxrandr-dev, libxfixes-dev,
  desktop-file-utils, libxinerama-dev, libpciaccess-dev, autoconf, automake,
  libglib2.0-dev, systemd, libsystemd-dev, libasound2-dev
- Provides a client and server; both daemonize
- pre/post inst/rm scripts automatically generated
- spice-vdagent init script starts the guest daemon, modprobes uinput
- spice-vdagentd and spice-vdagent systemd service files, start their
  daemons
- no dbus services
- No setuid or setgid files
- Two executables in PATH /usr/bin/spice-vdagent and
  /usr/sbin/spice-vdagentd
- No sudo fragments
- One udev rule for virtio-ports
- No test suite
- No cron
- Clean build logs

- Subprocesses spawned using system(), unsafe construction, reported
  upstream
- Memory management looked good enough; some cases of malloc(a*b) but 'b'
  was often 4, 8, maybe 16, and 'a' calculated from data on the wire in a
  fashion that looked difficult to really abuse.
- File IO looked safe except for uses of system()
- Logging looked safe
- No environment variable use
- chmod(socket, 0666) looked out of place
- other privileged ioctl() calls looked fine
- No cryptography
- Does networking; a quick skim looked like all Unix Domain Sockets
- I didn't see privileged portions of the code
- No tmp files
- No WebKit
- No PolicyKit
- Clean cppcheck


Here's some notes I collected while reviewing spice-vdagent:

- vdagent_file_xfers_data() does not escape xfers->save_dir before giving
  it to the shell (CVE-2017-15108 was assigned for this issue)
- vdagent_file_xfers_data() does not check snprintf() return code; a
  too-long xfers->save_dir could cause the & or ' or any number of other
  characters to go missing.
- daemonize() from ./src/vdagentd.c only forks once
- daemonize() from ./src/vdagent.c only forks once
- why does main() in ./src/vdagentd.c set vdagentd_socket to 0666


This symlink looks out of place:

/usr/share/gdm/greeter/autostart/spice-vdagent.desktop ->
/etc/xdg/autostart/spice-vdagent.desktop

Please make sure
https://cgit.freedesktop.org/spice/linux/vd_agent/commit/?id=8ba174816d245757e743e636df357910e1d5eb61
is included in our package before promoting the package.

Security team ACK for promoting spice-vdagent to main.

Thanks


** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15108

** Changed in: spice-vdagent (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] spice-vdagent

Status in spice-vdagent package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Availability
  
  Built for all supported architectures.

  In sync with Debian except for one cherry-picked patch to hide spice-
  vdagent from Startup Applications.

  Rationale
  =
  "spice-vdagent adds some nice features to guest systems running over SPICE: 
copy and paste between guest and host, arbitrary resolution support, ... It's 
also very tiny (40kB compressed, less than 200kB installed) and won't startup 
when not running in a SPICE guest.
  Shipping it on the desktop ISOs will improve the user experience when using 
SPICE (eg in GNOME Boxes), and will have no impact on other use cases, so it 
would be really nice to add this package to the ISO."

  Ubuntu GNOME 16.10 and 17.04 included it in the default install.

  Security
  
  No known open security vulnerabilities.

  https://rhn.redhat.com/errata/RHSA-2013-0924.html (CVE-2013-2152)

  Quality assurance
  =
  Bug subscriber: Ubuntu Desktop Bugs

  https://bugs.launchpad.net/ubuntu/+source/spice-vdagent
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=spice-vdagent
  https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__&component=unix 
agent&product=Spice

  No tests.

  Dependencies
  
  check-mir reports all other binary dependencies are in main

  Standards compliance
  
  3.9.8

  Maintenance
  ===
  - Actively developed upstream
  https://cgit.freedesktop.org/spice/linux/vd_agent/log/
  https://anonscm.debian.org/git/collab-maint/spice-vdagent.git

  - Maintained in Debian by the same Debian Developer who maintains the
  other Spice packages.

  short dh7 style rules, dh compat 10

  Background information
  ==
  N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1

[Touch-packages] [Bug 1038578] Re: vlc crash

[Launchpad Bug Tracker]

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

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

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

Title:
  vlc crash

Status in libproxy package in Ubuntu:
  Expired
Status in vlc package in Ubuntu:
  Expired

Bug description:
  1

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.3-1
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu8
  Architecture: i386
  Date: Sun Aug 19 08:05:28 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203)
  ProcCmdline: /usr/bin/vlc file://[...]/video.avi
  Signal: 6
  SourcePackage: vlc
  UpgradeStatus: Upgraded to quantal on 2012-07-30 (20 days ago)
  UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

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

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

[Touch-packages] [Bug 1038578] Re: vlc crash

[Launchpad Bug Tracker]

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

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

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

Title:
  vlc crash

Status in libproxy package in Ubuntu:
  Expired
Status in vlc package in Ubuntu:
  Expired

Bug description:
  1

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.3-1
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu8
  Architecture: i386
  Date: Sun Aug 19 08:05:28 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203)
  ProcCmdline: /usr/bin/vlc file://[...]/video.avi
  Signal: 6
  SourcePackage: vlc
  UpgradeStatus: Upgraded to quantal on 2012-07-30 (20 days ago)
  UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

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

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

[Touch-packages] [Bug 1735649] [NEW] not sure

[Kenneth Wright]

Public bug reported:

seriously I've no idea

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-49-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Dec  1 00:13:04 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1094]
InstallationDate: Installed on 2017-03-19 (257 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:57f3 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=80176af4-8ce5-4fc0-8f62-7b7cbba90c42 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd04/26/2016:svnAcer:pnAspireE5-575:pvrV1.04:rvnAcer:rnIronman_SK:rvrV1.04:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-575
dmi.product.version: V1.04
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Nov 30 21:46:06 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  not sure

Status in xorg package in Ubuntu:
  New

Bug description:
  seriously I've no idea

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec  1 00:13:04 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1094]
  InstallationDate: Installed on 2017-03-19 (257 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57f3 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=80176af4-8ce

[Touch-packages] [Bug 1722434] Re: stack frame size detection is broken

[Bug Watch Updater]

** Changed in: pcre3 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  stack frame size detection is broken

Status in pcre3 package in Ubuntu:
  Fix Released
Status in pcre3 package in Debian:
  Fix Released

Bug description:
  As reported in https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=878107

  The patch, as Ondřej says, clearly shouldn't be able to make anything
  worse, appears likely to fix the current mariadb-10.1 dep8 failure on
  s390x and ppc64el, and likely may fix other latent bugs on those
  architectures, so I intend to upload it.

  I think it's possible that the fix will also fix the current FTBFS
  (bug 1718373). If it doesn't, then the FTBFS will remain, but I don't
  think the package state will be any worse with this patch in it.

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

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

Re: [Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Ryan Harper]

Dec 01 05:07:25.679368 ubuntu systemd-udevd[474]: LINK
'disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869'
/lib/udev/rules.d/60-persistent-storage.rules:79
Dec 01 05:07:25.683008 ubuntu systemd-udevd[474]: WARK:
dev_old_name=/dev/bcache/by-uuid/92d882d8-38cd-4537-847b-6f9c40ba67b4
dev_old_path=/devices/virtual/block/bcache0
Dec 01 05:07:25.683042 ubuntu systemd-udevd[474]: WARK:
dev_name=/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869
dev_path=/devices/virtual/block/bcache0
Dec 01 05:07:25.683066 ubuntu systemd-udevd[474]: WARK:
streq(name=/dev/bcache/by-uuid/92d882d8-38cd-4537-847b-6f9c40ba67b4,
name_current=/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869)
Dec 01 05:07:25.683076 ubuntu systemd-udevd[474]: update old name,
'/dev/bcache/by-uuid/92d882d8-38cd-4537-847b-6f9c40ba67b4' no longer
belonging to '/devices/virtual/block/bcache0'
Dec 01 05:07:25.683085 ubuntu systemd-udevd[474]: WARK:
link_update(name=/dev/bcache/by-uuid/92d882d8-38cd-4537-847b-6f9c40ba67b4,
false
Dec 01 05:07:25.683094 ubuntu systemd-udevd[474]: no reference left, remove
'/dev/bcache/by-uuid/92d882d8-38cd-4537-847b-6f9c40ba67b4'
Dec 01 05:07:25.683104 ubuntu systemd-udevd[474]: WARK:
dev_old_name=/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869
dev_old_path=/devices/virtual/block/bcache0
Dec 01 05:07:25.683113 ubuntu systemd-udevd[474]: WARK:
dev_name=/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869
dev_path=/devices/virtual/block/bcache0
Dec 01 05:07:25.683122 ubuntu systemd-udevd[474]: WARK:
streq(name=/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869,
name_current=/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869)
Dec 01 05:07:25.683131 ubuntu systemd-udevd[474]: WARK: found match!
continue
Dec 01 05:07:25.683146 ubuntu systemd-udevd[474]: handling device node
'/dev/bcache0', devnum=b250:0, mode=0660, uid=0, gid=6
Dec 01 05:07:25.683155 ubuntu systemd-udevd[474]: set permissions
/dev/bcache0, 060660, uid=0, gid=6
Dec 01 05:07:25.683165 ubuntu systemd-udevd[474]: preserve already existing
symlink '/dev/block/250:0' to '../bcache0'
Dec 01 05:07:25.683174 ubuntu systemd-udevd[474]: found 'b250:0' claiming
'/run/udev/links/\x2fdisk\x2fby-uuid\x2f0a270acb-56b8-4498-8bad-b3bb149fe869'
Dec 01 05:07:25.683183 ubuntu systemd-udevd[474]: creating link
'/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869' to '/dev/bcache0'
Dec 01 05:07:25.683193 ubuntu systemd-udevd[474]: preserve already existing
symlink '/dev/disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869' to
'../../bcache0'
Dec 01 05:07:25.683201 ubuntu systemd-udevd[474]: created db file
'/run/udev/data/b250:0' for '/devices/virtual/block/bcache0'
Dec 01 05:07:25.683211 ubuntu systemd[1]:
dev-disk-by\x2duuid-0a270acb\x2d56b8\x2d4498\x2d8bad\x2db3bb149fe869.device:
Changed dead -> plugged
Dec 01 05:07:25.683226 ubuntu systemd[1]: dev-bcache0.device: Changed dead
-> plugged
Dec 01 05:07:25.683234 ubuntu systemd[1]:
sys-devices-virtual-block-bcache0.device: Changed dead -> plugged


The new dev (from /deb/bcache0) only has a by-uuid devlink as the UEVENT
that generates the CACHED_UUID devlink is not recorded/discovered
after the original binding of the cache device and backing store.  This
forces udev to remove the link.

I hacked in a change which allows the old link to stay if the old_name, or
old_path match; this
keeps the symlinks around.

This is required (or the kernel fix to emit the CACHED_UUID on cold plug);
but not sufficient.
What else is needed is a change to the bcache rules file such that when a
bcacheN device is
replugged, it will query the backing device's superblock to find out the
dev.uuid, and import that
value as CACHED_UUID so that the dname rule can match the path
/dev/bcache/by-uuid/ and dname
will point to that, which abstracts away whether it points to bcache0, 1 ,
or N.

/dev/disk/by-dname/foo -> ../../../bcache/by-uuid/  ->
../../bcacheN



On Thu, Nov 30, 2017 at 7:16 PM, Ryan Harper 
wrote:

> It looks like there is some ordering issues:
>
> This is a grep through /run/udev/links ; these are checked by udev-dev
>
> # find . -name 'b250*'
> ./\x2fdisk\x2fby-uuid\x2f0a270acb-56b8-4498-8bad-b3bb149fe869/b250:1
> ./\x2fdisk\x2fby-uuid\x2f92b0868d-7e56-4956-8e55-2c90ebee4a72/b250:0
> ./\x2fbcache\x2fby-uuid\x2f92d882d8-38cd-4537-847b-6f9c40ba67b4/b250:1
> ./\x2fbcache\x2fby-uuid\x2f57e009b1-6bf4-42ea-abe0-334b10941a0b/b250:0
>
> So both /dev/bcache/by-uuid and /dev/disk/by-uuid both point to the bcache
> device (b250:0)
>
> udevd shows this:
>
> Nov 30 23:39:10.738290 ubuntu systemd-udevd[465]: LINK
> 'disk/by-uuid/0a270acb-56b8-4498-8bad-b3bb149fe869' /lib/udev/rules.d/60-
> persistent-storage.rules:79
> Nov 30 23:39:10.738304 ubuntu systemd-udevd[465]: update old name,
> '/dev/bcache/by-uuid/92d882d8-38cd-4537-847b-6f9c40ba67b4' no longer
> belonging to '/devices/virtual/block/bcache1'
> Nov 30 23:39:10.738321 ubuntu systemd-udevd[465]: no reference left,
> remove '/dev/bcache/by-uuid/92d882d8-38cd-4537-847b-6f9c40ba67b4'