date:20171005

Public bug reported:

Settings list separators conflict visually with list item backgrounds.

The separators should be more visually significant than the things they
are separating, however the Ubuntu theme is using alternating light/dark
backgrounds which drown out the separators.

Screenshot attached.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
Date: Fri Oct  6 13:38:00 2017
InstallationDate: Installed on 2017-05-03 (156 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-themes
 Importance: Low
 Status: New

** Affects: gnome-control-center (Ubuntu)
 Importance: Low
 Status: New

** Affects: ubuntu-themes (Ubuntu)
 Importance: Low
 Status: New


** Tags: amd64 apport-bug artful third-party-packages visual-quality

** Attachment added: "Screenshot from 2017-10-06 13-35-14.png"
   
https://bugs.launchpad.net/bugs/1721693/+attachment/4963345/+files/Screenshot%20from%202017-10-06%2013-35-14.png

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

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

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

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

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

Title:
  Settings list separators conflict visually with list item backgrounds

Status in Ubuntu theme:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Settings list separators conflict visually with list item backgrounds.

  The separators should be more visually significant than the things
  they are separating, however the Ubuntu theme is using alternating
  light/dark backgrounds which drown out the separators.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Fri Oct  6 13:38:00 2017
  InstallationDate: Installed on 2017-05-03 (156 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721693] Re: Settings list separators conflict visually with list item backgrounds

That's strange. The colour profile is different (despite having none
configured and using identical monitors). The list backgrounds look
darker on the 17.10 Wayland machine I took the screenshot on, than on my
16.04 desktop I'm now viewing the image on.

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

Title:
  Settings list separators conflict visually with list item backgrounds

Status in Ubuntu theme:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Settings list separators conflict visually with list item backgrounds.

  The separators should be more visually significant than the things
  they are separating, however the Ubuntu theme is using alternating
  light/dark backgrounds which drown out the separators.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Fri Oct  6 13:38:00 2017
  InstallationDate: Installed on 2017-05-03 (156 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

The Xenial and Zesty kernel patch sets have been sent to the kernel
team:

https://lists.ubuntu.com/archives/kernel-team/2017-October/087448.html
https://lists.ubuntu.com/archives/kernel-team/2017-October/087456.html

I've uploaded a libseccomp SRU to zesty-proposed. The Xenial SRU is
going to be trickier. It may require bring Zesty's libseccomp back to
Xenial due to the current version of libseccomp in Xenial not fully
supporting the seccomp(2) system call. That system call is needed to
verify kernel support of the SECCOMP_RET_LOG action that's needed for
devmode.

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in libseccomp source package in Zesty:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument

  [Linux Kernel Test Case]

  All

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

** Description changed:

  A requirement for snappy is that a snap may be placed in developer mode
  which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make developing
  on snappy easier.
  
  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we
  can set complain mode to permit all calls, they are not logged at this
  time. I've discussed this with upstream and we are working together on
  the approach. This may require a kernel patch and an update to
  libseccomp, to filing this bug for now as a placeholder and we'll add
  other tasks as necessary.
  
  UPDATE: ubuntu-core-launcher now supports the '@complain' directive that
  is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).
  
  [Impact]
  
  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).
  
  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a
  number of new symbols and probably isn't appropriate to backport until
  upstream has acked the pull request. However, only a small part of that
  larger pull request is needed by snapd and that change can be safely
  backported since the only added symbol, the SCMP_ACT_LOG macro, must
  match the SECCOMP_RET_LOG macro that has already been approved and
  merged in the upstream Linux kernel.
  
  [libseccomp Test Case]
  
  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised to
  help catch any regressions. Note that on Artful, there's an existing
  test failure (20-live-basic_die%%002-1):
  
  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  
  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  
  
  
  
  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:
  
  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test
  
  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:
  
  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test"
  sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc
  
  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:
  
  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument
  
  [Linux Kernel Test Case]
  
  All of the libseccomp test cases apply here.
  
  
  
  Running the seccomp kernel selftests is also a great to exercise seccomp
  and the kernel patch set proposed for the SRU includes additional
  seccomp selftests. To build, enter into the root of the kernel source
  tree and build the seccomp test binary:
  
  $ make -C tools/testing/selftests TARGETS=seccomp
  
  Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or even
  copy it to a test machine and run it there. On Xenial, 54/54 tests
  should pass and 58/58 should pass on Zesty.
  
+ 
+ 
+ Now we can run a single test to verify that SECCOMP_RET_LOG is logged
+ when the seccomp BPF evaluates to that action. First, verify that "log"
+ is listed in the actions_logged sysctl:
+ 
+ $ cat /proc/sys/kernel/seccomp/actions_logged
+ kill trap errno trace log
+ 
+ Now, build and run the test program:
+ 
+ $ gcc -o lp1567597-kernel-test lp1567597-kernel-test.c
+ $ ./1567597-kernel-test
+ SUCCESS!
+ 
+ It should have generated a message like this in /var/log/syslog:
+ 
+ audit: type=1326 audit(1507263417.752:60): auid=1000 uid=1000

[Touch-packages] [Bug 1411581] Re: HP CP4525 printer confused by evince (libcairo 1.13.0~20140204-0ubuntu1) font naming mismatch

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

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

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

Title:
  HP CP4525 printer confused by evince (libcairo
  1.13.0~20140204-0ubuntu1) font naming mismatch

Status in cairo package in Ubuntu:
  Expired

Bug description:
  I have an HP Color LaserJet Enterprise CP4525 with firmware 07.164.1,
  which supports PDF files natively (@PJL LANGUAGE=PDF), and a print
  server running Debian 7 (cups-filters 1.0.18 and its pdftopdf, and a
  PDF-enabled PPD).

  I have been given a PDF file (from pdflatex) that uses four Type 1
  font subsets (of four different simple fonts). This file gets printed
  correctly with /usr/bin/lp . Not so when using evince on Ubuntu
  trusty: then the printer substitutes a different font (but keeping the
  glyph widths from the font object in the PDF file, so the letter
  spacings look all wrong).

  I've inspected the PDF file evince sends to the printer (which is not
  identical to the original PDF file: evince rewrites it) and noticed
  that the value of /FontName in the font program object doesn't match
  that of /FontName in the font descriptor object; the latter does match
  /BaseFont in the font object and has the form prescribed in §9.6.4 of
  the PDF 1.7 specification for font subsets. The /FontName in the font
  program object, on the other hand, is of the form /CairoFont-N-M,
  where N and M are integers.

  If I hand-edit the PDF output by evince, replacing /CairoFont-N-M with
  the value of /FontName in the corresponding font descriptor object
  (and adjusting /Length and /Length1 as needed), the result gets
  printed with the correct fonts.

  §9.6.2.1 of the PDF 1.7 specification (PDF 32000-1:2008, retrieved
  from Adobe's web site) does say that "[f]or Type 1 fonts, [BaseFont]
  is always the value of the FontName entry in the font program". One
  wonders, then, why Cairo changes the name. I could understand it if it
  wanted to make the font descriptors for two different subsets of the
  same font share the same font program object; but it doesn't take
  advantage of this. The sample file I have contains ligatures and
  accented letters, originally represented in a single font subset by
  using a non-standard encoding, and evince splits these font subsets
  into two parts, one of which uses /WinAnsiEncoding; each of the
  subsets gets its own font program object (with a different value of M
  in /CairoFont-N-M). So this is not the explanation.

  I think it would be prudent, in light of HP's PDF interpreter's
  behaviour, for Cairo to adhere more strictly to the wording of
  §9.6.2.1 and use the same /FontName in the font program object as in
  the font descriptor object.

  I think I'd also like for pdftopdf to incorporate a workaround for
  this, simply because I have more control over the print server than
  over the clients. But that's for another (wishlist) bug report.

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

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

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

** Description changed:

  A requirement for snappy is that a snap may be placed in developer mode
  which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make developing
  on snappy easier.
  
  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we
  can set complain mode to permit all calls, they are not logged at this
  time. I've discussed this with upstream and we are working together on
  the approach. This may require a kernel patch and an update to
  libseccomp, to filing this bug for now as a placeholder and we'll add
  other tasks as necessary.
  
  UPDATE: ubuntu-core-launcher now supports the '@complain' directive that
  is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).
  
  [Impact]
  
  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).
  
  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a
  number of new symbols and probably isn't appropriate to backport until
  upstream has acked the pull request. However, only a small part of that
  larger pull request is needed by snapd and that change can be safely
  backported since the only added symbol, the SCMP_ACT_LOG macro, must
  match the SECCOMP_RET_LOG macro that has already been approved and
  merged in the upstream Linux kernel.
  
- [Test Case]
+ [libseccomp Test Case]
  
  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised to
  help catch any regressions. Note that on Artful, there's an existing
  test failure (20-live-basic_die%%002-1):
  
  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  
  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  
  
+ 
+ 
  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:
  
  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test
  
  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:
  
  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test"
  sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc
  
  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:
  
  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument
  
+ [Linux Kernel Test Case]
+ 
+ All of the libseccomp test cases apply here.
+ 
+ 
+ 
+ Running the seccomp kernel selftests is also a great to exercise seccomp
+ and the kernel patch set proposed for the SRU includes additional
+ seccomp selftests. To build, enter into the root of the kernel source
+ tree and build the seccomp test binary:
+ 
+ $ make -C tools/testing/selftests TARGETS=seccomp
+ 
+ Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or even
+ copy it to a test machine and run it there. On Xenial, 54/54 tests
+ should pass and 58/58 should pass on Zesty.
+ 
  [Regression Potential]
  
  Relatively small since the core logic is in the kernel and we're only
  exposing the new action through libseccomp. The changes include smarts
  to query the kernel to see if the action is available in the kernel.
  Calling applications will not be able to use the action on older kernels
  that don't support it.

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

Title:
  implement 'complain mode'

[Touch-packages] [Bug 1721677] [NEW] package sudo 1.8.20p2-1ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2017-10-05 Thread rbmorse

Public bug reported:

This started as an automated report.  As the machine prepared it for
submission, it occurs to me the problem could be operator error...I may
have not logged into the proper environment (GNOME plus Xorg).

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: sudo 1.8.20p2-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
AptOrdering:
 gksu:amd64: Remove
 ubuntu-minimal:amd64: Remove
 sudo:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Oct  5 16:42:56 2017
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
InstallationDate: Installed on 2017-09-27 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.2-1ubuntu4
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: sudo
Title: package sudo 1.8.20p2-1ubuntu1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK

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

Title:
  package sudo 1.8.20p2-1ubuntu1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  This started as an automated report.  As the machine prepared it for
  submission, it occurs to me the problem could be operator error...I
  may have not logged into the proper environment (GNOME plus Xorg).

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: sudo 1.8.20p2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  AptOrdering:
   gksu:amd64: Remove
   ubuntu-minimal:amd64: Remove
   sudo:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Oct  5 16:42:56 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-09-27 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.2-1ubuntu4
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sudo
  Title: package sudo 1.8.20p2-1ubuntu1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

** Changed in: snappy
   Status: Confirmed => In Progress

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in libseccomp source package in Zesty:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument

  [Regression Potential]

  Relatively small since the core logic is in the kernel and we're only
  exposing the new action through libseccomp. The changes include smarts
  to query the kernel to see if the action is available in the kernel.
  Calling applications will not be able to use the action on older
  kernels that don't support it.

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

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

[Touch-packages] [Bug 1720256] Re: Wrong display of fonts in Gnome Tweak Tool after installing cantarell fonts

This bug was fixed in the package glib2.0 - 2.54.1-1ubuntu1

---
glib2.0 (2.54.1-1ubuntu1) artful; urgency=medium

  * Merge with debian, remaining changes: (LP: #1701780)
- exp_git_default_per_desktop*.patch:
  + cherry-pick per-desktop overrides from GNOME #786496
Allison confirmed the patches will be committed to glib soon
  * debian/patches/01_gettext-desktopfiles.patch:
- support desktop file action group translations (LP: #1711752)
  * exp_git_default_per_desktop*.patch:
- refresh and add exp_git_default_per_desktop4.pathc to fix some
  applications using a different way to access the default value
  for a key, and thus, getting a different result which
  doesn't take the per session override in action. Thanks Alberts!
  (LP: #1720256)

glib2.0 (2.54.1-1) unstable; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release
  * Bump Standards-Version to 4.1.1

  [ Michael Biebl ]
  * Drop uploaders.mk include as it breaks the clean target.
Updating the Uploaders list is already handled by the gnome dh addon.

 -- Didier Roche   Wed, 04 Oct 2017 15:49:24 +0200

** Changed in: glib2.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Wrong display of fonts in Gnome Tweak Tool after installing cantarell
  fonts

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  When cantarell fonts are installed, Gnome Tweak Tools shows as if
  "Cantarell" was the font being used when it is actually "Ubuntu".
  Before that, it showed "None".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1720256/+subscriptions

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

[Touch-packages] [Bug 1711752] Re: Some right click items are untranslated

This bug was fixed in the package glib2.0 - 2.54.1-1ubuntu1

---
glib2.0 (2.54.1-1ubuntu1) artful; urgency=medium

  * Merge with debian, remaining changes: (LP: #1701780)
- exp_git_default_per_desktop*.patch:
  + cherry-pick per-desktop overrides from GNOME #786496
Allison confirmed the patches will be committed to glib soon
  * debian/patches/01_gettext-desktopfiles.patch:
- support desktop file action group translations (LP: #1711752)
  * exp_git_default_per_desktop*.patch:
- refresh and add exp_git_default_per_desktop4.pathc to fix some
  applications using a different way to access the default value
  for a key, and thus, getting a different result which
  doesn't take the per session override in action. Thanks Alberts!
  (LP: #1720256)

glib2.0 (2.54.1-1) unstable; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release
  * Bump Standards-Version to 4.1.1

  [ Michael Biebl ]
  * Drop uploaders.mk include as it breaks the clean target.
Updating the Uploaders list is already handled by the gnome dh addon.

 -- Didier Roche   Wed, 04 Oct 2017 15:49:24 +0200

** Changed in: glib2.0 (Ubuntu Artful)
   Status: Triaged => Fix Released

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

Title:
  Some right click items are untranslated

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Artful:
  Fix Released

Bug description:
  When clicking the icons of Terminal, Nautilus etc., some things are
  being shown as the untranslated (English) strings even though they are
  translated upstream (GNOME). For example the "New Terminal" for GNOME
  Terminal, that is correctly translated (in Czech localization) as
  "Nový terminál" in GNOME panel, but untranslated when clicking the
  GNOME Terminal icon in the ubuntu-dock extension. Another example is
  the "New Window" item in Nautilus. See the attached screenshots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1711752/+subscriptions

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

[Touch-packages] [Bug 1701780] Re: GTK file chooser shows entries from /sys, /dev, etc.

This bug was fixed in the package glib2.0 - 2.54.1-1ubuntu1

---
glib2.0 (2.54.1-1ubuntu1) artful; urgency=medium

  * Merge with debian, remaining changes: (LP: #1701780)
- exp_git_default_per_desktop*.patch:
  + cherry-pick per-desktop overrides from GNOME #786496
Allison confirmed the patches will be committed to glib soon
  * debian/patches/01_gettext-desktopfiles.patch:
- support desktop file action group translations (LP: #1711752)
  * exp_git_default_per_desktop*.patch:
- refresh and add exp_git_default_per_desktop4.pathc to fix some
  applications using a different way to access the default value
  for a key, and thus, getting a different result which
  doesn't take the per session override in action. Thanks Alberts!
  (LP: #1720256)

glib2.0 (2.54.1-1) unstable; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release
  * Bump Standards-Version to 4.1.1

  [ Michael Biebl ]
  * Drop uploaders.mk include as it breaks the clean target.
Updating the Uploaders list is already handled by the gnome dh addon.

 -- Didier Roche   Wed, 04 Oct 2017 15:49:24 +0200

** Changed in: glib2.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GTK file chooser shows entries from /sys, /dev, etc.

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted
  entries from /sys, /dev, etc. For me, this occurs in the GTK3 file
  chooser opened from Firefox, GNOME Disks, etc. At the time of writing,
  I haven't tested whether it occurs in the GTK2 chooser as well. I have
  attached a screenshot showing the problem.

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

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

[Touch-packages] [Bug 1696499] Re: dhclient segfaults on ubuntu 17.04

Actually, I was able to connect with the exact same fix I used for the
cups issue:

add

@{PROC}/*/cmdline r,

to /etc/apparmor.d/sbin.dhclient

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

Title:
  dhclient segfaults on ubuntu 17.04

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  After upgrading, network-manager stopped running DHCP, after trying to
  run dhclient myself I found out it segfaults. Attached is its strace
  output.

  I can connect to the internet by stopping network-manager and using
  ifconfig + route + /etc/resolv.conf.

  Output:
  guy@golem4:~$ dhclient
  Segmentation fault (core dumped)

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

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

[Touch-packages] [Bug 1696499] Re: dhclient segfaults on ubuntu 17.04

The workaround was certainly helpful, but is there a more elegant
solution? I had similar apparmor problem with cupsd (bug 1706052), which
I worked around using the solution here, which eventually led to a fix
via editing the cups apparmor profile.

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

Title:
  dhclient segfaults on ubuntu 17.04

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  After upgrading, network-manager stopped running DHCP, after trying to
  run dhclient myself I found out it segfaults. Attached is its strace
  output.

  I can connect to the internet by stopping network-manager and using
  ifconfig + route + /etc/resolv.conf.

  Output:
  guy@golem4:~$ dhclient
  Segmentation fault (core dumped)

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

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

[Touch-packages] [Bug 1714866] Re: Update libproxy to 0.4.15

2017-10-05 Thread Jeremy Bicha

Since I wasn't able to test this much and Debian doesn't have this
version and it's not a high priority update, let's wait until 18.04 LTS.

I'm unsubscribing ubuntu-release now.

** Also affects: libproxy (Ubuntu Artful)
   Importance: Wishlist
   Status: Confirmed

** Also affects: libproxy (Ubuntu Bb-series)
   Importance: Undecided
   Status: New

** Changed in: libproxy (Ubuntu Artful)
   Status: Confirmed => Won't Fix

** Changed in: libproxy (Ubuntu Bb-series)
   Status: New => Triaged

** Changed in: libproxy (Ubuntu Bb-series)
   Importance: Undecided => Wishlist

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

Title:
  Update libproxy to 0.4.15

Status in libproxy package in Ubuntu:
  Confirmed
Status in libproxy source package in Artful:
  Won't Fix
Status in libproxy source package in bb-series:
  Triaged

Bug description:
  https://github.com/libproxy/libproxy/releases

  Big change here is updating the dependency from mozjs185 (from Firefox
  4!) to mozjs38. libproxy1-plugin-mozjs is in universe and has no
  Ubuntu reverse dependencies (Debian Edu uses it for something though.)

  I don't have any proxies so I haven't tested this beyond making sure
  it builds.

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Thanks BTW, good work.

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

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Here's what we've got so far:
Cups is back online and working in enforce mode. No errors are thrown, no crash 
reports.
HPLIP toolbox shows the printer and the right information.
I am able to print.

So far, so good.

However, hplip-systray is not playing along. The icon appears, but it is
functionless, nothing appears on click. Apparmor's not complaining, but
/var/log is getting flooded with hundreds of messages originating from
hplip-systray. Is this a separate or related issue?

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

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1721655] [NEW] a mistype of the kernel version can do you in

Public bug reported:

I mistyped the kernel version when running update-initramfs e.g.:

sudo update-initramfs -u -k 4.1.3.0-11-generic
[sudo] password for bdmurray: 
update-initramfs: Generating /boot/initrd.img-4.1.3.0-11-generic
WARNING: missing /lib/modules/4.1.3.0-11-generic
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.1.3.0-11-generic: No 
such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_MQwUHq/lib/modules/4.1.3.0-11-generic/modules.order: No 
such file or directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_MQwUHq/lib/modules/4.1.3.0-11-generic/modules.builtin: No 
such file or directory

I now have a bad(?) initrd in my /boot partition:

ls -lh /boot
...
-rw-r--r-- 1 root root 8.8M Oct  5 15:10 initrd.img-4.1.3.0-11-generic
-rw-r--r-- 1 root root  32M Oct  4 14:46 initrd.img-4.13.0-11-generic
-rw-r--r-- 1 root root  32M Oct  4 14:49 initrd.img-4.13.0-12-generic
...

And that version number was written to /var/lib/initramfs-tools/, so
every time update-initramfs is run that bad(?) initrd will be recreated.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: initramfs-tools 0.125ubuntu11
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct  5 15:14:04 2017
InstallationDate: Installed on 2016-01-22 (622 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-bug artful wayland-session

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  a mistype of the kernel version can do you in

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I mistyped the kernel version when running update-initramfs e.g.:

  sudo update-initramfs -u -k 4.1.3.0-11-generic
  [sudo] password for bdmurray: 
  update-initramfs: Generating /boot/initrd.img-4.1.3.0-11-generic
  WARNING: missing /lib/modules/4.1.3.0-11-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.1.3.0-11-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_MQwUHq/lib/modules/4.1.3.0-11-generic/modules.order: No 
such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_MQwUHq/lib/modules/4.1.3.0-11-generic/modules.builtin: No 
such file or directory

  I now have a bad(?) initrd in my /boot partition:

  ls -lh /boot
  ...
  -rw-r--r-- 1 root root 8.8M Oct  5 15:10 initrd.img-4.1.3.0-11-generic
  -rw-r--r-- 1 root root  32M Oct  4 14:46 initrd.img-4.13.0-11-generic
  -rw-r--r-- 1 root root  32M Oct  4 14:49 initrd.img-4.13.0-12-generic
  ...

  And that version number was written to /var/lib/initramfs-tools/, so
  every time update-initramfs is run that bad(?) initrd will be
  recreated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu11
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct  5 15:14:04 2017
  InstallationDate: Installed on 2016-01-22 (622 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-10-05 Thread bugproxy

--- Comment From lagar...@br.ibm.com 2017-10-05 17:29 EDT---
@JJohansen, any update on this one?

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

I've uploaded fixes to all releases previously identified as worth
fixing which remove the .old-dkms file after its been created.

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

** Changed in: dkms (Ubuntu)
   Status: Fix Released => In Progress

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-failed-xenial verification-failed-zesty

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721626] [NEW] Remove obsolete versioned dependency on initramfs-tools Edit

2017-10-05 Thread Steve Langasek

Public bug reported:

[SRU Justification]
Up until artful, console-setup declares a versioned dependency on 
initramfs-tools. This was an Ubuntu-specific dependency only needed for 
upgrades, and the version referenced is ancient (ca. 2008). In artful and 
later, the dependency has now been removed.

Since this is no longer relevant for upgrades and we would not otherwise
have a dependency on initramfs-tools, we should drop this dependency to
support building of images with initramfs-tools removed for systems that
we know don't require an initramfs.

[Test case]
1. On a xenial default cloud image install, try to run 'sudo apt purge 
initramfs-tools'.
2. Verify that this tries to remove console-setup, console-setup-linux, and kbd.
3. Cancel the removal.
4. Install console-setup from xenial-proposed.
5. Run 'sudo apt purge initramfs-tools' again.
6. Verify that console-setup, console-setup-linux, and kbd are not removed.
7. Run 'sudo apt install --reinstall console-setup' and confirm that the 
package can be installed successfully without initramfs-tools installed.

[Regression Potential]
If a user needs an initramfs in order to mount their root device, and 
console-setup is the only package on their system which depends on 
initramfs-tools, it is possible that the user may remove initramfs-tools and 
render their system unbootable.

This is unlikely because initramfs-tools is still part of the 'minimal'
seed and is therefore a dependency of ubuntu-minimal; and it remains a
dependency of the generic kernel image.

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: console-setup (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Steve Langasek (vorlon)
 Status: In Progress

** Changed in: console-setup (Ubuntu)
   Status: New => Fix Released

** Also affects: console-setup (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: console-setup (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: console-setup (Ubuntu Xenial)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  Remove obsolete versioned dependency on initramfs-tools Edit

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  In Progress

Bug description:
  [SRU Justification]
  Up until artful, console-setup declares a versioned dependency on 
initramfs-tools. This was an Ubuntu-specific dependency only needed for 
upgrades, and the version referenced is ancient (ca. 2008). In artful and 
later, the dependency has now been removed.

  Since this is no longer relevant for upgrades and we would not
  otherwise have a dependency on initramfs-tools, we should drop this
  dependency to support building of images with initramfs-tools removed
  for systems that we know don't require an initramfs.

  [Test case]
  1. On a xenial default cloud image install, try to run 'sudo apt purge 
initramfs-tools'.
  2. Verify that this tries to remove console-setup, console-setup-linux, and 
kbd.
  3. Cancel the removal.
  4. Install console-setup from xenial-proposed.
  5. Run 'sudo apt purge initramfs-tools' again.
  6. Verify that console-setup, console-setup-linux, and kbd are not removed.
  7. Run 'sudo apt install --reinstall console-setup' and confirm that the 
package can be installed successfully without initramfs-tools installed.

  [Regression Potential]
  If a user needs an initramfs in order to mount their root device, and 
console-setup is the only package on their system which depends on 
initramfs-tools, it is possible that the user may remove initramfs-tools and 
render their system unbootable.

  This is unlikely because initramfs-tools is still part of the
  'minimal' seed and is therefore a dependency of ubuntu-minimal; and it
  remains a dependency of the generic kernel image.

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

2017-10-05 Thread Till Kamppeter

Everyone with this problem, can you please add a line

@{PROC}/*/cmdline r,

after the line

@{PROC}/*/auxv r,

in your /etc/apparmor.d/usr.sbin.cupsd file, then run

sudo aa-enforce /usr/sbin/cupsd

and reboot.

Does this solve your problem?

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

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1721619] [NEW] Mouse ignored by Xorg

2017-10-05 Thread Kristian Benoit

Public bug reported:

Resizing a window with the mouse, the pointer got stuck with the
resizing icon. The cursor was still (visually) moving. I used xev to try
figuring out what Xorg was receiving. Weird, xev was reporting nothing,
not even mouse moves (from what I remember, it is not drawn by
software). I have 2 mice and they where both behaving the same. I switch
to console and cat /dev/input/mice, both mice where working fine. I
tried to find a way to reset (only) the pointer but could not find any,
is there ? Then I killed Xorg witch was restarted automatically and the
pointer was fine.

You should have all the hardware info, but I'm using a mac mini 5,1 and
a magic mouse.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu Oct  5 14:41:36 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.10.0-33-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.10.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated 
Graphics Controller [106b:00e6]
InstallationDate: Installed on 2017-09-12 (22 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Apple Inc. Macmini5,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed 
root=UUID=4c66383d-8a7f-4cf8-8e7d-1b0341336e44 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM51.88Z.0077.B14.1510261805
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-8ED6AF5B48C039E1
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini5,1
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-8ED6AF5B48C039E1
dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B14.1510261805:bd10/26/2015:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
dmi.product.name: Macmini5,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
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.14-0ubuntu1
xserver.bootTime: Thu Oct  5 13:01:11 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: modeset

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


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

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

Title:
  Mouse ignored by Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Resizing a window with the mouse, the pointer got stuck with the
  resizing icon. The cursor was still (visually) moving. I used xev to
  try figuring out what Xorg was receiving. Weird, xev was reporting
  nothing, not even mouse moves (from what I remember, it is not drawn
  by software). I have 2 mice and they where both behaving the same. I
  switch to console and cat /dev/input/mice, both mice where working
  fine. I tried to find a way to reset (only) the pointer but could not
  find any, is there ? Then I killed Xorg witch was restarted
  automatically and the pointer was fine.

  You should have all the hardware info, but I'm using a mac mini 5,1
  and a magic mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompositorRunning: compiz

[Touch-packages] [Bug 1679865] Re: coreutils FTBFS during zesty test rebuild

2017-10-05 Thread Tiago Stürmer Daitx

This is caused by a change in the new TZ as reported at [1]. A fix is
provided in [2] but required a small change for the first chunk to apply
cleanly - see attached debdiff.

Other option is to sync the newest version, 8.28-1 [3,4], which includes
the fix upstream and builds cleanly.

[1] http://lists.gnu.org/archive/html/coreutils/2017-03/msg00026.html
[2] http://lists.gnu.org/archive/html/coreutils/2017-03/msg00031.html
[3] http://snapshot.debian.org/package/coreutils/8.28-1/
[4] https://tracker.debian.org/pkg/coreutils

** Patch added: "coreutils_8.26-3ubuntu3_8.26-3ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1679865/+attachment/4963059/+files/coreutils_8.26-3ubuntu3_8.26-3ubuntu3.debdiff

** Changed in: coreutils (Ubuntu)
 Assignee: Matthias Klose (doko) => (unassigned)

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

** Tags added: patch

** Tags added: artful

** Summary changed:

- coreutils FTBFS during zesty test rebuild
+ coreutils FTBFS during zesty/artful test rebuild

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

Title:
  coreutils FTBFS during zesty/artful test rebuild

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  coreutils version 8.26-3ubuntu3 in zesty failed to build on all arches
  during a test rebuild of the archive. The build log can be found here:

  https://launchpadlibrarian.net/312365438/buildlog_ubuntu-zesty-
  amd64.coreutils_8.26-3ubuntu3_BUILDING.txt.gz

  The failure seems to be:

  FAIL: tests/misc/date-debug
  ===

  --- exp3  2017-03-25 05:27:00.477874098 +
  +++ out3  2017-03-25 05:27:00.481874118 +
  @@ -4,4 +4,4 @@
   date: final: 1.0 (epoch-seconds)
   date: final: (Y-M-D) 1970-01-01 00:00:01 (UTC0)
   date: final: (Y-M-D) 1969-12-31 19:00:01 (output timezone TZ=-05:00)
  -Wed Dec 31 19:00:01 PET 1969
  +Wed Dec 31 19:00:01 -05 1969
  FAIL tests/misc/date-debug.sh (exit status: 1)

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

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

[Touch-packages] [Bug 1721600] Re: usb canon pixma g2000 not detected

2017-10-05 Thread Till Kamppeter

Please follow the instructions in the "USB Printer" section on
https://wiki.ubuntu.com/DebuggingPrintingProblems.

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

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

Title:
  usb canon pixma g2000 not detected

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  i bought a new printer that doesn't get detected when i connect to the
  usb port on my computer. doesn't even show any changes happening when
  i track connections to the usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct  5 23:02:33 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-29 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: device for G2000series-TurboPrint: parallel:/dev/lp0
  MachineType: LENOVO 2347CTO
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/G2000series-TurboPrint.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/G2000series-TurboPrint.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET45WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET45WW(1.20):bd08/07/2012:svnLENOVO:pn2347CTO:pvrThinkPadT430:rvnLENOVO:rn2347CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2347CTO
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

The verification of this has failed as the fix was incorrect.

Removing linux-image-4.10.0-19-generic (4.10.0-19.21) ...
Examining /etc/kernel/prerm.d.
run-parts: executing /etc/kernel/prerm.d/dkms 4.10.0-19-generic 
/boot/vmlinuz-4.10.0-19-generic
removed '/boot/initrd.img-4.10.0-19-generic.old-dkms'
dkms: removing: r8168 8.043.02 (4.10.0-19-generic) (x86_64)

 Uninstall Beginning 
Module:  r8168
Version: 8.043.02
Kernel:  4.10.0-19-generic (x86_64)
-

Status: Before uninstall, this module version was ACTIVE on this kernel.

r8168.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.10.0-19-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod...

Backing up initrd.img-4.10.0-19-generic to 
/boot/initrd.img-4.10.0-19-generic.old-dkms
Making new initrd.img-4.10.0-19-generic
(If next boot fails, revert to initrd.img-4.10.0-19-generic.old-dkms image)
update-initramfs...

DKMS: uninstall completed.
Examining /etc/kernel/postrm.d .

The .old-dkms file is removed before a new one is created (see the
Backing up bits). So the remove_initrd_backup run needs to be reordered
for after the dkms call.

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-10-05 Thread Boris Malkov

It already looks like some kind of a tradition for ubuntu to break
something critical in every single release and keep those bugs as long
as possible.

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

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

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

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

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

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu3

---
ntp (1:4.2.8p10+dfsg-5ubuntu3) artful; urgency=medium

  * d/ntp.dhcp add support for parsing systemd networkd lease files LP:
#1717983

 -- Dimitri John Ledkov   Tue, 03 Oct 2017 01:54:33
+0100

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

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  In Progress
Status in controlaula package in Ubuntu:
  New
Status in ddclient package in Ubuntu:
  New
Status in maas package in Ubuntu:
  New
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Fix Released
Status in openresolv package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in samba package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default

Hello Malcolm, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
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!

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

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

Title:
  systemd-resolved: please do not use Google public DNS by default

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the 
absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.

  [Testcase]
  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  Possible workaround/bugfix: ship a resolved.conf which clears the
  FallbackDNS parameter.

  [Solution]
  In ubuntu, we disable fallback DNS at build time, via build system 
configuration flags.

  This issue has been discussed in the Debian BTS
  (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My
  interpretation of the Debian package maintainer's position is that a
  user concerned with the privacy implications shouldn't let systemd get
  into a state where it uses the fallback DNS servers (quoting Marco
  d'Itri: "Short summary: have a resolv.conf file or use DHCP").  I
  would argue that it's safest not to have fallback DNS servers
  configured at all by default.

  [Regression Potential]
  Missconfigured networks, that do not have a DNS server would previously 
magically work due to having Google DNS preconfigured regardless. With this 
change, such network configurations will fail to work, and one will have to 
properly fix network config to point at the right/existing name server.

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

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

[Touch-packages] [Bug 1710410] Re: Must run systemd-resolve --status before DNS resolving is operative

Hello WoJ, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
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!

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

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

Title:
  Must run systemd-resolve --status before DNS resolving is operative

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

Bug description:
  [Impact]
  systemd-resolved is not enabled by default, therefore relies on dbus 
activation to become active and operatable and update resolvconf with resolved 
stub resolver

  [Fix]
  Enable systemd-resolved in the src:systemd package by default, even when 
libnss-resolve is not installed

  [Regression Potential]
  Minimal, simply the service is now started earlier in the boot, as part of 
the multi-user.targer, rather than awaiting for dbus activation from command 
line tool or the nss-resolved module.

  [Testcase]
  Debootstrap minimal zesty, without libnss-resolve package installed, boot and 
check that 127.0.0.53 is present in /etc/resolv.conf and that 
systemd-resolved.service is running

  Context: fresh install of zesty via

  debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
  http://fr.archive.ubuntu.com/ubuntu

  ran via asystemd-nspawn with a static IP

  1. Upon first connexion, a ping fails:

  root@zesty1:~# ping google.com
  ping: google.com: Temporary failure in name resolution

  2. The content of /etc/resolv.conf:

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

  3. When running systemd-resolve --status:

  root@zesty1:~# systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
    8.8.4.4
    2001:4860:4860::
    2001:4860:4860::8844
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
  (...)

  4. After running this command the resolution is miraculously restored:

  root@zesty1:~# ping google.com
  PING google.com (172.217.22.142) 56(84) bytes of data.
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms

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

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

[Touch-packages] [Bug 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

Hello ChristianEhrhardt, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
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!

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

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

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

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

Bug description:
  [Impact]
  A unit with multiple Exec stanzas will loose execution state (which stanzas, 
out of multiple, have executed or not) upon systemd daemon-reload during the 
execution of these stanzas. This results in lost data/state, and units 
potentially failing to start/restart in unpredictable manner

  [Testcase]
  Setup a race of a unit with multiple exec stanzas (e.g. echo, sleep, echo) 
and execute daemon-reload whilst that is in progress. The execution state 
should persist across daemon-reload with all exec stanzas completing, in order, 
without duplicates.

  [Original Bug report]

  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

  [Regression Potential]
  Minimal, this is a fix for incorrect upstream behaviour which resolves a racy 
condition. The code changes are upstream reviewed cherry-pick.

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

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

[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

Hello slodki, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
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!

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

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

Title:
  loginctl ignoring user given sessions IDs at command-line

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  loginctl command does not process session IDs given on the command-line, like 
the documentation suggests. This makes it impossible to use simple command-line 
calls to check properties of a given session. 

  [Fix]
  Backport upstream patch to fix the issue

  [Testcase]
  Use loginctl command and specify multiple session IDs at the command-line and 
verify that details about these sessons are brought up in the output.

  [Regression Potential]
  Minimal, current behaviour is not sane at all, and it is a typpo fix from '1' 
to 'i' meaning that first argument was always used, instead of the current 
iterated one.

  
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

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

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

[Touch-packages] [Bug 1703393] Re: TCP offloads disabled by default

Hello Dimitri, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
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!

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

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

Title:
  TCP offloads disabled by default

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  Regression in systemd v232 resulted in IPv4 TCP segmentation offload ("tso" 
in ethtool) to be disabled by default, yet previously it was enabled.

  [Fix]
  Backport upstream patch to fix the regression

  [Testcase]
  Use ethtool to verify that tso is enabled on e.g. e1000e card with fixed 
package.

  [Regression Potential]
  Link features were incorrectly initialised, this fix changes the 
initialisation code back to the correct default values. This changes the 
defaults back to what they are in all other releases. Users on zesty release 
may have been accustomed to the wrong defaults and may need to adjust .link 
files to e.g. disable tso if that is the behavior they want.

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

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

Hello Ryan, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
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!

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

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

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

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  Fix Committed
Status in nplan source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1709649] Re: 229 backport for race between explicit mount and handling automount

Hello Pegerto, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
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!

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

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

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

Title:
  229 backport for  race between explicit mount and handling automount

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  In systemd prior to 234 a race exists between .mount and .automount units 
such that automount requests from kernel may not be serviced by systemd 
resulting in kernel holding the mountpoint and any processes that try to use 
said mount will hang. A race like this may lead to denial of service, until 
mount points are unmounted.

  [Testcase]
  Create a race between .mount and .automount units, such that automout request 
is serviced after .mount unit has been started. Observe a hang.
  More detailed steps are available at 
https://github.com/systemd/systemd/pull/5916

  [Butfix]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/e7d54bf58789545a9eb0b3964233defa0b007318

  [Regression Potential]
  The underlying logic of starting/stopping/triggering units is unchanged. 
However, there the logic as to when to send automout_send_ready() is relaxed, 
such that it is always sent whenever unit is already mounted. This is done to 
explicitly cope with late arrival of the incoming [aircraft] automount request.

  [Original Bug report / request]

  Hi,

  We have a blocking issue in systemd for the following release

  ```
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  ```

  This release runs systemd229, we are affected by the following auto-
  mouting race condition

  ```
  https://github.com/systemd/systemd/pull/5916
  ```

  Is back porting  the fix to the release 229 an option?

  Regards.

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

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

[Touch-packages] [Bug 1713536] Re: udev: boot script does not trigger subsystem coldplug

Hello bugproxy, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
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!

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

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

Title:
  udev: boot script does not trigger subsystem coldplug

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  subsystems udev rules are not processed on boot, thus resulting in missing 
devices on boot / before rootfs is mounted.

  [Solution]
  trigger udev subsystems and devices, in the initramfs, in that order.

  [Testcase]
  Boot s390x system with chzdev configured devices, and cio_ignore=all kernel 
command line parameter. The chzdev configured devices should still be 
discovered on boot.

  [Original Bug report]

  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

  [Regression Potential]
  More udev rules will be now triggered, earlier, during initramfs stage of 
boot rather than post-pivot-root. However, this is inline with current rootfs 
behaviour and thus should not regress behaviour - simply some rules will get 
triggered earlier.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713536/+subscriptions

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

[Touch-packages] [Bug 1714933] Re: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"

Hello Tobias, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
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!

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

** Tags added: verification-needed-zesty

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

Title:
  Xenial: Please roll SRU with upstream fix for networkd to "accept
  colons in network interface names"

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

Bug description:
  [Impact]
  networkd cannot manage interface names with ':' in them. As used commonly, by 
convention, by other tools.

  [Fix]
  Update networkd validation routines and test-suites to accept network 
interface names with ':' in it.

  [Testcase]
  Create an inteface with ':' in its name and use it anywhere where systemd 
validates ifname. E.g. Socket BindToDevice definition, nspawn network zone 
info, Label= in [Address] section in networkd.

  [Regression Potential]
  This fix will change validation routines, and thus commands or settings that 
were previously rejected or ignored will now take effect. Specifically Label= 
settings in networkd may lead to networking conflicts. The justification for 
this change is that networkd should really use the sensible ':' ifnames that 
the user is requesting systemd to use.

  [Original Bug Reprot]
  PR: https://github.com/systemd/systemd/pull/5117

  issue: https://github.com/systemd/systemd/issues/4057

  Before the networkd from 231 was backported, it was possible to use
  interface alias names that contained a colon, e.g. eth0:1. This is
  commonly used to make legacy tools like "ifconfig" work, because they
  *expect* a colon in the interface name.

  Martin told me to file a bug for this.

  Merging networkd from 231 lead to a regression where valid configs
  were not accepted anymore after the backport. Please merge that fix
  for the regression.

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

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

[Touch-packages] [Bug 1721600] [NEW] usb canon pixma g2000 not detected

2017-10-05 Thread Pawan Dhakal

Public bug reported:

i bought a new printer that doesn't get detected when i connect to the
usb port on my computer. doesn't even show any changes happening when i
track connections to the usb

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4ubuntu0.3
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Oct  5 23:02:33 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-09-29 (6 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lpstat: device for G2000series-TurboPrint: parallel:/dev/lp0
MachineType: LENOVO 2347CTO
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/G2000series-TurboPrint.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/G2000series-TurboPrint.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ET45WW (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2347CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET45WW(1.20):bd08/07/2012:svnLENOVO:pn2347CTO:pvrThinkPadT430:rvnLENOVO:rn2347CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2347CTO
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apparmor apport-bug xenial

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

Title:
  usb canon pixma g2000 not detected

Status in cups package in Ubuntu:
  New

Bug description:
  i bought a new printer that doesn't get detected when i connect to the
  usb port on my computer. doesn't even show any changes happening when
  i track connections to the usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct  5 23:02:33 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-29 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: device for G2000series-TurboPrint: parallel:/dev/lp0
  MachineType: LENOVO 2347CTO
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/G2000series-TurboPrint.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/G2000series-TurboPrint.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET45WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET45WW(1.20):bd08/07/2012:svnLENOVO:pn2347CTO:pvrThinkPadT430:rvnLENOVO:rn2347CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2347CTO
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 278095] RE

2017-10-05 Thread Troels

Check 
[Bug 278095] Re: MASTER crash in getenv() ... spi_atk_bridge_exit_func()

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

Title:
  MASTER crash in getenv() ... spi_atk_bridge_exit_func()

Status in at-spi:
  Expired
Status in apport package in Ubuntu:
  Invalid
Status in at-spi package in Ubuntu:
  Fix Released
Status in firefox-3.0 package in Ubuntu:
  Invalid
Status in apport source package in Intrepid:
  Invalid
Status in at-spi source package in Intrepid:
  Fix Released
Status in firefox-3.0 source package in Intrepid:
  Invalid
Status in apport source package in Jaunty:
  Invalid
Status in at-spi source package in Jaunty:
  Fix Released
Status in firefox-3.0 source package in Jaunty:
  Invalid

Bug description:
  This crash seems to occur most frequently when opening a new URL in an
  existing Firefox process.  The URL is successfully opened, but the
  client process then crashes while exiting.  The result is that the
  operation appears to work, but there has been a crash in the
  background (which is then displayed by update-notifier and apport).

  Steps to reproduce:

  1. check "Enable assisitive technologies"  in Preferences -> Assistive 
Technologies
  2. restart X session
  3. start firefox
  4. start from terminal: firefox http://www.ubuntu.com 

  Result: see crash.

  Verify: with updated package it shouldnt crash.

  ===

  I am using Ubuntu 8.10 beta

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/lib/firefox-3.0.3/firefox
  Package: firefox-3.0 3.0.3+build1+nobinonly-0ubuntu1
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/lib/firefox-3.0.3/firefox 
https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+filebug/7cEBHSr9Xvdab5iSpVMC09PXb6N?field.title=seahorse-agent+crashed+with+SIGSEGV+in+_XIOError%28%29
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: firefox-3.0
  StacktraceTop:
   getenv () from /lib/tls/i686/cmov/libc.so.6
   g_getenv () from /usr/lib/libglib-2.0.so.0
   ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
   exit () from /lib/tls/i686/cmov/libc.so.6
   __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
  Title: firefox crashed with SIGSEGV in getenv()
  Uname: Linux 2.6.27-4-generic i686
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev 
video

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/278095/+subscriptions

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

2017-10-05 Thread Scott Moser

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

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

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  
  Some context from those discussions

  
  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

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

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

[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

2017-10-05 Thread Lawrence A Fossi

After seeing you comment last night I did an apt-get purge of mesa-
vulkan drivers and vulkan-utils then ran apt-get autoremove to remove
libvulkan1 verified that all vulkan related files were gone then
rebooted and reinstalled them.

Mesa upgraded fine to 17.2.2 this morning but the problem remains.
$ apt-cache policy mesa-vulkan-drivers
mesa-vulkan-drivers:
  Installed: 17.2.2-0ubuntu1
  Candidate: 17.2.2-0ubuntu1
  Version table:
 *** 17.2.2-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
100 /var/lib/dpkg/status

vulkan-smoketest
WARNING: radv is not a conformant vulkan implementation, testing use only.
WARNING: radv is not a conformant vulkan implementation, testing use only.
Segmentation fault

from kernel log: Oct  5 10:22:17 Tardis-1 kernel: [ 4445.683796] vulkan-
smoketes[4128]: segfault at 0 ip 7f43321ef924 sp 7ffdee3530a0
error 6 in libvulkan_radeon.so[7f4332183000+18b000]

from syslog: Oct  5 10:22:17 Tardis-1 kernel: [ 4445.683796] vulkan-
smoketes[4128]: segfault at 0 ip 7f43321ef924 sp 7ffdee3530a0
error 6 in libvulkan_radeon.so[7f4332183000+18b000]

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  New

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

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Touch-packages] [Bug 1721578] [NEW] Firefox

2017-10-05 Thread Jukka

Public bug reported:

Firefox does not work properly

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.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: Thu Oct  5 18:38:01 2017
DistUpgraded: 2017-07-12 16:05:47,505 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF104 [GeForce GTX 460] [1043:835d]
InstallationDate: Installed on 2017-07-10 (87 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=fi
 PATH=(custom, no user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-07-12 (85 days ago)
dmi.bios.date: 10/24/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0815
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97
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.:bvr0815:bd10/24/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97: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.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
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.9.0-0ubuntu1
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.14-0ubuntu1
xserver.bootTime: Thu Oct  5 16:54:59 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)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: nouveau

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


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

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

Title:
  Firefox

Status in xorg package in Ubuntu:
  New

Bug description:
  Firefox does not work properly

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.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: Thu Oct  5 18:38:01 2017
  DistUpgraded: 2017-07-12 16:05:47,505 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF104 [GeForce GTX 460] [1043:835d]
  InstallationDate: Installed on 2017-07-10 (87 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-07-12 (85 days ago)
  dmi.bios.date: 10/24/2011
  dmi.bios.vendor: American Megatrends Inc.

[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

2017-10-05 Thread Dan Streetman

the linux-lts-xenial autopkgtest failures are due to that pkg's test
expecting the running kernel == test kernel, which is wrong as trusty is
running stock 3.13 linux in the test, and the linux-lts autopkgtest
doesn't upgrade to linux-lts-* kernel. so unrelated to this change.

e.g.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/linux-lts-xenial/20170929_000420_777ca@/log.gz

...
Source Package Version: 4.4.0-97.120~14.04.1
Running Kernel Version: 3.13.0-133.182
ERROR: running version does not match source package
...

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

Title:
update-initramfs fails for MODULES=dep when root is on LVM wich uses
nvme device

Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Trusty:
Fix Committed

Bug description:
[impact]

On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
initramfs fails to rebuild the initramfs. This prevents using
MODULES=dep for building an initramfs on trusty, with a rootfs that
uses lvm on nvme.

[test case]

install a system where the rootfs uses a LVM logical volume that is
located on a physical volume on a NVMe drive. Edit the /etc
/initramfs-tools/initramfs.conf file and change the MODULES line to
MODULES=dep and save the file. Then run sudo update-initramfs -u
which will fail with:

$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic
mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry
mkinitramfs: workaround is MODULES=most
mkinitramfs: Error please report the bug
update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1.

[regression potential]

This changes initramfs creation for rootfs that are on nvme or lvm, so
has the potential to break it for any system with its rootfs on either
or both of those. It is likely to only break initramfs creation, not
system booting.

[other info]

related to bug 1532146

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

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

[Touch-packages] [Bug 1698967] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')

2017-10-05 Thread Phillip Susi

** Tags removed: hardware-error
** Tags added: bot-stop-nagging

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in dpkg package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   bsdutils:amd64: Configure
   axel:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 18 17:43:58 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-15 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

2017-10-05 Thread Mathieu Trudel-Lapierre

Turns out this is something directly in klibc in the case of xenial:
since xenial is not yet using isc-dhcp for IPv4 DHCP, since that was
deemed too intrusive a change for xenial.

In other words, while DHCPv6 is done via isc-dhcp, DHCPv4 is done via
ipconfig (klibc); which will need to be fixed to follow the same logic
as isc-dhcp w.r.t DOMAINSEARCH handling.

In general, I think having DOMAINSEARCH contain the existing DNS domain
if it's not otherwise set by the DHCP server is sensible.

I set the xenial task to High since it might actually impact a lot of
people, but it's not as high for artful/zesty given that isc-dhcp is
used instead (still ought to land there since people might want to use
ipconfig on their own, etc.).

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: Invalid => Triaged

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Triaged
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Triaged
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Triaged

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

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

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

[Touch-packages] [Bug 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

2017-10-05 Thread Mathieu Trudel-Lapierre

** Description changed:

+ [Impact]
+ Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.
+ 
+ [Test cases]
+ 1) Boot a system with a remote root over the network
+  - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
+ One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
+ 2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
+ 3) Validate the contents of /etc/resolv.conf
+ 
+ [Regression potential]
+ Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.
+ 
+ --
+ 
  For networked systems, for instance booting with an iSCSI root, dhclient
  writes an output file in the form of /run/net-.conf that contains
  data for other programs to consume. This allows, for instance, open-
  iscsi to get the right information and properly connect to the server to
  mount the root filesystem.
  
  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).
  
  In the not-initramfs dhclient-script, when domain_search isn't provided
  but domain_name is, domain_name is written to the search string. If both
  are provided, domain_search is written. The initramfs enter hook should
  do the same.

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: In Progress => Invalid

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

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

** Changed in: klibc (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: klibc (Ubuntu Zesty)
   Status: New => Triaged

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

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

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

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

** Changed in: klibc (Ubuntu Xenial)
   Importance: Undecided => High

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

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Triaged
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Triaged
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Triaged

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write

[Touch-packages] [Bug 1721541] Re: Lan connection lost but network-manager still sees connection as active

2017-10-05 Thread Ubuntu1988

This bug looks a lot like mine (with the same network card, but another
revision), with the difference that I can not find the connection via
the network-manager applet https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1715013 so I do not know if they can be considered
as duplicates

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

Title:
  Lan connection lost but network-manager still sees connection as
  active

Status in network-manager package in Ubuntu:
  New

Bug description:
  From time to time the wired connection is no longer accessible for a
  few minutes while network-manager always sees it active, even when I
  disconnect / reconnect from the applet. To recover the connection,
  either I wait a few minutes, or I unplug and then reconnect the cable.

  The other devices connected to the router have no issue and despite
  new network cables, only the computer under Ubuntu is affected (the
  same with the r8168 driver)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct  5 15:02:48 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-27 (8 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  IpRoute:
   default via 192.168.0.254 dev enp2s0 proto static metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.11 metric 100
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPETIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   OpenDNS  6917d17f-d173-43fa-a516-7c8503bdcc7e  802-3-ethernet  1507208476  
jeu. 05 oct. 2017 15:01:16 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes enp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/3  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp2s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
OpenDNS 6917d17f-d173-43fa-a516-7c8503bdcc7e  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1721541] Re: Lan connection lost but network-manager still sees connection as active

2017-10-05 Thread Ubuntu1988

I forgot: I have of course tested DNS other than those of my ISP, like
OpenDNS (which I currently have) or Google but always the same, even
ignoring IPv6

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

Title:
  Lan connection lost but network-manager still sees connection as
  active

Status in network-manager package in Ubuntu:
  New

Bug description:
  From time to time the wired connection is no longer accessible for a
  few minutes while network-manager always sees it active, even when I
  disconnect / reconnect from the applet. To recover the connection,
  either I wait a few minutes, or I unplug and then reconnect the cable.

  The other devices connected to the router have no issue and despite
  new network cables, only the computer under Ubuntu is affected (the
  same with the r8168 driver)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct  5 15:02:48 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-27 (8 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  IpRoute:
   default via 192.168.0.254 dev enp2s0 proto static metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.11 metric 100
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPETIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   OpenDNS  6917d17f-d173-43fa-a516-7c8503bdcc7e  802-3-ethernet  1507208476  
jeu. 05 oct. 2017 15:01:16 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes enp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/3  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp2s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
OpenDNS 6917d17f-d173-43fa-a516-7c8503bdcc7e  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1714667] Re: please add old hungarian letters

2017-10-05 Thread kixidevel

How could add a patch?
(naming conventions,font properties)

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

Title:
  please add old hungarian letters

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Old Hungarian letters (U10c80-U10cff) missing from font-families

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+subscriptions

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

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

2017-10-05 Thread Tom Verdaat

We upgraded to the vlan 1.9-3.2ubuntu1.16.04.3 package and our
networking broke horribly in a very similar way.

Let me start with our networking configuration. Two slaves, a bond and a
vlan on top of that bond:

auto eno1
iface eno1 inet manual
   mtu 1500
   bond-master bond1
   bond-primary eno1

auto eno2
iface eno2 inet manual
   mtu 1500
   bond-master bond1

auto bond1
iface bond1 inet static
   mtu 1500
   address 10.10.10.3
   bond-miimon 100
   bond-mode active-backup
   bond-slaves none
   bond-downdelay 200
   bond-updelay 200
   dns-nameservers 10.10.0.1
   netmask 255.255.0.0

auto bond1.2
iface bond1.2 inet static
   mtu 1500
   address 10.11.10.3
   netmask 255.255.0.0
   vlan-raw-device bond1

This fails to come up correctly, both during boot and manually. Bringing
up either eno1, eno2, bond1 or bond1.2 all result in the same problem:
"ifup: waiting for lock on /run/network/ifstate.bond1".

Problem seems to be that ifup tries to bring up the base bond1 interface
*again*. Even if it is already up. And it gets stuck waiting for the
bond1 interface to be unlocked so it can bring it up, but it is already
up and thus locked so that will never happen.

We also tried bringing all interfaces down and just running "ifup
bond1.2" but that results in the same behavior.

Only workaround that seemed to work for us was to:
1) temporarily remove the bond1.2.cfg from /etc/network/interfaces.d
2) bring up eno1, eno2 and bond1
3) put the bond1.2.cfg back in its place
4) run "ifup bond1.2"
5) using another terminal, list all open processes using "ps -ef | grep ifup"
6) kill the "ifup bond1" process

The "ps -ef | grep ifup" during step 5, outputs two ifup processes. One
for bond1 and one for bond1.2. As soon as we kill the "ifup bond1"
process, the "ifup bond1.2" process completes immediately and correctly
configures the vlan 2 subinterface.

This is clearly linked to vlan, because our infiniband interfaces work
just fine. Also it worked just fine before upgrading the package. So my
best guess would be that something broke in the code that detects if the
vlan-raw-device is up. Perhaps related to LP #1573272 ?

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

Title:
  ifup -a does not start dependants last, causes deadlocks with
  vlans/bonding

Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed

Bug description:
  This is a problem I've been struggling with since moving to 16.04.1
  from 14.04 (fresh install)

  I don't believe this problem affected 14.04. I have used an almost
  identical interfaces file on 14.04 without problem.

  On 16.04.1, however, 9/10 boots would hang during network
  configuration and leave the network incorrectly configured.

  When calling "ifup -a" all candidate interfaces appear to be started
  in parallel leading to collisions with locks. This causes hanging
  (until timeout) during booting and the network interfaces left
  incorrectly configured

  Imagine this /etc/network/interfaces

  auto eno1 bond0 bond0.1

  iface eno1 inet manual
  bond-master bond0

  iface bond0 inet manual
  bond-slaves eno1
  bond-mode   4
  bond-lacp-rate  1
  bond-miimon 100
  bond-updelay200
  bond-downdelay  200

  iface bond0.5 inet dhcp
  vlan-raw-device bond0

  
  eno1 -> bond0 -> bond0.5 -> dhcp

  When calling "ifup -a" at boot time all three interfaces are started
  at the same time.

  bond0 and bond0.5 both attempt to share the same lock file:

/run/network/ifstate.bond0

  If bond0 wins the race, the system will start correctly (1/10):

* bond0 starts and creates the bond0 device and the ifenslave.bond0 file to 
indicate the bond is ready
* eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 
to bond0
* bond0 finishes and releases the lock
* bond0.5 now acquires the lock.
* bond0.5 starts dhclient, which can talk to the network and configure the 
interface

  
  If, however, bond0.2 wins the lock race, the system will hang at boot (5 
mins) and fail to set up the network.

* bond0.5 is awarded the ifstate.bond0 lockfile
* bond0.5 starts dhclient waiting to hear from the network
* bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file 
* eno1 polls but never finds the ifenslave.bond0 file so never attaches to 
bond0
* bond0.5's dhclient is trying to talk to a disconnected network and never 
receives an answer

! bond0.5 is stuck running dhclient
! bond0 is stuck waiting for bond0.5 to finish
! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file

  
  I believe ifup should start interfaces (that share lock files) in dependant 
order. The most basic interface must be awarded the lock over its dependants. 
In

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

2017-10-05 Thread Łukasz Zemczak

Hello David, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.25 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, 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)
   Status: In Progress => Invalid

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

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

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

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Installing snaps is not possible on Ubuntu 14.04 when having /var on
  its own partition, whether its LVM or not.

  The issue is with the core snap being unable to mount:

  The error with /var isolated and using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  The error with /var isolated but without using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service
 failed to load: No such file or directory. See system logs and 'systemctl 
status 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service'
 for details.
  )

  The same error happens if I try to install the hello-world snap (with
  LVM in this example):

  root@ubuntu:~# snap install hello-world
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  I cannot reproduce the issue in Ubuntu 16.04.

  I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image
  which doesn't isolate /var on its own partition. I tried adding a
  secondary disk to that cloud image VM and create a dummy VG and LV,
  but couldn't reproduce the issue.

  Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with
  only a / partition and swap.

  [Test Case]

  # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and
  configure /, /var and swap on their own partitions (with LVM or not,
  the issue happens in both situations).

  root@ubuntu:~# lvs
  LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
  rootvol vg00 -wi-ao--- 3.72g
  swap vg00 -wi-ao--- 3.72g
  varvol vg00 -wi-ao--- 3.72g

  root@ubuntu:~# df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 484M 4.0K 484M 1% /dev
  tmpfs 100M 988K 99M 1% /run
  /dev/dm-0 3.7G 1.7G 1.8G 49% /
  none 4.0K 0 4.0K 0% /sys/fs/cgroup
  none 5.0M 0 5.0M 0% /run/lock
  none 497M 0 497M 0% /run/shm
  none 100M 0 100M 0% /run/user
  /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var

  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  # After reboot, check kernel version and try to install the canonical-
  livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  root@ubuntu:~# snap install

[Touch-packages] [Bug 1721541] [NEW] Lan connection lost but network-manager still sees connection as active

2017-10-05 Thread Ubuntu1988

Public bug reported:

>From time to time the wired connection is no longer accessible for a few
minutes while network-manager always sees it active, even when I
disconnect / reconnect from the applet. To recover the connection,
either I wait a few minutes, or I unplug and then reconnect the cable.

The other devices connected to the router have no issue and despite new
network cables, only the computer under Ubuntu is affected (the same
with the r8168 driver)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct  5 15:02:48 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-09-27 (8 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
IpRoute:
 default via 192.168.0.254 dev enp2s0 proto static metric 100 
 169.254.0.0/16 dev enp2s0 scope link metric 1000 
 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.11 metric 100
IwConfig:
 enp2s0no wireless extensions.
 
 lono wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID  TYPETIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
 OpenDNS  6917d17f-d173-43fa-a516-7c8503bdcc7e  802-3-ethernet  1507208476  
jeu. 05 oct. 2017 15:01:16 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes enp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/3  --
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp2s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
OpenDNS 6917d17f-d173-43fa-a516-7c8503bdcc7e  
/org/freedesktop/NetworkManager/ActiveConnection/3 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug 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/1721541

Title:
  Lan connection lost but network-manager still sees connection as
  active

Status in network-manager package in Ubuntu:
  New

Bug description:
  From time to time the wired connection is no longer accessible for a
  few minutes while network-manager always sees it active, even when I
  disconnect / reconnect from the applet. To recover the connection,
  either I wait a few minutes, or I unplug and then reconnect the cable.

  The other devices connected to the router have no issue and despite
  new network cables, only the computer under Ubuntu is affected (the
  same with the r8168 driver)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct  5 15:02:48 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-27 (8 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  IpRoute:
   default via 192.168.0.254 dev enp2s0 proto static metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.11 metric 100
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPETIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH

[Touch-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install

This bug was fixed in the package ubuntu-settings - 17.10.17

---
ubuntu-settings (17.10.17) artful; urgency=medium

  * Hide imagemagick's Display app from the Ubuntu session (LP:
#1717951)

 -- Jeremy Bicha   Tue, 03 Oct 2017 21:36:30 -0400

** Changed in: ubuntu-settings (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  UIFe: Drop imagemagick-display from the default install

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in imagemagick package in Debian:
  New

Bug description:
  Impact
  ==
  I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

  It is visible in the Show Applications view of the Activities Overview
  so this could impact screenshots.

  Justification
  =
  imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

  Bundled with imagemagick is the "display" app, which is an app with an
  unusual, difficult-to-use UI. It was not intentionally included in the
  default Ubuntu install but was only there because it was packaged
  together.

  I am proposing splitting the display app to a separate binary package
  so that it is available for install for the few who do want to use the
  app.

  I tried proposing this to Debian. See comment #60 on the attached
  Debian bug but the Debian maintainer doesn't seem interested in
  accepting my proposal any time soon. (I emailed him directly a few
  months ago too.)

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

  Other Info
  ==
  I will be attaching a patch for review by the Desktop Team here soon.

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

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

[Touch-packages] [Bug 1721537] [NEW] No sound from headphone jack on xps13 9350 after ubuntu 17.10 dist-upgrade

2017-10-05 Thread Rien Heuver

Public bug reported:

I just upgraded from 17.04 to 17.10 on my Dell XPS13 9350. Ever since my
headphone jack doesn't output anything. The internal speakers are still
working fine, the speakers I connect to the laptop too (tested with my
phone). The system does recognize the speakers being connected, since I
get the Headpones | Headset | Microphone popup and I can also test
left/right speakers in Sound. However, no audio is coming through.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rienheuver   1426 F pulseaudio
CurrentDesktop: GNOME
Date: Thu Oct  5 14:41:11 2017
InstallationDate: Installed on 2016-11-22 (316 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at 
all
UpgradeStatus: Upgraded to artful on 2017-10-05 (0 days ago)
dmi.bios.date: 12/18/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.9
dmi.board.name: 07TYC2
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.9:bd12/18/2015:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  No sound from headphone jack on xps13 9350 after ubuntu 17.10 dist-
  upgrade

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just upgraded from 17.04 to 17.10 on my Dell XPS13 9350. Ever since
  my headphone jack doesn't output anything. The internal speakers are
  still working fine, the speakers I connect to the laptop too (tested
  with my phone). The system does recognize the speakers being
  connected, since I get the Headpones | Headset | Microphone popup and
  I can also test left/right speakers in Sound. However, no audio is
  coming through.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rienheuver   1426 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  5 14:41:11 2017
  InstallationDate: Installed on 2016-11-22 (316 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: Upgraded to artful on 2017-10-05 (0 days ago)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.9
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.9:bd12/18/2015:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

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

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

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

Title:
  ifup -a does not start dependants last, causes deadlocks with
  vlans/bonding

Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed

Bug description:
  This is a problem I've been struggling with since moving to 16.04.1
  from 14.04 (fresh install)

  I don't believe this problem affected 14.04. I have used an almost
  identical interfaces file on 14.04 without problem.

  On 16.04.1, however, 9/10 boots would hang during network
  configuration and leave the network incorrectly configured.

  When calling "ifup -a" all candidate interfaces appear to be started
  in parallel leading to collisions with locks. This causes hanging
  (until timeout) during booting and the network interfaces left
  incorrectly configured

  Imagine this /etc/network/interfaces

  auto eno1 bond0 bond0.1

  iface eno1 inet manual
  bond-master bond0

  iface bond0 inet manual
  bond-slaves eno1
  bond-mode   4
  bond-lacp-rate  1
  bond-miimon 100
  bond-updelay200
  bond-downdelay  200

  iface bond0.5 inet dhcp
  vlan-raw-device bond0

  
  eno1 -> bond0 -> bond0.5 -> dhcp

  When calling "ifup -a" at boot time all three interfaces are started
  at the same time.

  bond0 and bond0.5 both attempt to share the same lock file:

/run/network/ifstate.bond0

  If bond0 wins the race, the system will start correctly (1/10):

* bond0 starts and creates the bond0 device and the ifenslave.bond0 file to 
indicate the bond is ready
* eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 
to bond0
* bond0 finishes and releases the lock
* bond0.5 now acquires the lock.
* bond0.5 starts dhclient, which can talk to the network and configure the 
interface

  
  If, however, bond0.2 wins the lock race, the system will hang at boot (5 
mins) and fail to set up the network.

* bond0.5 is awarded the ifstate.bond0 lockfile
* bond0.5 starts dhclient waiting to hear from the network
* bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file 
* eno1 polls but never finds the ifenslave.bond0 file so never attaches to 
bond0
* bond0.5's dhclient is trying to talk to a disconnected network and never 
receives an answer

! bond0.5 is stuck running dhclient
! bond0 is stuck waiting for bond0.5 to finish
! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file

  
  I believe ifup should start interfaces (that share lock files) in dependant 
order. The most basic interface must be awarded the lock over its dependants. 
In this case:

1 eno1
2 bond0
3 bond0.5

  but never:

1 eno1
2 bond0.5
3 bond0

  
  As a work arouund, in /etc/network/interfaces

  -auto   eno1 bond0 bond0.1
  +auto   eno1 bond0
  +allow-bond bond0.1

  And also in /lib/systemd/system/networking.service

   ExecStart=/sbin/ifup -a --read-environment
  +ExecStart=/sbin/ifup -a --allow=bond --read-environment
   ExecStop=/sbin/ifdown -a --read-environment

  Then run:

systemctl dameon-reload

  This causes all "auto" interfaces to start then, when they've
  completed, all allow-bond interfaces to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.1 [modified: 
lib/systemd/system/networking.service]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 26 06:32:57 2016
  InstallationDate: Installed on 2016-10-24 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.networking.conf: [modified]
  mtime.conffile..etc.init.networking.conf: 2016-10-26T04:52:05.750927

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

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

[Touch-packages] [Bug 1718664] Re: Dragging folder to applications: Incorrect behaviour

2017-10-05 Thread Martin Riethmayer

Sorry for the delayed reply: I've one PC where opening folders doesn't
work in "Brackets" [1] as well, but I can't reproduce this issue in a
clean VM, so I'll have to investigate some more.

I'll get back as soon as I can confirm if an update of Kate fixes the
issue.

http://brackets.io/

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

Title:
  Dragging folder to applications: Incorrect behaviour

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

Bug description:
  Applies to: Kubuntu 16.04.3 (up-to-date)

  Additional PPAs: ppa:kubuntu-ppa/backports

  Reproducible: Always

  Steps to reproduce:
  1.) Create a folder with a text file and a subfolder with a text file
  2.) Write some text in the text files
  3.) Drag'n'Drop the folder into any text-processor (e.g. kate, kwrite)

  Expected behaviour:
  All text files should be opened with their content

  Actual behaviour:
  There will be the correct number of files opened, but they don't have content 
and are trying to be opened from the incorrect path. It looks like there is one 
folder missing from the path to the file

  Did this work in earlier versions:
  Yes, this works on a fully up-to-date Kubuntu 14.04

  Does this work in later version:
  Probably (can't test currently), it works e.g. in KDE Neon User Edition.

  System information:
  KDE Plasma Version: 5.8.7
  KDE Frameworks Version: 5.36.0
  QT Version: 5.6.1
  Kernel Version 4.10.0-35-generic

  Further information:
  I was told that this works fine with QT 5.6.2 but do not currently have the 
possibility to test this myself. I was also told that the fix might be this 
commit in QT:

  https://git.qt.io/consulting-usa/qtbase-xcb-
  rendering/commit/1108291e1a2e7de23440c2b36b2fd31010ae3f51

  but again, I can't test this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1718664/+subscriptions

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

2017-10-05 Thread Rafael David Tinoco

After fixing this BUG (for canonical-livepatch snap to work, but being
affected by broken systemd in Trusty due to the lack of systemd-
fsck@.service unit file, I'm facing the following opened BUG:
https://bugs.launchpad.net/snapd/+bug/1721518 for canonical-livepatch
(or any other snap) to work).

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

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  [Impact]

  Installing snaps is not possible on Ubuntu 14.04 when having /var on
  its own partition, whether its LVM or not.

  The issue is with the core snap being unable to mount:

  The error with /var isolated and using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  The error with /var isolated but without using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service
 failed to load: No such file or directory. See system logs and 'systemctl 
status 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service'
 for details.
  )

  The same error happens if I try to install the hello-world snap (with
  LVM in this example):

  root@ubuntu:~# snap install hello-world
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  I cannot reproduce the issue in Ubuntu 16.04.

  I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image
  which doesn't isolate /var on its own partition. I tried adding a
  secondary disk to that cloud image VM and create a dummy VG and LV,
  but couldn't reproduce the issue.

  Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with
  only a / partition and swap.

  [Test Case]

  # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and
  configure /, /var and swap on their own partitions (with LVM or not,
  the issue happens in both situations).

  root@ubuntu:~# lvs
  LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
  rootvol vg00 -wi-ao--- 3.72g
  swap vg00 -wi-ao--- 3.72g
  varvol vg00 -wi-ao--- 3.72g

  root@ubuntu:~# df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 484M 4.0K 484M 1% /dev
  tmpfs 100M 988K 99M 1% /run
  /dev/dm-0 3.7G 1.7G 1.8G 49% /
  none 4.0K 0 4.0K 0% /sys/fs/cgroup
  none 5.0M 0 5.0M 0% /run/lock
  none 497M 0 497M 0% /run/shm
  none 100M 0 100M 0% /run/user
  /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var

  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  # After reboot, check kernel version and try to install the canonical-
  livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  [Regression Potential]

  - Unit file has been added to systemd, could cause an error in some units 
initialization. Since systemd is not used as "init" system for Trusty, this is 
minor regression.
  - Could break all systemd units depending (After=/Wants=) 
systemd-fsck@.service but they are already broken.

  ** A "pre-SRU" test package provided in Tinoco's PPA has been also
  intensively tested with success, which bring even more confidence for
  this change. Note that the same level/quality of testing will be
  performed one more time when the

[Touch-packages] [Bug 1326335] Re: The 'GTK+' qt theme is buggy

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

** Changed in: qt4-x11 (Ubuntu)
   Status: New => Confirmed

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

Title:
  The 'GTK+' qt theme is buggy

Status in qt4-x11 package in Ubuntu:
  Confirmed

Bug description:
  If I launch qtconfig-qt4 in 12.04 Precise Pangolin or onwards (reproducible 
at least till 14.04 trusty) and I change the font size of the 'GTK+' theme 
(saving this change, obviously), this new values is really written in 
Trolltech.conf.
  But when I open again qtconfig-qt4, the changed config is not loaded, as if 
it were taken from another place. This problem does not occur with other themes 
available in qtconfig-qt4.

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

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

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

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

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Confirmed
Status in Totem:
  Incomplete
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  In Progress
Status in gstreamer package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

** Changed in: gstreamer (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Confirmed
Status in Totem:
  Incomplete
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  In Progress
Status in gstreamer package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720431] Re: Thin line below title bar

2017-10-05 Thread Treviño

** Changed in: ubuntu-themes
   Status: Incomplete => Fix Released

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: Incomplete => Fix Released

** Changed in: ubuntu-themes
 Assignee: (unassigned) => Didier Roche (didrocks)

** Changed in: ubuntu-themes (Ubuntu Artful)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => Didier Roche (didrocks)

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

Title:
  Thin line below title bar

Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Released

Bug description:
  ubuntu artful desktop 20170929

  There is a 1px line in the title bar (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170925-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 14:54:27 2017
  InstallationDate: Installed on 2013-09-03 (1486 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

** Branch linked: lp:~vanvugt/gtk/fix-1698270

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Confirmed
Status in Totem:
  Incomplete
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  In Progress
Status in gstreamer package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721203] Re: systemd armhf autopkgtest test-copy fails in artful

2017-10-05 Thread Bug Watch Updater

** Changed in: systemd
   Status: New => 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/1721203

Title:
  systemd armhf autopkgtest test-copy fails in artful

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

Bug description:
  systemd armhf autopkgtest test-copy fails in artful

  test-copy uses itself as the source to test copies. The test suite
  tries to test cases where maximum requested copy is below and above
  the internal buffer size. However, that fails when the maximum
  requested copy bytes is more than the source binary... as started to
  be the case with uber optimised artful toolchain on armhf, and after
  debug symbols stripped. Specifically test-copy started to be less than
  32000 bytes.

  Awaiting improvement to the test suite upstream, simply keep test-copy
  unstripped such that systemd-tests can be used in adt tests without
  failures.

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

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

[Touch-packages] [Bug 1721102] Re: Thin line at the left of Simple Scan's "Scan" headerbar button

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

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

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

Title:
  Thin line at the left of Simple Scan's "Scan" headerbar button

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

Bug description:
  There is a thin colored line (green or red) at the left of rounded
  button, for example in simple-scan in the screenshot attached (I
  didn't find any other app affected ATM)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170930-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 20:16:32 2017
  InstallationDate: Installed on 2013-09-03 (1490 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719746] Re: gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default Ubuntu desktop

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

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

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

Title:
  gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default
  Ubuntu desktop

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  I don't use gdebi but this commit looks wrong:

  https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu1ubuntu3

  See
  https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html

  https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-
  spec-latest.html#mime-types

  (Do not be confused by the Type=MimeType deprecation. This file is
  Type=Application.)

  Here's a user video report:
  https://youtu.be/yDrAbBAp-1A?t=16m19s

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

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

[Touch-packages] [Bug 1719746] Re: gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default Ubuntu desktop

2017-10-05 Thread Rik Mills

I see the same as shown in the video in Firefox.

i.e. previously you could click a link to a .deb file, use the Firefox
open with dialog to select 'other', and you would be able to find gdebi
in the 'recommended' or 'view all' applications. With this update, gdebi
is not there and cannot be found in any way.

Downgrading to 0.9.5.7+nmu1ubuntu2 brings gdebi back into the list of
available apps.

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

Title:
  gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default
  Ubuntu desktop

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  I don't use gdebi but this commit looks wrong:

  https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu1ubuntu3

  See
  https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html

  https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-
  spec-latest.html#mime-types

  (Do not be confused by the Type=MimeType deprecation. This file is
  Type=Application.)

  Here's a user video report:
  https://youtu.be/yDrAbBAp-1A?t=16m19s

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

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

[Touch-packages] [Bug 1721472] [NEW] package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

2017-10-05 Thread Einar Bjarni Halldórsson

Public bug reported:

Post install for console-setup failed. Had to edit postinstall script to
exit 0 to install other packages

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: console-setup 1.166ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
AptOrdering: NULL: ConfigurePending
Architecture: amd64
Date: Wed Oct  4 09:24:06 2017
DpkgTerminalLog:
 Setting up keyboard-configuration (1.166ubuntu6) ...
 Setting up console-setup-linux (1.166ubuntu6) ...
 Setting up console-setup (1.166ubuntu6) ...
 [1mdpkg:[0m error processing package console-setup (--configure):
  subprocess installed post-installation script was killed by signal 
(Terminated)
ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
InstallationDate: Installed on 2017-10-04 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.2-1ubuntu4
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: console-setup
Title: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess 
installed post-installation script was killed by signal (Terminated)
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package console-setup 1.166ubuntu6 failed to install/upgrade:
  subprocess installed post-installation script was killed by signal
  (Terminated)

Status in console-setup package in Ubuntu:
  New

Bug description:
  Post install for console-setup failed. Had to edit postinstall script
  to exit 0 to install other packages

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: console-setup 1.166ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Oct  4 09:24:06 2017
  DpkgTerminalLog:
   Setting up keyboard-configuration (1.166ubuntu6) ...
   Setting up console-setup-linux (1.166ubuntu6) ...
   Setting up console-setup (1.166ubuntu6) ...
   [1mdpkg:[0m error processing package console-setup (--configure):
subprocess installed post-installation script was killed by signal 
(Terminated)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  InstallationDate: Installed on 2017-10-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.2-1ubuntu4
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: console-setup
  Title: package console-setup 1.166ubuntu6 failed to install/upgrade: 
subprocess installed post-installation script was killed by signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721280] Re: vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()

2017-10-05 Thread Jean-Baptiste Lallement

** Information type changed from Private to Public

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

Title:
  vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()

Status in vim package in Ubuntu:
  New

Bug description:
  Might be related to one of my extensions

  camelcasemotion  lightline.vim  vim-fetch
  inorirust.vim   validator.vim  vim-fugitive

  
  Please also double check that it's not a duplicate of #96263 "vim crashed 
with sigsegv"

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: vim-gtk3 2:8.0.0197-4ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct  4 16:13:33 2017
  ExecutablePath: /usr/bin/vim.gtk3
  InstallationDate: Installed on 2017-05-30 (127 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: vim update_test_projects.sh
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   kill () at ../sysdeps/unix/syscall-template.S:84
   mch_exit ()
   getout ()
() at /lib/x86_64-linux-gnu/libpthread.so.0
   __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:135
  Title: vim.gtk3 crashed with SIGSEGV in kill()
  UpgradeStatus: Upgraded to artful on 2017-09-25 (8 days ago)
  UserGroups: dialout plugdev sudo wireshark

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

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

[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

2017-10-05 Thread Yuan-Chen Cheng

** Changed in: oem-priority/xenial
   Status: New => Triaged

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Zesty:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  New

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
    Installed: 0.90
    Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

  
  * APT SRU *
  [Impact]
  Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the 
signals to all processes in the cgroup, and will send KILL quickly after.

  [Test case]
  Start apt-daily-upgrade.service and stop it while unattended-upgrades is 
running.

  The upgrade should run to completion or a safe exit point as long as
  it takes less than about 900s (which is the timeout for sending kill).

  [Regression potential]
  Leftover processes might remain in the apt-daily-upgrade cgroup if the 
postinst scripts or some apt hooks do something funny.

  Shutdown might take longer due to the 900 second timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

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

[Touch-packages] [Bug 1719612] Re: non-us keyboard layout not setup in initramfs

2017-10-05 Thread William Daniau

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  non-us keyboard layout not setup in initramfs

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

Bug description:
  Description:Ubuntu Artful Aardvark (development branch)
  Release:17.10

  In Artful the /etc/console/cached.kmap.gz file does not exists, in its place, 
it uses some files with more precise names susch as cached_UTF-8_del.kmap.gz. 
However the initramfs scripts still uses cached.kmap.gz . The consequence is 
that the keyboard layout remains US in the initramfs which is a problem for 
full encrypted installation when entering passphrase.
  Proposed solution is to make a symbolic link from  cached_UTF-8_del.kmap.gz 
to cached.kmap.gz. Then the initramfs tools will find the 
/etc/console/cached.kmap.gz file and includes it in the initramfs.

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

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

[Touch-packages] [Bug 1721451] [NEW] package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: le paquet isc-dhcp-common n'est pas prêt pour la configuration configuration impossible (état

2017-10-05 Thread Cyril MARTINIE

Public bug reported:

???

Every update is forbidden because of this problem!!

Please, help me!

Thanks, Cyril

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-common 4.3.3-5ubuntu12.7
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Oct  5 08:17:47 2017
Dependencies:
 debianutils 4.7
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 sensible-utils 0.0.9
ErrorMessage: le paquet isc-dhcp-common n'est pas prêt pour la configuration  
configuration impossible (état actuel « half-installed »)
InstallationDate: Installed on 2017-03-30 (188 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: isc-dhcp
Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: le 
paquet isc-dhcp-common n'est pas prêt pour la configuration  configuration 
impossible (état actuel « half-installed »)
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade:
  le paquet isc-dhcp-common n'est pas prêt pour la configuration
  configuration impossible (état actuel « half-installed »)

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  ???

  Every update is forbidden because of this problem!!

  Please, help me!

  Thanks, Cyril

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-common 4.3.3-5ubuntu12.7
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Oct  5 08:17:47 2017
  Dependencies:
   debianutils 4.7
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   sensible-utils 0.0.9
  ErrorMessage: le paquet isc-dhcp-common n'est pas prêt pour la configuration  
configuration impossible (état actuel « half-installed »)
  InstallationDate: Installed on 2017-03-30 (188 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: 
le paquet isc-dhcp-common 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/+source/isc-dhcp/+bug/1721451/+subscriptions

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

[Touch-packages] [Bug 1720431] Re: Thin line below title bar

I think this got fixed with bug 1720980 ... ?

** Changed in: ubuntu-themes
   Status: Confirmed => Incomplete

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: Confirmed => Incomplete

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

Title:
  Thin line below title bar

Status in Ubuntu theme:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete
Status in ubuntu-themes source package in Artful:
  Incomplete

Bug description:
  ubuntu artful desktop 20170929

  There is a 1px line in the title bar (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170925-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 14:54:27 2017
  InstallationDate: Installed on 2013-09-03 (1486 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717023] Re: Jarring double gradient when window is maximized

** Branch linked: lp:~3v1n0/ubuntu-themes/use-inverted-decoration-
gradient-on-maximized-windows

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

Title:
  Jarring double gradient when window is maximized

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  light-themes:
    Installed: 16.10+17.10.20170817-0ubuntu1
    Candidate: 16.10+17.10.20170817-0ubuntu1

  Since windows no longer merge with the top panel when maximized in
  17.10, a jarring double gradient is produced instead.

  Steps to reproduce: Maximize a window

  Actual outcome: A double gradient with a sharp line where the top of
  the title bar meets the top panel is produced.

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

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

[Touch-packages] [Bug 1682102] Re: libseccomp should support GA and HWE kernels

@xnox bringing zesty's libseccomp back to xenial may be needed for some
kernel/snapd/libseccomp changes that I'm working on. Have you spent any
time investigating such a change?

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

Title:
  libseccomp should support GA and HWE kernels

Status in libseccomp package in Ubuntu:
  Confirmed
Status in libseccomp source package in Xenial:
  Confirmed

Bug description:
  Currently libseccomp version in Ubuntu are:

   libseccomp | 2.2.3-3ubuntu3   | xenial | 
source
   libseccomp | 2.3.1-2ubuntu2   | yakkety| 
source
   libseccomp | 2.3.1-2.1ubuntu1 | zesty  | 
source

  The difference between 2.2.3 and 2.3.1 is 63 upstream commits.

  Of those commits, 7 are already cherrypicked into xenial for s390x
  support.

  However that s390x support is incomplete as multiplexed syscalls are
  not supported.

  A request has been filed to support multiplexed syscalls in libseccomp
  in xenial at
  https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1679691

  That is a request for further 18 commits to backport, bringing the
  total to 25.

  Looking at the remaining 38 commits there are:
  - documentation updates
  - tools updates
  - tests updates
  - bugfixes
  - updates to syscall tables for linux 4.3, 4.5-rc4+

  IMHO, in the future when libseccomp is updated to support 4.10 kernel
  syscalls, it should be backported back to xenial too, to properly
  suppor the HWE kernels.

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

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

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps