[Touch-packages] [Bug 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

[Dmitry Shachnev]

The latest qtdeclarative build in Disco contains the properly built
documentation, so marking this bug as fixed there.

I am working on a backport to Cosmic now.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  New
Status in qtdeclarative-opensource-src source package in Cosmic:
  New
Status in qttools-opensource-src source package in Cosmic:
  New
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

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

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

[Touch-packages] [Bug 1805077] Re: the audio pause and repeat for a very short of time randomly

[widon1104]

vlc play local avi videos still has this problem

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

Title:
  the audio pause and repeat for a very short of time randomly

Status in firefox package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in smplayer package in Ubuntu:
  New

Bug description:
  the audio pause and repeat for a very short of time randomly
  when I use web browser to play music and use smplayer play video this bug 
happens randomly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon 13716 F pulseaudio
   /dev/snd/controlC0:  widon 13716 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  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.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1805077] Re: the audio pause and repeat for a very short of time randomly

[Daniel van Vugt]

Are you using Bluetooth audio?

** No longer affects: firefox (Ubuntu)

** No longer affects: smplayer (Ubuntu)

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

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

Title:
  the audio pause and repeat for a very short of time randomly

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  the audio pause and repeat for a very short of time randomly
  when I use web browser to play music and use smplayer play video this bug 
happens randomly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon 13716 F pulseaudio
   /dev/snd/controlC0:  widon 13716 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  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.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1805077] Re: the audio pause and repeat for a very short of time randomly

[widon1104]

I do not use Bluetooth at all.

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

Title:
  the audio pause and repeat for a very short of time randomly

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  the audio pause and repeat for a very short of time randomly
  when I use web browser to play music and use smplayer play video this bug 
happens randomly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon 13716 F pulseaudio
   /dev/snd/controlC0:  widon 13716 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  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.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Raimundas]

I have the same problem with my Ubuntu 16 VPS servers. I had systemd
version 229-4ubuntu21.5 on my templates and when it is updated to
version 229-4ubuntu21.9 this erroneous behavior occurs. On other client
VPS's i have seen that they updated systemd from version 229-4ubuntu21.8
to 229-4ubuntu21.9. Thus it seems like a problem with the November 19
update for systemd -
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.9


Here is an alternative "fix" you can use until this problem is properly 
resolved (just change the "21.5" version, which was working for you before the 
update):

cd /home/
wget launchpadlibrarian.net/392626140/libsystemd0_229-4ubuntu21.5_amd64.deb
wget launchpadlibrarian.net/392626138/libpam-systemd_229-4ubuntu21.5_amd64.deb
wget launchpadlibrarian.net/392626148/systemd_229-4ubuntu21.5_amd64.deb
dpkg -i libpam-systemd_229-4ubuntu21.5_amd64.deb 
systemd_229-4ubuntu21.5_amd64.deb libsystemd0_229-4ubuntu21.5_amd64.deb
apt-mark hold systemd libsystemd0 libpam-systemd
reboot

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  
  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
i->uid_set ? i->uid : UID_INVALID,
i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  
  Any help fixing this problem would be highly appreciated. 
  Many thanks,
  Rafael

To manage notifications about this bug go to:

[Touch-packages] [Bug 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath

[Łukasz Zemczak]

Kyle: which version of the package did you use during verification? We
want to make sure that the correct -proposed package version has been
tested. Could you provide us with apt-cache policy output?

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

Title:
  ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
  partitions name for the mpath

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact]
  Any user of Ubuntu on multipath, where the default path separator has been 
changed to something else. This possibly affects other scenarios where the 
partition separator can be changed.

  [Test case]
  1) Install Ubuntu on multipath system
  2) Change /etc/multipath.conf to set "path_separator" to "" or "p".
  3) Reboot
  4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions 
where the path separator would be visible.

  
  [Regression potential]
  Minimal. This only affects display. Default separator on Ubuntu remains 
"-part". If the separator is not one of "", "p", or "-part", then "-part" would 
be used, as is already the case.

  
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-09 11:14:07 
==
  We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the 
Emulex adapter to have the mpath disk.
  Running the fdisk -l and ls -l showing the conflict name for the mpath.

  :~# uname -a
  Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp4:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part1   2048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2  419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3  838862848 1258291199 419428352  200G 83 Linux

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:04 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha3 -> ../dm-3

  == Comment: #2 - Chanh H. Nguyen  - 2018-01-09 11:35:04 
==
  I just modify the partitions and it is still showing the conflicting name on 
partitions.

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha3 -> ../dm-3
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha4 -> ../dm-4
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha5 -> ../dm-5
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha6 -> ../dm-6
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha7 -> ../dm-7
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha8 -> ../dm-8

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot  StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part12048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2   419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3   838862848  964691967 125829120   60G 83 Linux
  /dev/mapper/mpatha-part4   964691968 1258291199 293599232  140G  5 
Extended
  /dev/mapper/mpatha-part5   964694016 1006637055  41943040   20G 83 Linux
  /dev/mapper/mpatha-part6  1006639104 1048582143  41943040   20G 83 Linux
  /dev/mapper/mpatha-part7  1048584192 1090527231  41943040   20G 83 Linux
  /dev/mapper/mpatha-part8  1090529280 113247

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Stefan Andres]

In it's current version (systemd-229-4ubuntu21.9) it seems to be made
worse.

Files in /var/run/ will get `Too many levels of symbolic links` files in
/run/ will still get `fchownat() of /run/... failed: Invalid argument`

root@sandres-test-systemd:/usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug 
systemd-tmpfiles --create zabbix-agent.conf
Reading config file "zabbix-agent.conf".
Running create action for entry d /var/run/zabbix
Failed to validate path /var/run/zabbix: Too many levels of symbolic links
root@sandres-test-systemd:/usr/lib/tmpfiles.d# cat zabbix-agent.conf
d /var/run/zabbix 0755 zabbix zabbix - -
root@sandres-test-systemd:/usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug 
systemd-tmpfiles --create zabbix-agent2.conf
Reading config file "zabbix-agent2.conf".
Running create action for entry d /run/zabbix
Found existing directory "/run/zabbix".
"/run/zabbix" has right mode 40755
chown "/run/zabbix" to 108.115
fchownat() of /run/zabbix failed: Invalid argument
root@sandres-test-systemd:/usr/lib/tmpfiles.d# cat zabbix-agent2.conf
d /run/zabbix 0755 zabbix zabbix - -
root@sandres-test-systemd:/usr/lib/tmpfiles.d#

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  
  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
i->uid_set ? i->uid : UID_INVALID,
i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  
  Any help f

[Touch-packages] [Bug 1805108] [NEW] CUPS are not compatible with Gutenprint

[CHRISTOPHORUS ARDI NUGRAHA]

Public bug reported:

I tried to print documents with Canon ip2770. But, the printer does not work. I 
looked at the CUPS GUI, there is report
stopped 
"The PPD version (5.2.13) is not compatible with Gutenprint 5.2.14. Please run 
`/usr/sbin/cups-genppdupdate' as administrator."
I tried to update PPD by sudo cups-genppupdate. It doesn't work.
I tried to change access of /usr/sbin/cups-genppdupdate to be Read-Write, does 
not work either.

What should I do now?
Please help.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 26 16:56:38 2018
InstallationDate: Installed on 2018-08-15 (102 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lpstat: device for iP2700: usb://Canon/iP2700%20series?serial=78A1BF
MachineType: HP HP Laptop 14-bs0xx
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iP2700.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/iP2700.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=761dccc8-ecad-4374-9d7d-de66adbc13e1 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 831F
dmi.board.vendor: HP
dmi.board.version: 17.36
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/24/2017:svnHP:pnHPLaptop14-bs0xx:pvrType1ProductConfigId:rvnHP:rn831F:rvr17.36:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-bs0xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apparmor apport-bug bionic

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

Title:
  CUPS are not compatible with Gutenprint

Status in cups package in Ubuntu:
  New

Bug description:
  I tried to print documents with Canon ip2770. But, the printer does not work. 
I looked at the CUPS GUI, there is report
  stopped 
  "The PPD version (5.2.13) is not compatible with Gutenprint 5.2.14. Please 
run `/usr/sbin/cups-genppdupdate' as administrator."
  I tried to update PPD by sudo cups-genppupdate. It doesn't work.
  I tried to change access of /usr/sbin/cups-genppdupdate to be Read-Write, 
does not work either.

  What should I do now?
  Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 26 16:56:38 2018
  InstallationDate: Installed on 2018-08-15 (102 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lpstat: device for iP2700: usb://Canon/iP2700%20series?serial=78A1BF
  MachineType: HP HP Laptop 14-bs0xx
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iP2700.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/iP2700.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=761dccc8-ecad-4374-9d7d-de66adbc13e1 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 831F
  dmi.board.vendor: HP
  dmi.board.version: 17.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/24/2017:svnHP:pnHPLaptop14-bs0xx:pvrType1ProductConfigId:rvnHP:rn831F:rvr17.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-bs0xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1805115] [NEW] problem with (ubuntu/cosmic)mawk /^[[:space:]]*

[dub src]

Public bug reported:


#lsb_release -rd

Description:Ubuntu 18.10
Release:18.10

## package version
#apt-cache policy mawk

mawk:
  Installed: 1.3.3-17ubuntu3
  Candidate: 1.3.3-17ubuntu3
  Version table:
 *** 1.3.3-17ubuntu3 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
###

more background @ 
https://github.com/whiteinge/ok.sh/issues/66# problem with (ubuntu/cosmic)mawk 
/^[[:space:]]*https://api.github.com/repositories/3386088/issues?page=2>; 
rel="next", ; 
rel="last"' | awk '
BEGIN { RS=", "; FS="; "; OFS=": " }
{
sub(/^rel="/, "", $2); sub(/"$/, "", $2)
sub(/^ *$/, "", $1)
print "Link_" $2, $1
}'
Link_next: https://api.github.com/repositories/3386088/issues?page=2
Link_last: https://api.github.com/repositories/3386088/issues?page=33
-

fails using [[:space:]]
eg
-
printf %s '; 
rel="next", ; 
rel="last"' | awk '
BEGIN { RS=", "; FS="; "; OFS=": " }
{
sub(/^rel="/, "", $2); sub(/"$/, "", $2)
sub(/^[[:space:]]*$/, "", $1)
print "Link_" $2, $1
}'
Link_next: ; 
rel="next", ; 
rel="last"' | awk '
  BEGIN { RS=", "; FS="; "; OFS=": " }
  {
  sub(/^rel="/, "", $2); sub(/"$/, "", $2)
  sub(/^ *$/, "", $1)
  print "Link_" $2, $1
  }'
  Link_next: https://api.github.com/repositories/3386088/issues?page=2
  Link_last: https://api.github.com/repositories/3386088/issues?page=33
  -

  fails using [[:space:]]
  eg
  -
  printf %s '; 
rel="next", ; 
rel="last"' | awk '
  BEGIN { RS=", "; FS="; "; OFS=": " }
  {
  sub(/^rel="/, "", $2); sub(/"$/, "", $2)
  sub(/^[[:space:]]*$/, "", $1)
  print "Link_" $2, $1
  }'
  Link_next: 

[Touch-packages] [Bug 1795407] Re: python-apt frontend locking

[Julian Andres Klode]

** Description changed:

  [Impact]
  Add support to python-apt for frontend locking. This is a bit more 
complicated, and also requires some other restructuring:
  
  (1) The archives lock was only taken for a short time, when it should
  have been kept for the duration of an installation, as otherwise debs
  could disappear from archives/ while the install is running.
  
  (2) There was no lock handling at all. Tools essentially acquire the
  lock, and then release it before commit().
  
  The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage
  both the frontend and the normal lock, and allows code to call
  apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner()
  around dpkg invocations to release the inner lock.
  
  Cache.commit() takes care of locking itself now. It releases the inner
  lock as needed for dpkg invocations. It also now requires
  apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself.
  
  [Test case]
  1. Mark a package in the cache for install/removal and commit() - FE lock 
should be taken while dpkg is running.
  2. Mark a package in the cache for install/removal and commit() while holding 
the lock. Releasing the lock afterwards should still work correctly, and the FE 
lock should never be released
  3. Observe that the archive lock is not released until the last dpkg run
  
  The locking behavior can be observed via strace.
  
  [Regression potential]
  The dpkg lock changed the most: Some lock counting might go wrong and 
programs might fail as a result. Any problems will be isolated, though - dpkg 
still acquires its locks, and if a lock miscount happens, apt would not tell 
dpkg to skip acquiring the frontend lock, so even if we were losing the lock 
anywhere, dpkg would still try to acquire it and not run unlocked.
  
  The archive lock done by commit()/fetch_archives() in apt.Cache() is now
  hold as long as the fetcher object exists though (as it uses the
  fetcher's get_lock method), which might cause unexpected behavior in
  apps not expecting that.
  
  The lists/ lock is unaffected by the changes, so there should not be any
  regressions when it comes to updating index files.
  
  [Other info (1)]
  CI changes: There were some improvements to type hints for mypy needed to 
make type checks pass, and changes to the CI's Dockerfile to pull a new apt 
from the apt stable PPA (as a new enough apt is only in unapproved atm). 
Neither of those files are used anywhere outside of the package, so they should 
not cause any problems.
  
  [Other info (2)]
  This is part of a wider series of SRUs for frontend locking
  
  - dpkg (bug 1796081)
  - apt (bug 1781169)
  - python-apt (bug 1795407)
  - packagekit (bug 1795614)
  - unattended-upgrades (bug 1789637)
  - aptdaemon (no bug filed yet)
  
  Further details about frontend locking can be found in
  https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
  
  - This SRU depends on the apt SRU above, and breaks unattended-upgrades
  in bionic without its SRU due to a bug in the u-u code in handling the
  new API.
+ 
+ - xenial depends on unattended-upgrades SRU

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

Title:
  python-apt frontend locking

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Add support to python-apt for frontend locking. This is a bit more 
complicated, and also requires some other restructuring:

  (1) The archives lock was only taken for a short time, when it should
  have been kept for the duration of an installation, as otherwise debs
  could disappear from archives/ while the install is running.

  (2) There was no lock handling at all. Tools essentially acquire the
  lock, and then release it before commit().

  The fix is based on the apt fix, which makes apt_pkg.SystemLock()
  manage both the frontend and the normal lock, and allows code to call
  apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner()
  around dpkg invocations to release the inner lock.

  Cache.commit() takes care of locking itself now. It releases the inner
  lock as needed for dpkg invocations. It also now requires
  apt_pkg.SystemLock to be hold - if it is not, it will acquire it
  itself.

  [Test case]
  1. Mark a package in the cache for install/removal and commit() - FE lock 
should be taken while dpkg is running.
  2. Mark a package in the cache for install/removal and commit() while holding 
the lock. Releasing the lock afterwards should still work correctly, and the FE 
lock should never be released
  3. Observe that the archive lock is not released until the last dpkg run

  The locking behavior can be observed via strace.

  [Regression potential]
  The dpkg lock ch

[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

[Ganesh Bhat]

Work-around  : User arrow keys and press space to select

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Tiago Maurício]

I am running Ubuntu 16.04 with plasma. I was experiencing this issue and
downgraded the network-manager package to 1.2.2-0ubuntu0.16.04.4. Since
the downgrade I haven't had any trouble. Waiting for fix in the latest
version :)

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1803749] Re: apt.Cache.clear() may set apt.Package.is_auto_removable to False

[Balint Reczey]

** Description changed:

+ [Impact]
+ 
+  * Originally autoremovable packages can be removed as newly autoremovable 
ones by unattended-upgrades
+  * This can surprise users potentially removing packages which are needed for 
the system's operation.
+ 
+ [Test Case]
+ 
+  * WIP, see Original Bug Test
+ 
+ [Regression Potential]
+ 
+  * Unattended-upgrades may use more CPU-time for operation but I did not 
observe a significant increase. Autopkgtest measures u-u's performance thus if 
this regression occurs, we can observe it easily.
+  * Due to the code changes u-u may still remove already autoremovable 
packages or fail to remove newly autoremovable ones in default configuration, 
but since the code became simpler with the change by eliminating an 
optimization this regression is unlikely to take place.
+ 
+ [Original Bug Text]
+ 
  While triaging LP: #1803587 I found that originally autoremovable
  packages were handled as newly autoremovable ones by unattended-upgrades
  due to not finding all of them at the beginning of u-u's run.
  
  The root cause seems to be cache.clear() resetting pkg.is_auto_removable
  to False under some circumstances I haven't fully narrowed down.
  
- The reproduction is as follows:
- Set up a Bionic (or later) system with autoremovable packages, packages 
upgradable from -security and blacklist at least one upgradable package and 
apply the following patch to u-u:
- 
+ Set up a Bionic (or later) system with autoremovable packages, packages
+ upgradable from -security and blacklist at least one upgradable package
+ and apply the following patch to u-u:
  
  root@bb-1803587:~# diff -Naur /usr/bin/unattended-upgrade.orig 
/usr/bin/unattended-upgrade
  --- /usr/bin/unattended-upgrade.orig  2018-11-16 16:17:58.522583254 +
  +++ /usr/bin/unattended-upgrade   2018-11-16 16:36:12.226675870 +
  @@ -948,7 +948,9 @@
-  def rewind_cache(cache, pkgs_to_upgrade):
-  # type: (apt.Cache, List[apt.Package]) -> None
-  """ set the cache back to the state with packages_to_upgrade """
+  def rewind_cache(cache, pkgs_to_upgrade):
+  # type: (apt.Cache, List[apt.Package]) -> None
+  """ set the cache back to the state with packages_to_upgrade """
  +print([pkg.name  for pkg in cache if pkg.is_auto_removable])
-  cache.clear()
+  cache.clear()
  +print([pkg.name for pkg in cache if pkg.is_auto_removable])
-  for pkg2 in pkgs_to_upgrade:
-  pkg2.mark_install(from_user=not pkg2.is_auto_installed)
-  if cache.broken_count > 0:
+  for pkg2 in pkgs_to_upgrade:
+  pkg2.mark_install(from_user=not pkg2.is_auto_installed)
+  if cache.broken_count > 0:
  
+ Run u-u to observe cache.clear() resetting the list of autoremovable
+ packages:
  
- Run u-u to observe cache.clear() resetting the list of autoremovable packages:
- 
-  ~# /usr/bin/unattended-upgrade --dry-run --verbose --debug
+  ~# /usr/bin/unattended-upgrade --dry-run --verbose --debug
  Initial blacklisted packages: systemd
- Initial whitelisted packages: 
+ Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  Using 
(^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-modules-.*|^linux-modules-.*|^linux-tools|^linux-cloud-tools)
 regexp to find kernel packages
  Using 
(^linux-image.*4.15.0-38-generic|^linux-headers.*4.15.0-38-generic|^linux-image-extra.*4.15.0-38-generic|^linux-modules.*4.15.0-38-generic|^linux-modules-extra.*4.15.0-38-generic|^linux-signed-image.*4.15.0-38-generic|^kfreebsd-image.*4.15.0-38-generic|^kfreebsd-headers.*4.15.0-38-generic|^gnumach-image.*4.15.0-38-generic|4.15.0-38-generic.*-modules|4.15.0-38-generic.*-kernel|^linux-backports-modules-.*.*4.15.0-38-generic|^linux-modules-.*.*4.15.0-38-generic|^linux-tools.*4.15.0-38-generic|^linux-cloud-tools.*4.15.0-38-generic)
 regexp to find running kernel packages
  Checking: apport ([])
  adjusting candidate version: apport=2.20.9-0ubuntu7.1
  ...
  Checking: libnss-systemd ([, 
])
  skipping blacklisted package systemd
  pkg systemd package has been blacklisted
  sanity check failed
  ['libfreetype6']
  []
  ...

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

Title:
  apt.Cache.clear() may set apt.Package.is_auto_removable to False

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Originally autoremovable packages can be removed as newly autoremovable 
ones by unattended-upgrades
   * This can surprise users potentially removing packages which are needed for 
the system's operation.

  [Test Case]

   * WIP, see Original Bug Test

  [Regression Potential]

   * Unatten

[Touch-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

[Lisa byron]

** Changed in: gnome-keyring (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

Status in seahorse:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  on hardy (preserved home folder from feisty) i get the following when
  i try to ssh

  Agent admitted failure to sign using the key.
  Permission denied (publickey).

  or with verbose on

  sam@titania:~$ ssh -v oberon
  OpenSSH_4.7p1 Debian-4ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
  debug1: Reading configuration data /home/sam/.ssh/config
  debug1: Applying options for oberon
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: Applying options for *
  debug1: Connecting to ## [##] port ##.
  debug1: Connection established.
  debug1: identity file /home/sam/.ssh/identity type -1
  debug1: identity file /home/sam/.ssh/id_rsa type 1
  debug1: identity file /home/sam/.ssh/id_dsa type -1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_4.6p1 
Debian-5ubuntu0.1
  debug1: match: OpenSSH_4.6p1 Debian-5ubuntu0.1 pat OpenSSH*
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-4ubuntu1
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server->client aes128-cbc hmac-md5 none
  debug1: kex: client->server aes128-cbc hmac-md5 none
  debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
  debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
  debug1: using hostkeyalias: oberon
  debug1: Host 'oberon' is known and matches the RSA host key.
  debug1: Found key in /home/sam/.ssh/known_hosts:1
  debug1: ssh_rsa_verify: signature correct
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey
  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/sam/.ssh/id_rsa
  debug1: Server accepts key: pkalg ssh-rsa blen 277
  Agent admitted failure to sign using the key.
  debug1: Trying private key: /home/sam/.ssh/identity
  debug1: Trying private key: /home/sam/.ssh/id_dsa
  debug1: No more authentication methods to try.
  Permission denied (publickey).

  I tried generating a new key. this worked for a few logons, but then i
  get back to this error.

  I think it is to do with the local key agent. i found that
   SSH_AUTH_SOCK=0 ssh oberon
  works fine.

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

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

[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships

[Thadeu Lima de Souza Cascardo]

Upstream discussion is progressing. I have tested some patches from hch,
will send him some feedback later today and post the links here.

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Invalid

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
00

[Touch-packages] [Bug 1804748] Re: s390x qemu vt220 terminal, tput cols and lines is wrong

[Frank Heimes]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => bugproxy (bugproxy)

** Changed in: ubuntu-z-systems
   Status: New => Triaged

** Tags added: reverse-proxy-bugzilla

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

Title:
  s390x qemu vt220 terminal, tput cols and lines is wrong

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in ncurses package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New

Bug description:
  s390x qemu vt220 terminal, tput cols and lines is reported as 80x24,
  whilst that's not true.

  The number of columns is semi-true, as the shell wraps them, however,
  one can print things beyond 80 cols.

  Ideally resizing qemu window, should manage to report the actual
  number of lines and columns to the underlying terminal.

  Similarly, one should be able to resize ASCII terminal window in HMC
  beyond 80x24.

  These days everyone has HD widescreen monitors, there is no reason to
  limit to 80x24.

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

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

[Touch-packages] [Bug 1803749] Re: apt.Cache.clear() may set apt.Package.is_auto_removable to False

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 1.8

---
unattended-upgrades (1.8) unstable; urgency=medium

  * Add note about increasing InhibitDelayMaxSec for InstallOnShutdown to
50unattended-upgrades.
  * Ship historical md5sums of /etc/apt/apt.conf.d/50unattended-upgrades for ucf
  * Remove .ucf-* configuration file copies on purge
  * Add NEWS entry about increasing InhibitDelayMaxSec and InstallOnShutdown
changes
  * Revert to WantedBy=multi-user.target from 1.5ubuntu3 and 1.7, too, on
Ubuntu. 1.5ubuntu4 is the first fixed version on and 1.7 did not upgrade
properly from 1.5ubuntu3.
  * List commented-out default values in 50unattended-upgrades config file.
Always list the default value commented out unless the explanation clearly
states the default value.
  * Transition obsolete 50unattended-upgrades conffile to ucf prior upgrades did
not do that (Closes: #808336)
  * Speed up ordering of packages in which minimal upgrade steps are performed.
  * Stop using ActionGroups, they interfere with apt.Cache.clear() causing all
autoremovable packages to be handled as newly autoremovable ones and be
removed by default. Dropping ActionGroup usage does not slow down the
most frequent case of not having anything to upgrade and when ther are
packages to upgrade the gain is small compared to the actual package
installation.
Also collect autoremovable packages before adjusting candidates because that
also changed .is_auto_removable attribute of some of them. (LP: #1803749)
(Closes: #910874)
  * Fix pyflakes

 -- Balint Reczey   Wed, 21 Nov 2018 17:02:49 +0100

** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  apt.Cache.clear() may set apt.Package.is_auto_removable to False

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * Originally autoremovable packages can be removed as newly autoremovable 
ones by unattended-upgrades
   * This can surprise users potentially removing packages which are needed for 
the system's operation.

  [Test Case]

   * WIP, see Original Bug Test

  [Regression Potential]

   * Unattended-upgrades may use more CPU-time for operation but I did not 
observe a significant increase. Autopkgtest measures u-u's performance thus if 
this regression occurs, we can observe it easily.
   * Due to the code changes u-u may still remove already autoremovable 
packages or fail to remove newly autoremovable ones in default configuration, 
but since the code became simpler with the change by eliminating an 
optimization this regression is unlikely to take place.

  [Original Bug Text]

  While triaging LP: #1803587 I found that originally autoremovable
  packages were handled as newly autoremovable ones by unattended-
  upgrades due to not finding all of them at the beginning of u-u's run.

  The root cause seems to be cache.clear() resetting
  pkg.is_auto_removable to False under some circumstances I haven't
  fully narrowed down.

  Set up a Bionic (or later) system with autoremovable packages,
  packages upgradable from -security and blacklist at least one
  upgradable package and apply the following patch to u-u:

  root@bb-1803587:~# diff -Naur /usr/bin/unattended-upgrade.orig 
/usr/bin/unattended-upgrade
  --- /usr/bin/unattended-upgrade.orig  2018-11-16 16:17:58.522583254 +
  +++ /usr/bin/unattended-upgrade   2018-11-16 16:36:12.226675870 +
  @@ -948,7 +948,9 @@
   def rewind_cache(cache, pkgs_to_upgrade):
   # type: (apt.Cache, List[apt.Package]) -> None
   """ set the cache back to the state with packages_to_upgrade """
  +print([pkg.name  for pkg in cache if pkg.is_auto_removable])
   cache.clear()
  +print([pkg.name for pkg in cache if pkg.is_auto_removable])
   for pkg2 in pkgs_to_upgrade:
   pkg2.mark_install(from_user=not pkg2.is_auto_installed)
   if cache.broken_count > 0:

  Run u-u to observe cache.clear() resetting the list of autoremovable
  packages:

   ~# /usr/bin/unattended-upgrade --dry-run --verbose --debug
  Initial blacklisted packages: systemd
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  Using 
(^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-modules-.*|^linux-modules-.*|^linux-tools|^linux-cloud-tools)
 regexp to find kernel packages
  Using 
(^linux-image.*4.15.0-38-generic|^linux-headers.*4.15.0-38-generic|^linux-image-extra.*4.15.0-38-generic|^linux-modules.*4.15.0-38-generic|^linux-modules-extra.*4.15.0

[Touch-packages] [Bug 1804748] Re: s390x qemu vt220 terminal, tput cols and lines is wrong

[bugproxy]

** Tags added: architecture-s39064 bugnameltc-173564 severity-high
targetmilestone-inin1804

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

Title:
  s390x qemu vt220 terminal, tput cols and lines is wrong

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in ncurses package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New

Bug description:
  s390x qemu vt220 terminal, tput cols and lines is reported as 80x24,
  whilst that's not true.

  The number of columns is semi-true, as the shell wraps them, however,
  one can print things beyond 80 cols.

  Ideally resizing qemu window, should manage to report the actual
  number of lines and columns to the underlying terminal.

  Similarly, one should be able to resize ASCII terminal window in HMC
  beyond 80x24.

  These days everyone has HD widescreen monitors, there is no reason to
  limit to 80x24.

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

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

[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs

[crush]

Same issue here! No SSH-Daemon will start again! Happens after Shutdown,
just a Reboot shouldn't affect the System.

received the package via unattended security updates (?)

2018-11-21 06:55:30 upgrade systemd:amd64 229-4ubuntu21.8
229-4ubuntu21.9

No relevance at all with btrfs, we use ext4


** Summary changed:

- systemd-tmpfiles-setup.service fails on btrfs
+ systemd-tmpfiles-setup.service fails

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

Title:
  systemd-tmpfiles-setup.service fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service
  fails with:

  Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and 
Directories...
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/var": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/home": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/srv": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed 
with result 'exit-code'.
  Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files 
and Directories.

  This happens on btrfs root filesystems in real hardware and on our
  virtualized servers as well. 237-3ubuntu10.6 didnt show this errors
  and going back to 237-3ubuntu10 removes them as well.

  # lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  # apt-cache policy systemd
  systemd:
Installiert:   237-3ubuntu10.9
Installationskandidat: 237-3ubuntu10.9
Versionstabelle:
   *** 237-3ubuntu10.9 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1805151] [NEW] Desktop freeze running VirtualBox, Intel graphics

[Michael Thayer]

Public bug reported:

This is identical to bug 1804885, but as requested I am filing this while 
running the standard Ubuntu kernel.  I will copy and paste my summary below.  
Updates since I created that bug:
 * This occurs with the mainline PPA 4.18.12-041812-generic kernel.
 * The glxinfo section I include below is identical with 4.18.0-11-generic 
(presumably no surprise).
 * I would appreciate a bit of hand-holding for bisecting this.  Does the 
kernel team have ready-built kernel packages for bisecting?  Or guidance about 
the fastest way of doing it (i.e. not rebuilding things which do not need to be 
rebuilt for successive rounds)?

=== Original report follows ===

When I start a VirtualBox virtual machine (reproducible with the Ubuntu
18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA
emulation and 3D pass-through enabled, my system hangs. Sometimes I can
recover if I get to a VT fast enough to kill the process. Also, the OOM
killer sometimes triggers and kills the process or gnome-shell, but the
OOM killer entries in dmesg look like neither of the two are using
excessive memory compared to available system RAM. When I switch to the
Ubuntu drm-tip kernel packages from the kernel PPA the problem goes
away. Debugging shows that the hang occurs during the first
glXMakeCurrent call made by the application. It did not occur using the
standard Ubuntu kernel but running the application under apitrace. I can
provide the trace if that helps.

Short extract from glxinfo running the 4.20 drm-tip kernel:

Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916)
Version: 18.2.2
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperVersion: 1.399
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 26 15:01:53 2018
DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:2245]
InstallationDate: Installed on 2018-06-12 (166 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20HES0E73E
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash 
crashkernel=384M-:128M
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to cosmic on 2018-10-08 (49 days ago)
dmi.bios.date: 09/13/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1QET78W (1.53 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HES0E73E
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470
dmi.product.name: 20HES0E73E
dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470
dmi.product.version: ThinkPad T470
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic freeze third-party-packages ubuntu 
wayland-session

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

Title:
   Desktop freeze ru

[Touch-packages] [Bug 1718231] Re: Mismatch in type-ahead search of the GTKFileChooser causes the first file to get the focus

[Sebastien Bacher]

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

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

Title:
  Mismatch in type-ahead search of the GTKFileChooser causes the first
  file to get the focus

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 17.10 dev with libgtk-3-0 3.22.19-0ubuntu1 and
  initially this issue was reported at
  https://bugzilla.gnome.org/show_bug.cgi?id=764668 . If the
  GTKFileChooser gets opened and something is typed that causes a
  mismatch the first file gets deselected but instead it gets now a
  focus (which it hadn't before) which might be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1718231/+subscriptions

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

[Touch-packages] [Bug 1760240] Re: Write past end of buffer in gtk/gtkrc.c gtk_rc_add_default_file

[Sebastien Bacher]

Thank you for your bug report, that looks like an upstream issue and
should be reported on https://gitlab.gnome.org/GNOME/gtk/issues

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Write past end of buffer in gtk/gtkrc.c gtk_rc_add_default_file

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  In all repositories there is a buffer-overrun in the function
  gtk_rc_add_default_file(), where if the dynamic array
  gtk_rc_default_files has exactly max_default_files entries, a NULL
  will be written past the allocated memory.  The resize function does
  not resize the null terminated array in this case, and address
  sanitizer (and valgrind) detects a memory access violation in any code
  leading to this function.

  The following code is in error ( from 
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596
 )
  {{{
for (n = 0; n < max_default_files; n++) 
  {
if (gtk_rc_default_files[n] == NULL)
break;
  }

if (n == max_default_files)
  {
max_default_files += 10;
gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
  }

gtk_rc_default_files[n++] = g_strdup (filename);
gtk_rc_default_files[n] = NULL;
  }}}

  Proposed modified implementation is as follows:
  {{{
for (n = 0; n < (max_default_files-1); n++) 
  {
if (gtk_rc_default_files[n] == NULL)
break;
  }

if (n >= (max_default_files-1))
  {
max_default_files += 10;
gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
  }

gtk_rc_default_files[n++] = g_strdup (filename);
gtk_rc_default_files[n] = NULL;
  }}}

  This implementation should be changed in all branches:

  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-updates/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-proposed/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise/view/head:/gtk/gtkrc.c#L590
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-updates/view/head:/gtk/gtkrc.c#L596
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1760240/+subscriptions

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

[Touch-packages] [Bug 1763591] Re: dlmopen glib2.0 crashed in g_variant_lookup_value

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software on https://gitlab.gnome.org/GNOME/glib/issues/

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  dlmopen glib2.0 crashed in g_variant_lookup_value

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  when dlmopen glib2.0 and the program is linked with pthread, glib2.0 crashed 
in g_variant_lookup_value when dlmopen with 
  LM_ID_NEWLM

  following is the poc:

  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 

  
  int main(int argc, char*argv[])
  {
char buf[4096] = {0};
pthread_attr_t attr;

pthread_attr_init(&attr);
snprintf(buf, sizeof(buf), "/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2");
dlmopen(-1, buf, RTLD_NOW|RTLD_LOCAL);
return 0;
  }

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

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

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

[bugproxy]

--- Comment From mihaj...@de.ibm.com 2018-11-26 10:49 EDT---
This is - unfortunately - true for every serial console (nothing specific to 
s390), as there's no architected interface to transport console size changes. 
By running /usr/bin/resize, the actual cols/rows will be set.

See also https://unix.stackexchange.com/questions/16578/resizable-
serial-console-window/283206

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

Title:
  s390x qemu vt220 terminal, tput cols and lines is wrong

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in ncurses package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New

Bug description:
  s390x qemu vt220 terminal, tput cols and lines is reported as 80x24,
  whilst that's not true.

  The number of columns is semi-true, as the shell wraps them, however,
  one can print things beyond 80 cols.

  Ideally resizing qemu window, should manage to report the actual
  number of lines and columns to the underlying terminal.

  Similarly, one should be able to resize ASCII terminal window in HMC
  beyond 80x24.

  These days everyone has HD widescreen monitors, there is no reason to
  limit to 80x24.

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

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

[Touch-packages] [Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend

[Claude van Ackere]

This happens from time to time in CAJA and when launching VLC.

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

Title:
  at-spi-bus-launcher makes Xorg crash when resuming from suspend

Status in at-spi2-core package in Ubuntu:
  Confirmed

Bug description:
  If at-spi2-core is installed, when resuming from suspend messages like
  these are logged in systemd journal:

  at-spi-bus-launcher[31720]: XIO:  fatal IO error 11 (Resource temporarily 
unavailable) on X server ":0.0"
  at-spi-bus-launcher[31720]:   after 8065 requests (8065 known processed) 
with 0 events remaining.

  The number of requests vary, it can reach more than 15000. Depending
  on the number of requests, the Xorg server crashes with SIGBUS.
  Depending on the exact moment Xorg crashes, when lightdm manages to
  recover, it shows a login greeter, or worst case scenario, it can't
  recover, a black screen is shown and the desptop session doesn't
  start.

  It took me a long time to discover the cause. The visible symptom was:
  once in a while when resuming from suspend, I got a login greeter
  instead of an unlock greeter, or a black screen which forced me to
  power down. Investigating, I found out that whenever that happened,
  there was a Xorg core left behind. Looking at the journal messages
  before the crash, there was always that flood of at-spi2-core
  requests. So I uninstalled at-spi2-core and Xorg never crashed
  anymore.

  This is a quite severe bug, which makes it impossible to use at-
  spi2-core.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: at-spi2-core (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jun  6 09:10:12 2018
  InstallationDate: Installed on 2018-04-28 (38 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: at-spi2-core
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions

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

[Touch-packages] [Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend

[Claude van Ackere]

-- Logs begin at Thu 2018-11-01 16:00:55 CET, end at Mon 2018-11-26 16:45:36 
CET. --
nov. 26 16:42:47 claude-M61PME-S2P mintmenu[12883]: mintMenu.py: Fatal IO error 
11 (Ressource temporairement non dispo
nov. 26 16:42:47 claude-M61PME-S2P unknown[12887]: clock-applet: Fatal IO error 
11 (Ressource temporairement non dispo
nov. 26 16:42:47 claude-M61PME-S2P at-spi-bus-launcher[12832]: XIO:  fatal IO 
error 11 (Resource temporarily unavailab
nov. 26 16:42:47 claude-M61PME-S2P at-spi-bus-launcher[12832]:   after 5057 
requests (5057 known processed) with 0
nov. 26 16:42:47 claude-M61PME-S2P unknown[12889]: notification-area-applet: 
Fatal IO error 11 (Ressource temporaireme
nov. 26 16:42:47 claude-M61PME-S2P unknown[12885]: wnck-applet: Fatal IO error 
11 (Ressource temporairement non dispon
nov. 26 16:42:47 claude-M61PME-S2P polkitd(authority=local)[698]: Unregistered 
Authentication Agent for unix-session:c
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 12397 (lightdm) with signal SIGTERM.
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 12415 (gnome-keyring-d) with signal 
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 12762 (ssh-agent) with signal SIGTER
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 12912 (applet.py) with signal SIGTER
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 13265 (dbus-launch) with signal SIGT
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing 
process 13931 (xplayer) with signal SIGTERM.
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: Stopping Session c12 of user 
claude.
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: Stopped Session c12 of user 
claude.
nov. 26 16:42:47 claude-M61PME-S2P systemd-logind[628]: Removed session c12.
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so:
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM adding faulty module: 
pam_kwallet.so
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.s
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM adding faulty module: 
pam_kwallet5.so

Lightdm ends on login screen

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

Title:
  at-spi-bus-launcher makes Xorg crash when resuming from suspend

Status in at-spi2-core package in Ubuntu:
  Confirmed

Bug description:
  If at-spi2-core is installed, when resuming from suspend messages like
  these are logged in systemd journal:

  at-spi-bus-launcher[31720]: XIO:  fatal IO error 11 (Resource temporarily 
unavailable) on X server ":0.0"
  at-spi-bus-launcher[31720]:   after 8065 requests (8065 known processed) 
with 0 events remaining.

  The number of requests vary, it can reach more than 15000. Depending
  on the number of requests, the Xorg server crashes with SIGBUS.
  Depending on the exact moment Xorg crashes, when lightdm manages to
  recover, it shows a login greeter, or worst case scenario, it can't
  recover, a black screen is shown and the desptop session doesn't
  start.

  It took me a long time to discover the cause. The visible symptom was:
  once in a while when resuming from suspend, I got a login greeter
  instead of an unlock greeter, or a black screen which forced me to
  power down. Investigating, I found out that whenever that happened,
  there was a Xorg core left behind. Looking at the journal messages
  before the crash, there was always that flood of at-spi2-core
  requests. So I uninstalled at-spi2-core and Xorg never crashed
  anymore.

  This is a quite severe bug, which makes it impossible to use at-
  spi2-core.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: at-spi2-core (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jun  6 09:10:12 2018
  InstallationDate: Installed on 2018-04-28 (38 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: at-spi2-core
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions

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

[Touch-packages] [Bug 1778767] Re: iPhone doesn't charge when plugged in after disconnect

[Leo Soares]

where can I track the progress of the fix until it gets released in
bionic? i cant seem to find it in sru

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

Title:
  iPhone doesn't charge when plugged in after disconnect

Status in usbmuxd package in Ubuntu:
  Fix Released
Status in usbmuxd source package in Bionic:
  Fix Committed
Status in usbmuxd package in Debian:
  New

Bug description:
  * Impact
  the usbmuxd service is not restarted after disconnecting/reconnecting a 
device, which means users need to reboot (or use the command line to activate 
the service) to have their iphone handled a second time in a session

  * Test case
  - open an Ubuntu/GNOME session and connect an iphone
  - disconnect the device
  - connect it again

  -> it should be handled the second time like it was the first time

  * Regression potential
  The changes are in the udev rule, just make sure that idevices are correctly 
detected when connected

  
  

  
  Plugging in the iPhone via usb will charge the iPhone after reboot, but after 
disconnect usbmuxd's systemctl service is inactive and does not start.

  Problem and workaround documented here:

  https://ubuntuforums.org/showthread.php?t=2376741&p=13779062#post13779062

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

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

[Touch-packages] [Bug 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager

[Sebastien Bacher]

The issue was fixed in cosmic and the fix was part of that SRU update to bionic
https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.1

** Changed in: glib2.0 (Ubuntu)
   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/1773334

Title:
  Ubuntu 18.04 mounted network shares not appearing under devices in
  file manager

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  Apologies if this is not the correct package to file this
  bug/regression against.

  On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when
  mounting network shares (SMB and NFS) they no longer appear under
  Devices in file manager (Nautilus or Caja), the mounts do succeed and
  are accessible at their mount points.

  In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of
  mounted network shares on Ubuntu Mate 17.10 attached)

  I am using the following code to mount NFS shares

  `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup
  /media/philroche/photobackup`

  and for SMB shares

  `sudo mount.cifs //192.168.2.123/photobackup
  /media/philroche/photobackup`

  Is this a bug/regression, or perhaps it is an intentional change?

  I did ask this on IRC in #ubuntu and askubuntu.com but no reply.

  Expected behaviour:

  I expected the mounted network shares to appear under Devices in File
  manager

  Actual behaviour:

  Mounting network shares does succeed as expected but does not appear
  under Devices in File manager as it did in previous releases.

  Requested details:

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  udisks2:
Installed: 2.7.6-3
Candidate: 2.7.6-3
Version table:
   *** 2.7.6-3 500
  500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1805178] [NEW] Apparmor should include letsencrypt directory for Slapd

[Tarek Loubani]

Public bug reported:

Apparmor denies access to /etc/letsencrypt for slapd, which is confusing
for users trying to secure ldap with Letsencrypt in a stock
configuration.

The fix is inserting the following line in
/etc/apparmor.d/usr.sbin.slapd:

  /etc/letsencrypt/** r,

and then refreshing the profile:

# apparmor_parser -vr usr.sbin.slapd

This line should simply be included.

tarek : )

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

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

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

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

Title:
  Apparmor should include letsencrypt directory for Slapd

Status in apparmor package in Ubuntu:
  New
Status in openldap package in Ubuntu:
  New

Bug description:
  Apparmor denies access to /etc/letsencrypt for slapd, which is
  confusing for users trying to secure ldap with Letsencrypt in a stock
  configuration.

  The fix is inserting the following line in
  /etc/apparmor.d/usr.sbin.slapd:

/etc/letsencrypt/** r,

  and then refreshing the profile:

  # apparmor_parser -vr usr.sbin.slapd

  This line should simply be included.

  tarek : )

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

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

[Touch-packages] [Bug 1805048] Re: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or crackling sound. It's not my microphone, it's every audio input... Audio output is fine

[Paul]

*tried ;-)
And thank you for helping !

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

Title:
  [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or
  crackling sound. It's not my microphone, it's every audio input...
  Audio output is fine

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Motherboard : MSI B350M BAZOOKA

  It happens all the time, and with every audio input...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  p4ul1  1433 F pulseaudio
   /dev/snd/pcmC1D0c:   p4ul1  1433 F...m pulseaudio
   /dev/snd/pcmC1D0p:   p4ul1  1433 F...m pulseaudio
   /dev/snd/controlC1:  p4ul1  1433 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Nov 25 21:40:48 2018
  InstallationDate: Installed on 2018-11-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Pink Mic, Front
  Symptom_PulseAudioLog:
   Nov 25 21:02:45 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.32' (uid=121 pid=1123 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Nov 25 21:02:46 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.59' (uid=121 pid=1123 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M BAZOOKA (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.70:bd09/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350MBAZOOKA(MS-7A38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1803137] Re: Unattended-upgrades may keep running after unmounting local filesystems in InstallOnShutdown mode

[Łukasz Zemczak]

Hello Balint, or anyone else affected,

Accepted unattended-upgrades into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.5ubuntu3.18.10.0 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unattended-upgrades (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Unattended-upgrades may keep running after unmounting local
  filesystems in InstallOnShutdown mode

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Unattended-upgrades may keep running during shutdown even beyond 
unmounting local filesystems potentially leaving a broken installation behind.
   * The fix reverts the original fix of LP: #1778219 and applies a different 
one starting unattended-upgrades-shutdown _before_ the shutdown transaction 
starts/

  [Test Case]

   * Run unattended-upgrades in InstallOnShutdown mode and observe it
  being finished installing a few packages _before_ the shutdown
  transaction starts:

  $ lxc launch ubuntu:18.10 cc-uu-onshutdown
  Creating cc-uu-onshutdown
  Starting cc-uu-onshutdown
  $ lxc shell cc-uu-onshutdown
  mesg: ttyname failed: No such device
  root@cc-uu-onshutdown:~# apt update -qq
  33 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@cc-uu-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' 
> /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@cc-uu-onshutdown:~# dbus-send --system --print-reply 
--dest=org.freedesktop.login1 /org/freedesktop/login1 
"org.freedesktop.login1.Manager.Reboot" boolean:false
  method return time=1542112922.046290 sender=:1.4 -> destination=:1.13 
serial=27 reply_serial=2

  Session terminated, terminating shell...$
  $ lxc shell cc-uu-onshutdown
  mesg: ttyname failed: No such device
  root@cc-uu-onshutdown:~# journalctl -l
  ...
  Nov 13 12:50:10 cc-uu-shutdown systemd[1]: Started Unattended Upgrades 
Shutdown.
  Nov 13 12:51:17 cc-uu-shutdown systemd-logind[228]: System is rebooting.

  ...
  root@cc-uu-shutdown:~# cat 
/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
  ...
  2018-11-13 12:51:13,835 WARNING - Running unattended-upgrades in shutdown mode
  2018-11-13 12:51:13,852 WARNING - Unattended-upgrade in progress during 
shutdown, please don't turn off the computer
  2018-11-13 12:51:15,482 WARNING - Unattended-upgrade in progress during 
shutdown, please don't turn off the computer
  2018-11-13 12:51:17,151 WARNING - Unattended-upgrade in progress during 
shutdown, please don't turn off the computer
  2018-11-13 12:51:17,166 INFO - All upgrades installed

  [Regression Potential]

   * The change reverts the behavior of unattended-upgrades-shutdown to
  be close to the behavior observed in Ubuntu 18.04, blocking the
  shutdown process reliably until is unattended-upgrades finished, but
  it starts _before_ shutdown triggered by the PrepareForShutdown()
  signal. Due to the shutdown not fully starting yet users may not get
  visual notification of unattended-upgrades running.

  In my testing on Bionic when a logged-in user shuts down the system
  when InstallOnShutdown is configured the user is dropped out to the
  login manager and nothing shows that u-u is running behind the screens
  for 30s, when the inhibition timer expires and u-u is starting to
  gracefully stop and the usual text appears after the login manager
  exits and plymouth shutdown screen is shown. The fix would be the
  login manager also monitoring PrepareForShutdown() and exiting (LP:
  #1803581).

  On Xenial (with Unity) starting shutdown from the graphical session
  does not log the user out nor show

[Touch-packages] [Bug 1805048] Re: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or crackling sound. It's not my microphone, it's every audio input... Audio output is fine

[Paul]

I'm using a jack connector. I use a steelseries arctis 3 but I tries
with other mics.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1805048/+attachment/5216539/+files/journal.txt

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

Title:
  [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or
  crackling sound. It's not my microphone, it's every audio input...
  Audio output is fine

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Motherboard : MSI B350M BAZOOKA

  It happens all the time, and with every audio input...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  p4ul1  1433 F pulseaudio
   /dev/snd/pcmC1D0c:   p4ul1  1433 F...m pulseaudio
   /dev/snd/pcmC1D0p:   p4ul1  1433 F...m pulseaudio
   /dev/snd/controlC1:  p4ul1  1433 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Nov 25 21:40:48 2018
  InstallationDate: Installed on 2018-11-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Pink Mic, Front
  Symptom_PulseAudioLog:
   Nov 25 21:02:45 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.32' (uid=121 pid=1123 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Nov 25 21:02:46 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.59' (uid=121 pid=1123 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M BAZOOKA (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.70:bd09/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350MBAZOOKA(MS-7A38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1805040] Re: Apparently "Readline6" is not in Ubuntu 18.4.1 LTS but I need it

[Hans Joachim Desserud]

Thanks for reporting.

Looks like readline6 was removed intentionally, see
https://launchpad.net/ubuntu/+source/readline6/+publishinghistory or
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877240 for details.

Ideally the applications should be ported to readline7, which is
currently supported and available in Ubuntu 18.04. If that isn't
possible, you may be able to manually install the older readline6
packages from an older Ubuntu release. Beware that this might conflict
with the newer readline version and may cause problems for other
packages which now expect readline7.

(I wasn't sure whether this should be converted to a question, so I left
it as a bug report)

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

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

Title:
  Apparently "Readline6" is not in Ubuntu 18.4.1 LTS but I need it

Status in readline6 package in Ubuntu:
  New

Bug description:
  I use applications that require Readline6.  But Ubuntu 18.4.1 does not
  seem to have it - how can Iget it?

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

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

[Touch-packages] [Bug 1805151] Re: Desktop freeze running VirtualBox, Intel graphics

[Michael Thayer]

Update: 4.19.4-041904-generic is affected, 4.20.0-042000rc1-generic is
not.

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

Title:
   Desktop freeze running VirtualBox, Intel graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  This is identical to bug 1804885, but as requested I am filing this while 
running the standard Ubuntu kernel.  I will copy and paste my summary below.  
Updates since I created that bug:
   * This occurs with the mainline PPA 4.18.12-041812-generic kernel.
   * The glxinfo section I include below is identical with 4.18.0-11-generic 
(presumably no surprise).
   * I would appreciate a bit of hand-holding for bisecting this.  Does the 
kernel team have ready-built kernel packages for bisecting?  Or guidance about 
the fastest way of doing it (i.e. not rebuilding things which do not need to be 
rebuilt for successive rounds)?

  === Original report follows ===

  When I start a VirtualBox virtual machine (reproducible with the
  Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with
  VMSVGA emulation and 3D pass-through enabled, my system hangs.
  Sometimes I can recover if I get to a VT fast enough to kill the
  process. Also, the OOM killer sometimes triggers and kills the process
  or gnome-shell, but the OOM killer entries in dmesg look like neither
  of the two are using excessive memory compared to available system
  RAM. When I switch to the Ubuntu drm-tip kernel packages from the
  kernel PPA the problem goes away. Debugging shows that the hang occurs
  during the first glXMakeCurrent call made by the application. It did
  not occur using the standard Ubuntu kernel but running the application
  under apitrace. I can provide the trace if that helps.

  Short extract from glxinfo running the 4.20 drm-tip kernel:

  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel Open Source Technology Center (0x8086)
  Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916)
  Version: 18.2.2
  Accelerated: yes
  Video memory: 3072MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperVersion: 1.399
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 26 15:01:53 2018
  DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2245]
  InstallationDate: Installed on 2018-06-12 (166 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HES0E73E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash 
crashkernel=384M-:128M
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2018-10-08 (49 days ago)
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET78W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HES0E73E
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470
  dmi.product.name: 20HES0E73E
  dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470
  dmi.product.version: ThinkPad T470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xs

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

[Łukasz Zemczak]

Hello Cs-gon, or anyone else affected,

Accepted unattended-upgrades into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7 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-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Confirmed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regressio

[Touch-packages] [Bug 1803749] Re: apt.Cache.clear() may set apt.Package.is_auto_removable to False

[Łukasz Zemczak]

Hello Balint, or anyone else affected,

Accepted unattended-upgrades into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.5ubuntu3.18.10.0 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unattended-upgrades (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  apt.Cache.clear() may set apt.Package.is_auto_removable to False

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Originally autoremovable packages can be removed as newly autoremovable 
ones by unattended-upgrades
   * This can surprise users potentially removing packages which are needed for 
the system's operation.

  [Test Case]

   * WIP, see Original Bug Test

  [Regression Potential]

   * Unattended-upgrades may use more CPU-time for operation but I did not 
observe a significant increase. Autopkgtest measures u-u's performance thus if 
this regression occurs, we can observe it easily.
   * Due to the code changes u-u may still remove already autoremovable 
packages or fail to remove newly autoremovable ones in default configuration, 
but since the code became simpler with the change by eliminating an 
optimization this regression is unlikely to take place.

  [Original Bug Text]

  While triaging LP: #1803587 I found that originally autoremovable
  packages were handled as newly autoremovable ones by unattended-
  upgrades due to not finding all of them at the beginning of u-u's run.

  The root cause seems to be cache.clear() resetting
  pkg.is_auto_removable to False under some circumstances I haven't
  fully narrowed down.

  Set up a Bionic (or later) system with autoremovable packages,
  packages upgradable from -security and blacklist at least one
  upgradable package and apply the following patch to u-u:

  root@bb-1803587:~# diff -Naur /usr/bin/unattended-upgrade.orig 
/usr/bin/unattended-upgrade
  --- /usr/bin/unattended-upgrade.orig  2018-11-16 16:17:58.522583254 +
  +++ /usr/bin/unattended-upgrade   2018-11-16 16:36:12.226675870 +
  @@ -948,7 +948,9 @@
   def rewind_cache(cache, pkgs_to_upgrade):
   # type: (apt.Cache, List[apt.Package]) -> None
   """ set the cache back to the state with packages_to_upgrade """
  +print([pkg.name  for pkg in cache if pkg.is_auto_removable])
   cache.clear()
  +print([pkg.name for pkg in cache if pkg.is_auto_removable])
   for pkg2 in pkgs_to_upgrade:
   pkg2.mark_install(from_user=not pkg2.is_auto_installed)
   if cache.broken_count > 0:

  Run u-u to observe cache.clear() resetting the list of autoremovable
  packages:

   ~# /usr/bin/unattended-upgrade --dry-run --verbose --debug
  Initial blacklisted packages: systemd
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  Using 
(^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-modules-.*|^linux-modules-.*|^linux-tools|^linux-cloud-tools)
 regexp to find kernel packages
  Using 
(^linux-image.*4.15.0-38-generic|^linux-headers.*4.15.0-38-generic|^linux-image-extra.*4.15.0-38-generic|^linux-modules.*4.15.0-38-generic|^linux-modules-extra.*4.15.0-38-generic|^linux-signed-image.*4.15.0-38-generic|^kfreebsd-image.*4.15.0-38-gene

[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[Łukasz Zemczak]

Hello Cs-gon, or anyone else affected,

Accepted unattended-upgrades into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.5ubuntu3.18.10.0 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unattended-upgrades (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Confirmed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling i

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

[Łukasz Zemczak]

Hello Balint, or anyone else affected,

Accepted unattended-upgrades into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7 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-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  apt.Cache.clear() may set apt.Package.is_auto_removable to False

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Originally autoremovable packages can be removed as newly autoremovable 
ones by unattended-upgrades
   * This can surprise users potentially removing packages which are needed for 
the system's operation.

  [Test Case]

   * WIP, see Original Bug Test

  [Regression Potential]

   * Unattended-upgrades may use more CPU-time for operation but I did not 
observe a significant increase. Autopkgtest measures u-u's performance thus if 
this regression occurs, we can observe it easily.
   * Due to the code changes u-u may still remove already autoremovable 
packages or fail to remove newly autoremovable ones in default configuration, 
but since the code became simpler with the change by eliminating an 
optimization this regression is unlikely to take place.

  [Original Bug Text]

  While triaging LP: #1803587 I found that originally autoremovable
  packages were handled as newly autoremovable ones by unattended-
  upgrades due to not finding all of them at the beginning of u-u's run.

  The root cause seems to be cache.clear() resetting
  pkg.is_auto_removable to False under some circumstances I haven't
  fully narrowed down.

  Set up a Bionic (or later) system with autoremovable packages,
  packages upgradable from -security and blacklist at least one
  upgradable package and apply the following patch to u-u:

  root@bb-1803587:~# diff -Naur /usr/bin/unattended-upgrade.orig 
/usr/bin/unattended-upgrade
  --- /usr/bin/unattended-upgrade.orig  2018-11-16 16:17:58.522583254 +
  +++ /usr/bin/unattended-upgrade   2018-11-16 16:36:12.226675870 +
  @@ -948,7 +948,9 @@
   def rewind_cache(cache, pkgs_to_upgrade):
   # type: (apt.Cache, List[apt.Package]) -> None
   """ set the cache back to the state with packages_to_upgrade """
  +print([pkg.name  for pkg in cache if pkg.is_auto_removable])
   cache.clear()
  +print([pkg.name for pkg in cache if pkg.is_auto_removable])
   for pkg2 in pkgs_to_upgrade:
   pkg2.mark_install(from_user=not pkg2.is_auto_installed)
   if cache.broken_count > 0:

  Run u-u to observe cache.clear() resetting the list of autoremovable
  packages:

   ~# /usr/bin/unattended-upgrade --dry-run --verbose --debug
  Initial blacklisted packages: systemd
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  Using 
(^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-modules-.*|^linux-modules-.*|^linux-tools|^linux-cloud-tools)
 regexp to find kernel packages
  Using 
(^linux-image.*4.15.0-38-generic|^linux-headers.*4.15.0-38-generic|^linux-image-extra.*4.15.0-38-generic|^linux-modules.*4.15.0-38-generic|^linux-modules-extra.*4.15.0-38-generic|^linux-signed-image.*4.15.0-38-generic|^kfreebsd-image.*4.15.0-38-generic|^kfreebsd-headers.*4.15.0-38-generic|^gnumach-image.*4.15.0-38-generic|4.15.0-38-generic.*-modules|4.15.0-38-generic.*-kernel|^linux-backports-modules-.*.*4.15.0-38-generic|^linux-modules-.*.*4.15.0-38-generic|^linux-tools.*4.15.0-38-generic|^linux-cloud-tools.*4.15.0-38-generi

[Touch-packages] [Bug 1805200] [NEW] Xorg crashes when it tries to resume a scale transformation after that Screen has been closed

[Treviño]

Public bug reported:

Happens in X.Org X Server 2:1.20.3-1ubuntu1, but also previous versions

Very easy to reproduce:
Start a simple (empty) X server instance (say Xorg :2 vt8)
Set a scale transformation
xrandr -d :2 --output eDP-1 --scale 2x2
Call xrandr again so that the server tries to resume the previous 
transformation
xrandr -d :2

I've addressed the issue at
https://gitlab.freedesktop.org/xorg/xserver/issues/14 and proposed
various fixes for that, but so far no feedback.

Marking it as incoming rls bug as this needs to be addressed as per
supporting xrandr scaling support in desktop.

** Affects: xorg (Ubuntu)
 Importance: High
 Assignee: Timo Aaltonen (tjaalton)
 Status: Triaged


** Tags: rls-dd-incoming

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

Title:
  Xorg crashes when it tries to resume a scale transformation after that
  Screen has been closed

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  Happens in X.Org X Server 2:1.20.3-1ubuntu1, but also previous
  versions

  Very easy to reproduce:
  Start a simple (empty) X server instance (say Xorg :2 vt8)
  Set a scale transformation
  xrandr -d :2 --output eDP-1 --scale 2x2
  Call xrandr again so that the server tries to resume the previous 
transformation
  xrandr -d :2

  I've addressed the issue at
  https://gitlab.freedesktop.org/xorg/xserver/issues/14 and proposed
  various fixes for that, but so far no feedback.

  Marking it as incoming rls bug as this needs to be addressed as per
  supporting xrandr scaling support in desktop.

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

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

[Touch-packages] [Bug 1805063] Re: package systemd-sysv 237-3ubuntu10.10 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

[Mike Salvatore]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package systemd-sysv 237-3ubuntu10.10 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Im not sure where the bug may have come from...it came with the new
  update

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.10
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Sat Nov 24 10:50:14 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-04-13 (2052 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.10 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-11-26 (0 days ago)

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

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

[Touch-packages] [Bug 1804894] Re: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned

[Mike Salvatore]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers
  looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  usb drivers needed for china phone

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hicolor-icon-theme 0.17-2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 09:16:38 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-11-23 (0 days ago)
  InstallationMedia: Lubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-11-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1804894/+subscriptions

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

[Touch-packages] [Bug 1804683] Re: there is too many errors in my ubuntu 18.04

[Mike Salvatore]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  there is too many errors in my ubuntu 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I am trying to install nvidia driver 415 there is already 390 but the
  laptop recommends 415 when i insert the code it says that there is a
  held broken packeges please help me

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 18:59:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
   nvidia, 390.77, 4.15.0-39-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:39d1]
 Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39d1]
  InstallationDate: Installed on 2018-11-09 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80WK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=d82157c0-ebe8-41dc-a55d-30ee1b736357 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4KCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y520-15IKBN
  dmi.modalias: 
dmi:bvnLENOVO:bvr4KCN40WW:bd10/17/2017:svnLENOVO:pn80WK:pvrLenovoY520-15IKBN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBN:
  dmi.product.family: Y520-15IKBN
  dmi.product.name: 80WK
  dmi.product.version: Lenovo Y520-15IKBN
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted libdrm into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.95-1~18.04.1 in a few
hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libdrm (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

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

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted libdrm into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.95-1~18.04.1 in a few
hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New

Bug description:
  [Impact]

  [Test case]

  [Regression potential]

  libdrm:

  llvm-7:

  libclc:

  mesa:

  xserver:

  drivers:

  [Other info]

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

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

[Touch-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-7 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-7/1:7-3~ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: llvm-toolchain-7 (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-7 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New

Bug description:
  [Impact]

  [Test case]

  [Regression potential]

  libdrm:

  llvm-7:

  libclc:

  mesa:

  xserver:

  drivers:

  [Other info]

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

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

[Touch-packages] [Bug 1805203] [NEW] libcurl3-gnutls in cosmic breaks git with Azure DevOps

[Mark Inderhees]

Public bug reported:

The version of libcurl3-gnutls in cosmic (7.61.0) causes authentication
failures with Azure DevOps. This causes all git operations with the
server to fail (eg clone, push, pull). For details see this curl bug:
https://github.com/curl/curl/pull/2754

To work around this I downgraded libcurl3-gnutls to the version in
bionic (7.58.0)

>From the curl change list https://curl.haxx.se/changes.html#7_61_1, this
issue should be fixed in package version 7.61.1 or above.

Request: please upgrade package in cosmic for libcurl3-gnutls to 7.61.1
or above

Details:
1 - Ubuntu 18.10
2 - libcurl3-gnutls (7.61.0-1ubuntu2.2 and others)
3 - Be able to git clone from an Azure DevOps repository using a Personal 
Access Token
4 - git operations fail to authenticate

Thank you,
Mark

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


** Tags: upgrade-software-version

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

Title:
  libcurl3-gnutls in cosmic breaks git with Azure DevOps

Status in curl package in Ubuntu:
  New

Bug description:
  The version of libcurl3-gnutls in cosmic (7.61.0) causes
  authentication failures with Azure DevOps. This causes all git
  operations with the server to fail (eg clone, push, pull). For details
  see this curl bug: https://github.com/curl/curl/pull/2754

  To work around this I downgraded libcurl3-gnutls to the version in
  bionic (7.58.0)

  From the curl change list https://curl.haxx.se/changes.html#7_61_1,
  this issue should be fixed in package version 7.61.1 or above.

  Request: please upgrade package in cosmic for libcurl3-gnutls to
  7.61.1 or above

  Details:
  1 - Ubuntu 18.10
  2 - libcurl3-gnutls (7.61.0-1ubuntu2.2 and others)
  3 - Be able to git clone from an Azure DevOps repository using a Personal 
Access Token
  4 - git operations fail to authenticate

  Thank you,
  Mark

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

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

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[David Dombrowsky]

AH HA!

@petr-sedlacek I thought the problem was: the oracle provided version of
virtualbox depends on libcurl3, and the canonical provided version is
5.0 doesn't have 64-bit support (or at least, it doesn't work yet).

Whelll

Turns out I was downloading the wrong version from Oracle.  There is a
"xenial" version of 5.2_5.2.22-126460, and a "bionic" version.  That's
right, two different versions of the same version.  EXCELLENT!  Install
the copy of virtualbox for bionic and all is right with the world.

I apologize for my annoyance :)

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop
  mongodb

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

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

[Adam Conrad]

Hello Daniel, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.3 in a few
hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
    

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Adam Conrad]

Hello Daniel, or anyone else affected,

Accepted netplan.io into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/netplan.io/0.40.2.2
in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

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

[Ryan Harper]

It seems there are some limitations to what systemd will do with
IPv6BytesMTU.

1) if LinkLocalAddressing is not disabled, it will clobber any
IPv6BytesMTU value set.

[Network]
LinkLocalAddressing=ipv6
Address=10.10.10.10/24
IPv6MTUBytes=1470

This results in: /proc/sys/net/ipv6/conf//mtu having a value of
1500

if I disable LinkLocalAddressing like so:

[Network]
LinkLocalAddressing=no
Address=10.10.10.10/24
IPv6MTUBytes=1470

Then I get 1470.

This seems like a bug; do we need an upstream issue to track this?


2) systemd-networkd will not raise the device MTU limit automatically.  The 
default device MTU is 1500.  If you set IPv6BytesMTU to 1520, then 
systemd-networkd emits this message:

Nov 26 19:13:59 rharper-b2 systemd-networkd[593]: eth2: Cannot set IPv6
MTU for interface: Invalid argument

which is the same message you get if you: echo "1520" >
/proc/sys/net/ipv6/conf//mtu:

# echo 1520 > /proc/sys/net/ipv6/conf/eth2/mtu  
bash: echo: write error: Invalid argument


If this is considered "acceptable" behavior for systemd, then it will leave 
netplan with a decision when it is presented with a config which sets an 
ipv6-mtu bytes value that is bigger than the default device value (1500), or 
bigger than an specified device mtu.  Will it report an error with the config?

Should we file an upstream issue to see if networkd is willing to raise
the device limit (or possibly emit a more helpful message to indicate
that networkd cannot set an IPv6 MTU greater than the underlying device
MTU?

-- 
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 cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]
   
   * Original bug report below

  = end of systemd =

  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/cloud-init/+bug/1671951/+subscriptions

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

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Franz Seidl]

I've the problem with my VPS at Strato, they use Virtuozzo.

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  
  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
i->uid_set ? i->uid : UID_INVALID,
i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  
  Any help fixing this problem would be highly appreciated. 
  Many thanks,
  Rafael

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

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

[Touch-packages] [Bug 1805241] [NEW] Problem using secret-tool as root

[pickadi]

Public bug reported:

Ubuntu release: 18.10 x64
Package version: libsecret-tools 0.18.6-3

Command example: sudo secret-tool store --label='password' key value
(similar issues can be obtained with secret-tool lookup / clear /
search)

Expected behavior: the same behavior as a non-privileged user, that is:
no output in stdout nor syslog, secret-tool simply asks for the password
and stores it.

Observed behavior: After a few seconds of waiting, secret-tool crashes
with the following output in stdout:

(secret-tool:3394): GLib-GObject-CRITICAL **: 15:45:12.811: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
secret-tool: Error calling StartServiceByName for org.freedesktop.secrets: 
Timeout was reached

and the following output in /var/log/syslog:

dbus-daemon[4246]: [session uid=0 pid=4244] AppArmor D-Bus mediation is enabled
dbus-daemon[4246]: [session uid=0 pid=4244] Activating service 
name='org.freedesktop.secrets' requested by ':1.0' (uid=0 pid=4240 
comm="secret-tool store --label=password key value " label="unconfined")
gnome-keyring-d[4249]: couldn't create socket directory: 
/home/user/.cache/keyring-XTN8SZ: Permission denied
gnome-keyring-d[4249]: couldn't bind to control socket: 
/home/user/.cache/keyring-XTN8SZ/control: Permission denied

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

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

Title:
  Problem using secret-tool as root

Status in libsecret package in Ubuntu:
  New

Bug description:
  Ubuntu release: 18.10 x64
  Package version: libsecret-tools 0.18.6-3

  Command example: sudo secret-tool store --label='password' key value
  (similar issues can be obtained with secret-tool lookup / clear /
  search)

  Expected behavior: the same behavior as a non-privileged user, that
  is: no output in stdout nor syslog, secret-tool simply asks for the
  password and stores it.

  Observed behavior: After a few seconds of waiting, secret-tool crashes
  with the following output in stdout:

  (secret-tool:3394): GLib-GObject-CRITICAL **: 15:45:12.811: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  secret-tool: Error calling StartServiceByName for org.freedesktop.secrets: 
Timeout was reached

  and the following output in /var/log/syslog:

  dbus-daemon[4246]: [session uid=0 pid=4244] AppArmor D-Bus mediation is 
enabled
  dbus-daemon[4246]: [session uid=0 pid=4244] Activating service 
name='org.freedesktop.secrets' requested by ':1.0' (uid=0 pid=4240 
comm="secret-tool store --label=password key value " label="unconfined")
  gnome-keyring-d[4249]: couldn't create socket directory: 
/home/user/.cache/keyring-XTN8SZ: Permission denied
  gnome-keyring-d[4249]: couldn't bind to control socket: 
/home/user/.cache/keyring-XTN8SZ/control: Permission denied

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

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

[Touch-packages] [Bug 1582470] Re: should put OOPS ID / URL in .uploaded file

[Brian Murray]

** Changed in: whoopsie
   Status: In Progress => Fix Released

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

Title:
  should put OOPS ID / URL in .uploaded file

Status in Whoopsie:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released

Bug description:
  To make it easier to investigate crash dumps, it would be helpful if
  whoopsie could put the OOPS ID and errors.ubuntu.com URL in the
  .uploaded file it creates after upload to indicate successful
  transfer.

  This makes it much easier, for example, for a script to pull
  everything in /var/crash/ and get information relevant for submitting
  a bug report.  At the moment, I instead try to parse the ID out of
  whoopsie.log and generate the URL, but that tends to be a bit brittle.

  This is mostly to help with data collection during automated testing,
  but also to make manual investigations easier.

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

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

[Touch-packages] [Bug 837557] Re: fraudulent DigiNotar certificate issuance

[Olivier Tilloy]

Nora Blob, Ubuntu 17.10 is EOL and not supported any longer. Is the
issue present in a supported release of Ubuntu (14.04, 16.04, 18.04,
18.10) or in the current development version (19.04) ?

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

Title:
  fraudulent DigiNotar certificate issuance

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in nss package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in seamonkey package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Fix Released
Status in xulrunner-1.9.2 package in Ubuntu:
  Invalid
Status in ca-certificates source package in Lucid:
  Fix Released
Status in chromium-browser source package in Lucid:
  Fix Released
Status in firefox source package in Lucid:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in qt4-x11 source package in Lucid:
  Fix Released
Status in seamonkey source package in Lucid:
  Won't Fix
Status in thunderbird source package in Lucid:
  Fix Released
Status in xulrunner-1.9.2 source package in Lucid:
  Fix Released
Status in ca-certificates source package in Maverick:
  Fix Released
Status in chromium-browser source package in Maverick:
  Fix Released
Status in firefox source package in Maverick:
  Fix Released
Status in nss source package in Maverick:
  Fix Released
Status in qt4-x11 source package in Maverick:
  Fix Released
Status in seamonkey source package in Maverick:
  Won't Fix
Status in thunderbird source package in Maverick:
  Fix Released
Status in xulrunner-1.9.2 source package in Maverick:
  Fix Released
Status in ca-certificates source package in Natty:
  Fix Released
Status in chromium-browser source package in Natty:
  Fix Released
Status in firefox source package in Natty:
  Fix Released
Status in nss source package in Natty:
  Fix Released
Status in qt4-x11 source package in Natty:
  Fix Released
Status in seamonkey source package in Natty:
  Won't Fix
Status in thunderbird source package in Natty:
  Fix Released
Status in xulrunner-1.9.2 source package in Natty:
  Fix Released
Status in ca-certificates source package in Oneiric:
  Fix Released
Status in chromium-browser source package in Oneiric:
  Fix Released
Status in firefox source package in Oneiric:
  Fix Released
Status in nss source package in Oneiric:
  Fix Released
Status in qt4-x11 source package in Oneiric:
  Fix Released
Status in seamonkey source package in Oneiric:
  Won't Fix
Status in thunderbird source package in Oneiric:
  Fix Released
Status in xulrunner-1.9.2 source package in Oneiric:
  Invalid
Status in ca-certificates package in Debian:
  Fix Released

Bug description:
  USN Information: This is being tracked in USN-1197-*

  NOTE: The Firefox update causes a regression for certain Dutch sites which is 
being tracked in Bug #838322.
  NOTE #2: The current update for Thunderbird still shows the DigiNotar Root CA 
as trusted in the certificate manager.  This is due to Thunderbird using the 
system version of NSS. In this initial update, Thunderbird will actively 
distrust any certificate signed by the DigiNotar Root CA.  Future updates will 
properly show the root CA as distrusted in the certificate manager.

  WORKAROUND (from blog post):
  http://support.mozilla.com/en-US/kb/deleting-diginotar-ca-cert

  -

  http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-
  certificate/

  Qt 4.7 blog post: http://labs.qt.nokia.com/2011/09/07/what-the-
  diginotar-security-breach-means-for-qt-users-continued/

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

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

[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Brian Murray]

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

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

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

Status in systemd package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  If a cloud server is upgraded from Xenial to Bionic, the dhclient
  system remains in place and any DHCP lease refreshes cause a needless
  restart of the system-resolved daemon

  
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on 
ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal 
in 1466 seconds.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started 
resolvconf-pull-resolved.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.25
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Nov 26 16:17:52 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1805298] [NEW] Unknown Xorg error message

[Warrick]

Public bug reported:

games slow, pc speeds up & pc shuts down

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Nov 27 09:41:27 2018
DistUpgraded: 2018-11-13 13:59:02,460 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: anbox, 1, 4.18.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity [Radeon HD 
7560D] [1462:7800]
InstallationDate: Installed on 2018-11-12 (14 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: MEDION MS-7800
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8d04374c-a31a-4c37-a8bd-0a5c02f26aa7 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to cosmic on 2018-11-13 (13 days ago)
dmi.bios.date: 11/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: M7800W08.209
dmi.board.name: MS-7800
dmi.board.vendor: MEDION
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: MEDION
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM7800W08.209:bd11/02/2012:svnMEDION:pnMS-7800:pvr1.0:rvnMEDION:rnMS-7800:rvr1.0:cvnMEDION:ct3:cvr:
dmi.product.name: MS-7800
dmi.product.version: 1.0
dmi.sys.vendor: MEDION
version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
xserver.bootTime: Tue Nov 27 08:03:13 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.1-3ubuntu2.1
xserver.video_driver: radeon

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


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

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

Title:
  Unknown Xorg error message

Status in xorg package in Ubuntu:
  New

Bug description:
  games slow, pc speeds up & pc shuts down

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 27 09:41:27 2018
  DistUpgraded: 2018-11-13 13:59:02,460 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: anbox, 1, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity [Radeon HD 
7560D] [1462:7800]
  InstallationDate: Installed on 2018-11-12 (14 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDION MS-7800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8d04374c-a31a-4c37-a8bd-0a5c02f26aa7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-13 (13 days ago)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.b

[Touch-packages] [Bug 735297] Re: Can not print on an SMB shared printer after password change

[teramind]

@ronan Where can I find this printer configuration?

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

Title:
  Can not print on an SMB shared printer after password change

Status in cups package in Ubuntu:
  Expired
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  I print to a number of SMB shared printers in a 2003 Active Directory
  domain. My password is changed from time to time as a policy in our
  organisation. When this happens I get prompted to enter the new
  password  but I can no longer connect to the using the new password.
  The previous password was saved using the  "Saved forever" option

  The only workaround I found is to delete the printer and recreate it.
  I had this problem several times in the past and so are the rest of my
  ubuntu users. Is there a workaround for that. Can someone confirm this
  bug?

  I tried to sniff the packets from my PC to the Print Server but
  wireshark showed nothing! This means that the problem is actually on
  my side. I can connect to other domain services like file shares using
  the same credentials. I am using the DOMAIN\username format to
  connect.

  The relevant cups error logs are here in case you want to have a look:
  http://paste.ubuntu.com/580463/

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: cups 1.4.4-6ubuntu2.3
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic-pae 2.6.35.11
  Uname: Linux 2.6.35-27-generic-pae i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Tue Mar 15 08:25:04 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  Lpstat:
   device for Deskjet-F4200-series: 
hp:/usb/Deskjet_F4200_series?serial=CN84A3D1SN052D
   device for FOLLOWME: smb://prs03ist00.lim.tepak.int/FollowMe
   device for hp-LaserJet-2300-series: 
dnssd://hp%20LaserJet%202300%20series%20(0001E6A8204B)._printer._tcp.local/
   device for PDF: cups-pdf:/
   device for SRB02MF001: smb://prs03ist00.lim.tepak.int/srb02mf001
  MachineType: LENOVO 2767WB7
  Papersize: letter
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  PpdFiles:
   SRB02MF001: NRG MP C2500 PXL
   Deskjet-F4200-series: HP Deskjet f4200 Series hpijs, 3.10.6
   PDF: Generic CUPS-PDF Printer
   hp-LaserJet-2300-series: HP LaserJet 2300 Postscript (recommended)
   FOLLOWME: KONICA MINOLTA C252 PS(P)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-27-generic-pae 
root=UUID=5440d147-6520-49af-a1fd-76b8ec027c80 ro splash quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=el_GR.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 10/17/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET49WW (1.19 )
  dmi.board.name: 2767WB7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET49WW(1.19):bd10/17/2008:svnLENOVO:pn2767WB7:pvrThinkPadT400:rvnLENOVO:rn2767WB7:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2767WB7
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 837557] Re: fraudulent DigiNotar certificate issuance

[Nora Blob]

Hello Oliver Tilloy,
I can reproduce this issue in

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

I created a new profile with firefox -p --new-instance, and get the
certificates in the new profile with the new instance. If I delete the
certificates they will be in the certificate manager with every new
profile.

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

Title:
  fraudulent DigiNotar certificate issuance

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in nss package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in seamonkey package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Fix Released
Status in xulrunner-1.9.2 package in Ubuntu:
  Invalid
Status in ca-certificates source package in Lucid:
  Fix Released
Status in chromium-browser source package in Lucid:
  Fix Released
Status in firefox source package in Lucid:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in qt4-x11 source package in Lucid:
  Fix Released
Status in seamonkey source package in Lucid:
  Won't Fix
Status in thunderbird source package in Lucid:
  Fix Released
Status in xulrunner-1.9.2 source package in Lucid:
  Fix Released
Status in ca-certificates source package in Maverick:
  Fix Released
Status in chromium-browser source package in Maverick:
  Fix Released
Status in firefox source package in Maverick:
  Fix Released
Status in nss source package in Maverick:
  Fix Released
Status in qt4-x11 source package in Maverick:
  Fix Released
Status in seamonkey source package in Maverick:
  Won't Fix
Status in thunderbird source package in Maverick:
  Fix Released
Status in xulrunner-1.9.2 source package in Maverick:
  Fix Released
Status in ca-certificates source package in Natty:
  Fix Released
Status in chromium-browser source package in Natty:
  Fix Released
Status in firefox source package in Natty:
  Fix Released
Status in nss source package in Natty:
  Fix Released
Status in qt4-x11 source package in Natty:
  Fix Released
Status in seamonkey source package in Natty:
  Won't Fix
Status in thunderbird source package in Natty:
  Fix Released
Status in xulrunner-1.9.2 source package in Natty:
  Fix Released
Status in ca-certificates source package in Oneiric:
  Fix Released
Status in chromium-browser source package in Oneiric:
  Fix Released
Status in firefox source package in Oneiric:
  Fix Released
Status in nss source package in Oneiric:
  Fix Released
Status in qt4-x11 source package in Oneiric:
  Fix Released
Status in seamonkey source package in Oneiric:
  Won't Fix
Status in thunderbird source package in Oneiric:
  Fix Released
Status in xulrunner-1.9.2 source package in Oneiric:
  Invalid
Status in ca-certificates package in Debian:
  Fix Released

Bug description:
  USN Information: This is being tracked in USN-1197-*

  NOTE: The Firefox update causes a regression for certain Dutch sites which is 
being tracked in Bug #838322.
  NOTE #2: The current update for Thunderbird still shows the DigiNotar Root CA 
as trusted in the certificate manager.  This is due to Thunderbird using the 
system version of NSS. In this initial update, Thunderbird will actively 
distrust any certificate signed by the DigiNotar Root CA.  Future updates will 
properly show the root CA as distrusted in the certificate manager.

  WORKAROUND (from blog post):
  http://support.mozilla.com/en-US/kb/deleting-diginotar-ca-cert

  -

  http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-
  certificate/

  Qt 4.7 blog post: http://labs.qt.nokia.com/2011/09/07/what-the-
  diginotar-security-breach-means-for-qt-users-continued/

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

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

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Dimitri John Ledkov]

Could you please post output of:

   uname -a

** Information type changed from Public to Public Security

** Tags added: regression-update

** Description changed:

  The following description is taken from:
  
  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237
- 
  
  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:
  
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument
  
  To verify I tried this:
  
  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument
  
  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade of
  systemd to 229-4ubuntu21.8.
  
  At this point I don't know what to do.
  
  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
- if (chown(fn,
-   i->uid_set ? i->uid : UID_INVALID,
-   i->gid_set ? i->gid : GID_INVALID) < 0)
- return log_error_errno(errno, "chown(%s) 
failed: %m", path);
+ if (chown(fn,
+   i->uid_set ? i->uid : UID_INVALID,
+   i->gid_set ? i->gid : GID_INVALID) < 0)
+ return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../
  
  Tag v238
  
  /.../
- if (fchownat(fd,
-  "",
-  i->uid_set ? i->uid : UID_INVALID,
-  i->gid_set ? i->gid : GID_INVALID,
-  AT_EMPTY_PATH) < 0)
+ if (fchownat(fd,
+  "",
+  i->uid_set ? i->uid : UID_INVALID,
+  i->gid_set ? i->gid : GID_INVALID,
+  AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../
  
- 
- Any help fixing this problem would be highly appreciated. 
+ Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael
+ 
+ 
+ === Notes ===
+ fchownat() was added to Linux in kernel 2.6.16;
+ library support was added to glibc in version 2.4.
+ checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+sou

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Dimitri John Ledkov]

** Description changed:

  The following description is taken from:
  
  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237
  
  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:
  
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument
  
  To verify I tried this:
  
  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument
  
  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade of
  systemd to 229-4ubuntu21.8.
  
  At this point I don't know what to do.
  
  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../
  
  Tag v238
  
  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../
  
  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael
  
- 
  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
+ glibc in bionic requires minimum linux 3.2.

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h211

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Seth Arnold]

I'm also curious what filesystems are showing this issue. If you're
affected can you please run this command and include the results here?

mount | grep run

Thanks

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael

  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
  glibc in bionic requires minimum linux 3.2.

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

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

[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Seth Arnold]

Andrew, you could try adding:

flags=(attach_disconnected)

to the profile attachment line:

/usr/sbin/ntpd flags=(attach_disconnected) {

And add:

/run/systemd/journal/dev-log w,

to the profile, then run:

apparmor_parser --replace /etc/apparmor.d/usr.sbin.ntpd  # or whatever
the filename is

See if that lets you get useful logs, any new messages in dmesg or
auditd logs, etc.

Thanks

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

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in openntpd package in Ubuntu:
  New
Status in ntp source package in Xenial:
  Invalid
Status in openntpd source package in Xenial:
  New
Status in ntp source package in Zesty:
  Invalid
Status in openntpd source package in Zesty:
  New
Status in ntp source package in Artful:
  Fix Released
Status in openntpd source package in Artful:
  New
Status in ntp source package in Bionic:
  Fix Released
Status in openntpd source package in Bionic:
  New

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1805316] [NEW] systemd 229-4ubuntu21.9 faulty - breaks the system!

[Tom-Oliver Heidel]

Public bug reported:

Ubuntu 16.04.5 LTS

systemd 229-4ubuntu21.9

syslog file http://locoserver.net:8080/inline/14ItB1/syslog

I had to restart one of my server. This one is ovz and the only ubuntu
16 left. All my other servers are ubuntu 18 already.

So what happened?
I restarted my server and I could ping it fine. However when I tried to connect 
with ssh it immediately refused my connection. So I run nmap and indeed all 
other services were running BUT ssh.

I could connect over a service console provided by the hoster. I could
not user 'service ssh rstart' because it would fail since this
'/var/run/sshd' was missing although I checked every script. The scripts
were fine. So I looked through the syslog and found something
interesting on google. There are a lot of people actually having the
same problem at least when using ovz and ubuntu 16.

Right now I try to downgrade my systemd to a previous version until a
fix will be published.

I cannot always log in over the service console and create the file
'/var/run/sshd' by hand to manually start ssh.

There is a thread in the german ubuntu forum
https://forum.ubuntuusers.de/topic/systemd-tmpfiles-fchownat-of-run-failed-invali/

I used this to downgrade
curl -LO 
'http://launchpadlibrarian.net/395488411/systemd_229-4ubuntu21.6_amd64.deb'
curl -LO 
'http://launchpadlibrarian.net/395488403/libsystemd0_229-4ubuntu21.6_amd64.deb'
apt install ./systemd_229-4ubuntu21.6_amd64.deb 
./libsystemd0_229-4ubuntu21.6_amd64.deb

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


** Tags: ssh

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1805316/+attachment/5216643/+files/syslog

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

Title:
  systemd 229-4ubuntu21.9 faulty - breaks the system!

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.5 LTS

  systemd 229-4ubuntu21.9

  syslog file http://locoserver.net:8080/inline/14ItB1/syslog

  I had to restart one of my server. This one is ovz and the only ubuntu
  16 left. All my other servers are ubuntu 18 already.

  So what happened?
  I restarted my server and I could ping it fine. However when I tried to 
connect with ssh it immediately refused my connection. So I run nmap and indeed 
all other services were running BUT ssh.

  I could connect over a service console provided by the hoster. I could
  not user 'service ssh rstart' because it would fail since this
  '/var/run/sshd' was missing although I checked every script. The
  scripts were fine. So I looked through the syslog and found something
  interesting on google. There are a lot of people actually having the
  same problem at least when using ovz and ubuntu 16.

  Right now I try to downgrade my systemd to a previous version until a
  fix will be published.

  I cannot always log in over the service console and create the file
  '/var/run/sshd' by hand to manually start ssh.

  There is a thread in the german ubuntu forum
  
https://forum.ubuntuusers.de/topic/systemd-tmpfiles-fchownat-of-run-failed-invali/

  I used this to downgrade
  curl -LO 
'http://launchpadlibrarian.net/395488411/systemd_229-4ubuntu21.6_amd64.deb'
  curl -LO 
'http://launchpadlibrarian.net/395488403/libsystemd0_229-4ubuntu21.6_amd64.deb'
  apt install ./systemd_229-4ubuntu21.6_amd64.deb 
./libsystemd0_229-4ubuntu21.6_amd64.deb

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

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

[Touch-packages] [Bug 1805316] Re: systemd 229-4ubuntu21.9 faulty - breaks the system!

[Tom-Oliver Heidel]

** Description changed:

  Ubuntu 16.04.5 LTS
  
  systemd 229-4ubuntu21.9
  
  syslog file http://locoserver.net:8080/inline/14ItB1/syslog
  
  I had to restart one of my server. This one is ovz and the only ubuntu
  16 left. All my other servers are ubuntu 18 already.
  
  So what happened?
  I restarted my server and I could ping it fine. However when I tried to 
connect with ssh it immediately refused my connection. So I run nmap and indeed 
all other services were running BUT ssh.
  
  I could connect over a service console provided by the hoster. I could
  not user 'service ssh rstart' because it would fail since this
  '/var/run/sshd' was missing although I checked every script. The scripts
  were fine. So I looked through the syslog and found something
  interesting on google. There are a lot of people actually having the
  same problem at least when using ovz and ubuntu 16.
  
  Right now I try to downgrade my systemd to a previous version until a
  fix will be published.
  
  I cannot always log in over the service console and create the file
  '/var/run/sshd' by hand to manually start ssh.
+ 
+ There is a thread in the german ubuntu forum
+ 
https://forum.ubuntuusers.de/topic/systemd-tmpfiles-fchownat-of-run-failed-invali/
+ 
+ I used this to downgrade
+ curl -LO 
'http://launchpadlibrarian.net/395488411/systemd_229-4ubuntu21.6_amd64.deb'
+ curl -LO 
'http://launchpadlibrarian.net/395488403/libsystemd0_229-4ubuntu21.6_amd64.deb'
+ apt install ./systemd_229-4ubuntu21.6_amd64.deb 
./libsystemd0_229-4ubuntu21.6_amd64.deb

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

Title:
  systemd 229-4ubuntu21.9 faulty - breaks the system!

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.5 LTS

  systemd 229-4ubuntu21.9

  syslog file http://locoserver.net:8080/inline/14ItB1/syslog

  I had to restart one of my server. This one is ovz and the only ubuntu
  16 left. All my other servers are ubuntu 18 already.

  So what happened?
  I restarted my server and I could ping it fine. However when I tried to 
connect with ssh it immediately refused my connection. So I run nmap and indeed 
all other services were running BUT ssh.

  I could connect over a service console provided by the hoster. I could
  not user 'service ssh rstart' because it would fail since this
  '/var/run/sshd' was missing although I checked every script. The
  scripts were fine. So I looked through the syslog and found something
  interesting on google. There are a lot of people actually having the
  same problem at least when using ovz and ubuntu 16.

  Right now I try to downgrade my systemd to a previous version until a
  fix will be published.

  I cannot always log in over the service console and create the file
  '/var/run/sshd' by hand to manually start ssh.

  There is a thread in the german ubuntu forum
  
https://forum.ubuntuusers.de/topic/systemd-tmpfiles-fchownat-of-run-failed-invali/

  I used this to downgrade
  curl -LO 
'http://launchpadlibrarian.net/395488411/systemd_229-4ubuntu21.6_amd64.deb'
  curl -LO 
'http://launchpadlibrarian.net/395488403/libsystemd0_229-4ubuntu21.6_amd64.deb'
  apt install ./systemd_229-4ubuntu21.6_amd64.deb 
./libsystemd0_229-4ubuntu21.6_amd64.deb

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

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

Re: [Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Robert Dinse]

I have since upgraded to 18.10 and I don't even see an apparmor profile 
for ntp anymore.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 27 Nov 2018, Seth Arnold wrote:

> Date: Tue, 27 Nov 2018 01:07:37 -
> From: Seth Arnold <1727...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name
>  lookup - disconnected path
> 
> Andrew, you could try adding:
>
> flags=(attach_disconnected)
>
> to the profile attachment line:
>
> /usr/sbin/ntpd flags=(attach_disconnected) {
>
> And add:
>
> /run/systemd/journal/dev-log w,
>
> to the profile, then run:
>
> apparmor_parser --replace /etc/apparmor.d/usr.sbin.ntpd  # or whatever
> the filename is
>
> See if that lets you get useful logs, any new messages in dmesg or
> auditd logs, etc.
>
> Thanks
>
> ** Also affects: openntpd (Ubuntu)
>   Importance: Undecided
>   Status: New
>
> -- 
> You received this bug notification because you are subscribed to a
> duplicate bug report (1739943).
> https://bugs.launchpad.net/bugs/1727202
>
> Title:
>  [17.10 regression] AppArmor ntp denial: Failed name lookup -
>  disconnected path
>
> Status in ntp package in Ubuntu:
>  Fix Released
> Status in openntpd package in Ubuntu:
>  New
> Status in ntp source package in Xenial:
>  Invalid
> Status in openntpd source package in Xenial:
>  New
> Status in ntp source package in Zesty:
>  Invalid
> Status in openntpd source package in Zesty:
>  New
> Status in ntp source package in Artful:
>  Fix Released
> Status in openntpd source package in Artful:
>  New
> Status in ntp source package in Bionic:
>  Fix Released
> Status in openntpd source package in Bionic:
>  New
>
> Bug description:
>  [Impact]
>
>   * NTP has new isolation features which makes it trigger apparmor issues.
>   * Those apparmor issues not only clutter the log and make other things
>     less readable, they also prevent ntp from reporting its actual
>     messages.
>   * Fix is opening the apparmor profile to follow ntp through the
>     disconnect by the isolation feature.
>
>  [Test Case]
>
>   * This is hard to trigger, but then also not. Which means it is not
>     entirely sorted out when it triggers and when not, but the following
>     does trigger it in tests of Pitti and also mine (while at the same time
>     sometimes it does not - mabye I had other guests or kvm instead of lxd)
>
>   * First install ntp in Artful (or above unless fixed)
>     * Install ntp and check demsg for denies
>     * Once an issue triggers instead of the error in syslog you'll see the
>   apparmor Deny like:
>     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
>     disconnected path" error=-13 profile="/usr/sbin/ntpd"
>     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
>     requested_mask="w" denied_mask="w" fsuid=0 ouid=0
>
>  [Regression Potential]
>
>   * We are slightly opening up the apparmor profile which is far lower risk
>     than adding more constraints. So safe from that POV.
>
>   * OTOH one could think this might be a security issue, but in fact this
>     isn't a new suggestion if you take a look at [1] with an ack by Seth of
>     the Security Team.
>
>  [Other Info]
>
>   * n/a
>
>  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html
>
>  
>
>  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
>  this AppArmor violation:
>
>  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
>  operation="sendmsg" info="Failed name lookup - disconnected path"
>  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
>  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
>
>  (many times). This hasn't happened in earlier Ubuntu releases yet.
>
>  This was spotted by Cockpit's integration tests, as our "ubuntu-
>  stable" image now moved to 17.10 after its release.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
>  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>  Uname: Linux 4.13.0-16-generic x86_64
>  ApportVersion: 2.20.7-0ubuntu3
>  Architecture: amd64
>  Date: Wed Oct 25 03:19:34 2017
>  SourcePackage: ntp
>  UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions
>

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix

[Touch-packages] [Bug 1805151] Re: Desktop freeze running VirtualBox, Intel graphics

[Daniel van Vugt]

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

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

Title:
   Desktop freeze running VirtualBox, Intel graphics

Status in linux package in Ubuntu:
  New

Bug description:
  This is identical to bug 1804885, but as requested I am filing this while 
running the standard Ubuntu kernel.  I will copy and paste my summary below.  
Updates since I created that bug:
   * This occurs with the mainline PPA 4.18.12-041812-generic kernel.
   * The glxinfo section I include below is identical with 4.18.0-11-generic 
(presumably no surprise).
   * I would appreciate a bit of hand-holding for bisecting this.  Does the 
kernel team have ready-built kernel packages for bisecting?  Or guidance about 
the fastest way of doing it (i.e. not rebuilding things which do not need to be 
rebuilt for successive rounds)?

  === Original report follows ===

  When I start a VirtualBox virtual machine (reproducible with the
  Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with
  VMSVGA emulation and 3D pass-through enabled, my system hangs.
  Sometimes I can recover if I get to a VT fast enough to kill the
  process. Also, the OOM killer sometimes triggers and kills the process
  or gnome-shell, but the OOM killer entries in dmesg look like neither
  of the two are using excessive memory compared to available system
  RAM. When I switch to the Ubuntu drm-tip kernel packages from the
  kernel PPA the problem goes away. Debugging shows that the hang occurs
  during the first glXMakeCurrent call made by the application. It did
  not occur using the standard Ubuntu kernel but running the application
  under apitrace. I can provide the trace if that helps.

  Short extract from glxinfo running the 4.20 drm-tip kernel:

  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel Open Source Technology Center (0x8086)
  Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916)
  Version: 18.2.2
  Accelerated: yes
  Video memory: 3072MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperVersion: 1.399
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 26 15:01:53 2018
  DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2245]
  InstallationDate: Installed on 2018-06-12 (166 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HES0E73E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash 
crashkernel=384M-:128M
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2018-10-08 (49 days ago)
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET78W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HES0E73E
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470
  dmi.product.name: 20HES0E73E
  dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470
  dmi.product.version: ThinkPad T470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel:

[Touch-packages] [Bug 1805048] Re: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or crackling sound. It's not my microphone, it's every audio input... Audio output is fine

[Daniel van Vugt]

Thanks.

Your kernel log shows a lot of messages from Discord. I wonder is that
app affected, and can you please try a few other voice apps too?

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

Title:
  [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or
  crackling sound. It's not my microphone, it's every audio input...
  Audio output is fine

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Motherboard : MSI B350M BAZOOKA

  It happens all the time, and with every audio input...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  p4ul1  1433 F pulseaudio
   /dev/snd/pcmC1D0c:   p4ul1  1433 F...m pulseaudio
   /dev/snd/pcmC1D0p:   p4ul1  1433 F...m pulseaudio
   /dev/snd/controlC1:  p4ul1  1433 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Nov 25 21:40:48 2018
  InstallationDate: Installed on 2018-11-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Pink Mic, Front
  Symptom_PulseAudioLog:
   Nov 25 21:02:45 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.32' (uid=121 pid=1123 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Nov 25 21:02:46 p4ul1-MS-7A38 dbus-daemon[806]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.59' (uid=121 pid=1123 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MS-7A38, Realtek ALC892, Pink Mic, Front] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M BAZOOKA (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.70:bd09/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350MBAZOOKA(MS-7A38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1805200] Re: Xorg crashes when it tries to resume a scale transformation after that Screen has been closed

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Xorg crashes when it tries to resume a scale transformation after that Screen 
has been closed
+ Xorg crashes when it tries to resume a scale transformation after that Screen 
has been closed. Crashed in __strlen_avx2() from transform_filter_length() from 
ProcRRGetCrtcTransform()

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

Title:
  Xorg crashes when it tries to resume a scale transformation after that
  Screen has been closed. Crashed in __strlen_avx2() from
  transform_filter_length() from ProcRRGetCrtcTransform()

Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Happens in X.Org X Server 2:1.20.3-1ubuntu1, but also previous
  versions

  Very easy to reproduce:
  Start a simple (empty) X server instance (say Xorg :2 vt8)
  Set a scale transformation
  xrandr -d :2 --output eDP-1 --scale 2x2
  Call xrandr again so that the server tries to resume the previous 
transformation
  xrandr -d :2

  I've addressed the issue at
  https://gitlab.freedesktop.org/xorg/xserver/issues/14 and proposed
  various fixes for that, but so far no feedback.

  Marking it as incoming rls bug as this needs to be addressed as per
  supporting xrandr scaling support in desktop.

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

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

[Touch-packages] [Bug 1805298] Re: Unknown Xorg error message

[Daniel van Vugt]

Can you please clarify in more detail what problem you would like this
bug to be about?

** Tags added: radeon

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Unknown Xorg error message

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  games slow, pc speeds up & pc shuts down

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 27 09:41:27 2018
  DistUpgraded: 2018-11-13 13:59:02,460 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: anbox, 1, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity [Radeon HD 
7560D] [1462:7800]
  InstallationDate: Installed on 2018-11-12 (14 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDION MS-7800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8d04374c-a31a-4c37-a8bd-0a5c02f26aa7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-13 (13 days ago)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M7800W08.209
  dmi.board.name: MS-7800
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM7800W08.209:bd11/02/2012:svnMEDION:pnMS-7800:pvr1.0:rvnMEDION:rnMS-7800:rvr1.0:cvnMEDION:ct3:cvr:
  dmi.product.name: MS-7800
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Tue Nov 27 08:03:13 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2.1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1804683] Re: there is too many errors in my ubuntu 18.04

[Daniel van Vugt]

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

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

Title:
  there is too many errors in my ubuntu 18.04

Status in Ubuntu:
  New

Bug description:
  I am trying to install nvidia driver 415 there is already 390 but the
  laptop recommends 415 when i insert the code it says that there is a
  held broken packeges please help me

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 18:59:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
   nvidia, 390.77, 4.15.0-39-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:39d1]
 Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39d1]
  InstallationDate: Installed on 2018-11-09 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80WK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=d82157c0-ebe8-41dc-a55d-30ee1b736357 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4KCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y520-15IKBN
  dmi.modalias: 
dmi:bvnLENOVO:bvr4KCN40WW:bd10/17/2017:svnLENOVO:pn80WK:pvrLenovoY520-15IKBN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBN:
  dmi.product.family: Y520-15IKBN
  dmi.product.name: 80WK
  dmi.product.version: Lenovo Y520-15IKBN
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

Re: [Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Seth Arnold]

On Tue, Nov 27, 2018 at 01:22:10AM -, Robert Dinse wrote:
> I have since upgraded to 18.10 and I don't even see an apparmor profile 
> for ntp anymore.

That's curious. This is in the source package:

# vim:syntax=apparmor
#include 

/usr/sbin/ntpd flags=(attach_disconnected) {
  #include 
  #include 

  # conf
  /etc/openntpd/ntpd.conf r,

  # capabilities
  capability kill,
  capability sys_chroot,
  capability setgid,
  capability setuid,
  capability sys_time,
  capability sys_nice,

  /usr/sbin/ntpd mrix,
  /var/lib/openntpd/db/ntpd.drift rw,
  /var/lib/openntpd/run/ntpd.sock rw,

}

It looks like half the change has already been integrated, but not the
systemd-journald socket.

> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
>   Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
> Knowledgeable human assistance, not telephone trees or script readers.
>   See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

Ah this takes me back. :) I learned a huge amount on irc.eskimo.com back
in the day. Belated by two decades, thanks!

Thanks

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in openntpd package in Ubuntu:
  New
Status in ntp source package in Xenial:
  Invalid
Status in openntpd source package in Xenial:
  New
Status in ntp source package in Zesty:
  Invalid
Status in openntpd source package in Zesty:
  New
Status in ntp source package in Artful:
  Fix Released
Status in openntpd source package in Artful:
  New
Status in ntp source package in Bionic:
  Fix Released
Status in openntpd source package in Bionic:
  New

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Peter Enns]

Output of uname -a:

Linux newpnc 2.6.32-042stab132.1 #1 SMP Wed Jul 11 13:51:30 MSK 2018
x86_64 x86_64 x86_64 GNU/Linux

Output of mount | grep run:

tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
none on /run/shm type tmpfs (rw,relatime)

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael

  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
  glibc in bionic requires minimum linux 3.2.

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

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

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Mathew Hodson]

** Changed in: apparmor/2.11
   Status: Fix Committed => Fix Released

** Tags removed: sts-sru-needed verification-needed

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Released
Status in AppArmor 2.11 series:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in apparmor source package in Artful:
  Fix Released
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

  This fix is committed, but not released. so all supporting version are
  affected.

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [Test Case]

  1. making pid over 6 digits
  #!/bin/bash

  for i in {1..100}
  do
    touch t
  done

  2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
  16-2.30 avoids using /proc/PID/cmdline, so need to use older version

  3. you can see DENIED msgs in syslog

  4. change /etc/apparmor.d/tunables/kernelvars
  5. service apparmor restart
  6. service snapd restart
  7. DENIED is gone

  This is one way, can't reproduce this issue again even if you change
  back to original kernelvars, and restart snapd

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2

  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic

  $ rmadison -u debian apparmor
   apparmor | 2.11.1-4   | unstable
  --

  [Original Description]

  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is defined in /etc/apparmor.d/tunables:
  
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}

  It only covers up to 6 digits.

  This Ubuntu 17.04 system has:
  kernel.pid_max = 4194303

  And is showing
  type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Steve Langasek]

glibc in Ubuntu 16.04 does have MIN_KERNEL_SUPPORTED := 2.6.32 in
debian/sysdeps/amd64.mk precisely to support running Ubuntu userspace on
RHEL6 kernels.  This is not a supported configuration for a full booted
Ubuntu 16.04 install, because the minimum kernel version for udev itself
is higher than this (iirc, Linux 3.2) - but since this is running as a
container, udev isn't a concern.

So it seems reasonablbe to expect this not to regress as part of a
security update of systemd on Ubuntu 16.04.

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael

  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
  glibc in bionic requires minimum linux 3.2.

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

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

[Touch-packages] [Bug 1805148] Re: Lock screen corrupt since upgrade to 18.04.01

[Daniel van Vugt]

Thanks. Unfortunately that didn't attach everything I was thinking of.
Can you please also:

1. Run 'lspci -k' and attach the output.

2. Run 'dpkg -l > allpackages.txt' and attach the file
'allpackages.txt'.


** Summary changed:

- Lock screen corrupt since upgrade to 18.04.01
+ [i945] Lock screen corrupt since upgrade to 18.04.01

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

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

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

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

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

Title:
  [i945] Lock screen corrupt since upgrade to 18.04.01

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-01-23 (1038 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1787824] Re: "rfkill: input handler disabled" boot time 11 seconds.

[Charles Wright]

I was watching a video over the network from my x1 system when it went
offline.

My system had been up over a day at the time,

Later it came back online and I found this pattern in the logs.

Nov 24 22:08:38 x1 kernel: [ 4491.984774] rfkill: input handler enabled
Nov 24 22:45:15 x1 kernel: [ 6689.350749] r8169 :04:00.0 eth0: link down
Nov 24 22:45:18 x1 kernel: [ 6692.350653] r8169 :04:00.0 eth0: link up
...
Nov 24 23:28:51 x1 kernel: [ 9305.191129] perf: interrupt took too long (2514 > 
2500), lowering kernel.perf_event_max_sample_rate to 79500
Nov 24 23:44:36 x1 kernel: [10250.105921] r8169 :04:00.0 eth0: link down
Nov 24 23:44:39 x1 kernel: [10253.137255] r8169 :04:00.0 eth0: link up
Nov 24 23:44:41 x1 kernel: [10254.820174] r8169 :04:00.0 eth0: link down
Nov 24 23:44:53 x1 kernel: [10267.308766] r8169 :04:00.0 eth0: link down
Nov 24 23:44:57 x1 kernel: [10270.416767] r8169 :04:00.0 eth0: link up
Nov 24 23:45:05 x1 kernel: [10278.366294] r8169 :04:00.0 eth0: link down
Nov 24 23:45:08 x1 kernel: [10281.415489] r8169 :04:00.0 eth0: link up
Nov 24 23:45:56 x1 kernel: [10329.333933] r8169 :04:00.0 eth0: link down
Nov 24 23:46:04 x1 kernel: [10337.815700] r8169 :04:00.0 eth0: link down
Nov 24 23:46:11 x1 kernel: [10344.998667] r8169 :04:00.0 eth0: link up
Nov 24 23:46:13 x1 kernel: [10346.873959] r8169 :04:00.0 eth0: link down
Nov 24 23:46:16 x1 kernel: [10350.226690] r8169 :04:00.0 eth0: link up
Nov 24 23:46:18 x1 kernel: [10352.318011] r8169 :04:00.0 eth0: link down
Nov 24 23:46:21 x1 kernel: [10355.245040] r8169 :04:00.0 eth0: link up

Nov 26 21:14:23 x1 kernel: [129787.573891] rfkill: input handler enabled
Nov 26 21:23:30 x1 kernel: [130334.427437] r8169 :03:00.0 eth0: link down
Nov 26 21:23:33 x1 kernel: [130337.443076] r8169 :03:00.0 eth0: link up
Nov 26 21:23:57 x1 kernel: [130361.790251] r8169 :03:00.0 eth0: link down
Nov 26 21:24:00 x1 kernel: [130364.790674] r8169 :03:00.0 eth0: link up
Nov 26 21:41:58 x1 kernel: [131442.193462] r8169 :03:00.0 eth0: link down
Nov 26 21:42:01 x1 kernel: [131445.332817] r8169 :03:00.0 eth0: link up
Nov 26 21:42:14 x1 kernel: [131458.567170] rfkill: input handler disabled
Nov 26 21:42:16 x1 kernel: [131460.513607] r8169 :03:00.0 eth0: link down
Nov 26 21:42:19 x1 kernel: [131464.056605] r8169 :03:00.0 eth0: link up
Nov 26 21:42:23 x1 kernel: [131467.593377] r8169 :03:00.0 eth0: link down
Nov 26 21:42:30 x1 kernel: [131474.613404] r8169 :03:00.0 eth0: link up
Nov 26 21:42:41 x1 kernel: [131485.133432] r8169 :03:00.0 eth0: link down
Nov 26 21:42:49 x1 kernel: [131493.199224] rfkill: input handler enabled
Nov 26 21:42:52 x1 kernel: [131496.274226] r8169 :03:00.0 eth0: link up
Nov 26 21:42:53 x1 kernel: [131497.548189] r8169 :03:00.0 eth0: link down
Nov 26 21:42:56 x1 kernel: [131500.994252] r8169 :03:00.0 eth0: link up
Nov 26 21:42:57 x1 kernel: [131501.750754] r8169 :03:00.0 eth0: link down
Nov 26 21:43:04 x1 kernel: [131508.486113] r8169 :03:00.0 eth0: link up


root@x1:/var/log# uname -a
Linux x1 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

root@x1:/var/log# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

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

Title:
  "rfkill: input handler disabled" boot time 11 seconds.

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  My computer is slowly opening, I looked at the output of dmesg and at 11th I 
get this post.
  What i need to do? thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rfkill 2.31.1-0.4ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 19:44:21 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libsmartcols1 2.31.1-0.4ubuntu3.1
  InstallationDate: Installed on 2018-08-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1779265] Re: package gcc-4.9-base 4.9.3-0ubuntu4 failed to install/upgrade: package architecture (armhf) does not match system (amd64)

[Launchpad Bug Tracker]

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

** Changed in: gccgo-4.9 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package gcc-4.9-base 4.9.3-0ubuntu4 failed to install/upgrade: package
  architecture (armhf) does not match system (amd64)

Status in gccgo-4.9 package in Ubuntu:
  Expired

Bug description:
  I want that package

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gcc-4.9-base 4.9.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Fri Jun 29 12:09:21 2018
  Dependencies:
   
  ErrorMessage: package architecture (armhf) does not match system (amd64)
  InstallationDate: Installed on 2017-08-22 (310 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gccgo-4.9
  Title: package gcc-4.9-base 4.9.3-0ubuntu4 failed to install/upgrade: package 
architecture (armhf) does not match system (amd64)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

[Peter Enns]

Ah ok, thank you for the information.

Since it is an OpenVZ container, I assume my only option is to apply the
temporary solution above, then start to look for a VPS provider that
supports a more current kernel version (or one that would let me upgrade
the kernel).

Thanks again.

Peter

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael

  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
  glibc in bionic requires minimum linux 3.2.

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

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

[Jay Vosburgh]

Regarding #2 from comment #19:

As the defined range for the ipv6.mtu is from IPV6_MIN_MTU to the
device's MTU, and the existing API returns an error if the ipv6.mtu is
out of range, I think it's reasonable for a configuration with the
ipv6.mtu > device MTU to fail.

-- 
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 cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]
   
   * Original bug report below

  = end of systemd =

  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/cloud-init/+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 1296218] Re: aa-complain crashed with apparmor.common.AppArmorException in get_profile_flags(): '/etc/apparmor.d/usr.bin.chromium-browser contains no profile'

[Mathew Hodson]

Should be fixed in Trusty now that the new version has been backported.

apparmor (2.10.95-0ubuntu2.5~14.04.1) trusty; urgency=medium

  * Bring apparmor 2.10.95-0ubuntu2.5, from Ubuntu 16.04, to Ubuntu 14.04.
- This allows for proper snap confinement on Ubuntu 14.04 when using the
  hardware enablement kernel (LP: #1641243)

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

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

Title:
  aa-complain crashed with apparmor.common.AppArmorException in
  get_profile_flags(): '/etc/apparmor.d/usr.bin.chromium-browser
  contains no profile'

Status in AppArmor:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Released
Status in apparmor source package in Utopic:
  Fix Released

Bug description:
  Here the profile exists
  ---
  $ sudo aa-autodep /usr/bin/chromium-browser
  Profile for /usr/bin/chromium-browser already exists - skipping.
  
  Here it doesn't exist
  
  $ sudo aa-genprof /usr/bin/chromium-browser
  Traceback (most recent call last):
File "/usr/sbin/aa-genprof", line 102, in 
  apparmor.helpers[program] = apparmor.get_profile_flags(profile_filename, 
program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 600, in 
get_profile_flags
  raise AppArmorException(_('%s contains no profile') % filename)
  apparmor.common.AppArmorException: '/etc/apparmor.d/usr.bin.chromium-browser 
contains no profile'
  ---
  and finally this crashes again
  ---
  $ sudo aa-complain /usr/bin/chromium-browser
  Setting /usr/bin/chromium-browser to complain mode.
  Traceback (most recent call last):
File "/usr/sbin/aa-complain", line 30, in 
  tool.cmd_complain()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 178, in 
cmd_complain
  apparmor.set_complain(profile, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 264, in 
set_complain
  change_profile_flags(filename, program, 'complain', True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 603, in 
change_profile_flags
  old_flags = get_profile_flags(filename, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 600, in 
get_profile_flags
  raise AppArmorException(_('%s contains no profile') % filename)
  apparmor.common.AppArmorException: '/etc/apparmor.d/usr.bin.chromium-browser 
contains no profile'

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: apparmor-utils 2.8.95~2430-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-18.38-lowlatency 3.13.6
  Uname: Linux 3.13.0-18-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Sun Mar 23 08:47:30 2014
  ExecutablePath: /usr/sbin/aa-complain
  InstallationDate: Installed on 2014-03-08 (14 days ago)
  InstallationMedia: Ubuntu-Studio 14.04 "Trusty Tahr" - Alpha amd64 (20140224)
  InterpreterPath: /usr/bin/python3.4
  ProcCmdline: /usr/bin/python3 /usr/sbin/aa-complain /usr/bin/chromium-browser
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-lowlatency 
root=UUID=4333a8e9-30cd-431d-8682-8211c549f168 ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/sbin/aa-complain', '/usr/bin/chromium-browser']
  SourcePackage: apparmor
  Title: aa-complain crashed with apparmor.common.AppArmorException in 
get_profile_flags(): '/etc/apparmor.d/usr.bin.chromium-browser contains no 
profile'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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