[Touch-packages] [Bug 1802055] Re: package openssh-client 1:7.2p2-4ubuntu2.6 failed to install/upgrade: end of file on stdin at conffile prompt

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package openssh-client 1:7.2p2-4ubuntu2.6 failed to install/upgrade:
  end of file on stdin at conffile prompt

Status in openssh package in Ubuntu:
  New

Bug description:
  sw crash happened

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-client 1:7.2p2-4ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Nov  7 06:55:08 2018
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2018-09-26 (41 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.2p2 Ubuntu-4ubuntu2.6, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  Title: package openssh-client 1:7.2p2-4ubuntu2.6 failed to install/upgrade: 
end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2018-09-26T13:27:40.611382

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

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

[Touch-packages] [Bug 1802055] [NEW] package openssh-client 1:7.2p2-4ubuntu2.6 failed to install/upgrade: end of file on stdin at conffile prompt

[Ferenc Cserepkei]

Public bug reported:

sw crash happened

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-client 1:7.2p2-4ubuntu2.6
ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Nov  7 06:55:08 2018
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2018-09-26 (41 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
RelatedPackageVersions:
 ssh-askpass   N/A
 libpam-sshN/A
 keychain  N/A
 ssh-askpass-gnome N/A
SSHClientVersion: OpenSSH_7.2p2 Ubuntu-4ubuntu2.6, OpenSSL 1.0.2g  1 Mar 2016
SourcePackage: openssh
Title: package openssh-client 1:7.2p2-4ubuntu2.6 failed to install/upgrade: end 
of file on stdin at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.ssh.ssh_config: [modified]
mtime.conffile..etc.ssh.ssh_config: 2018-09-26T13:27:40.611382

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package openssh-client 1:7.2p2-4ubuntu2.6 failed to install/upgrade:
  end of file on stdin at conffile prompt

Status in openssh package in Ubuntu:
  New

Bug description:
  sw crash happened

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-client 1:7.2p2-4ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Nov  7 06:55:08 2018
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2018-09-26 (41 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.2p2 Ubuntu-4ubuntu2.6, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  Title: package openssh-client 1:7.2p2-4ubuntu2.6 failed to install/upgrade: 
end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2018-09-26T13:27:40.611382

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

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

[Touch-packages] [Bug 1791029] Re: cannot print pdf

[Launchpad Bug Tracker]

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

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

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

Title:
  cannot print pdf

Status in cups package in Ubuntu:
  Expired

Bug description:
  I cannot print pdfs on any printer. The file is processed in the
  printer dialogue and then disappears. without printing. I can print
  odf files on the same printer without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.5
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Thu Sep  6 11:10:50 2018
  InstallationDate: Installed on 2018-02-01 (216 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat:
   device for Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n: 
hp:/net/HP_LaserJet_200_colorMFP_M276n?ip=192.168.1.2
   device for Hewlett-Packard-HP-LaserJet-400-M401dne: 
hp:/net/HP_LaserJet_400_M401dne?zc=NPI13B8A2
  MachineType: LENOVO 20281
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-400-M401dne.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n.ppd: 
Permission denied
   grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-400-M401dne.ppd: Permission 
denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=18dad62c-a203-45d8-a228-4a2dfc8af342 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J6ET58WW (2.03 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20281  QB0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ6ET58WW(2.03):bd01/17/2014:svnLENOVO:pn20281:pvrM5400:rvnLENOVO:rn20281QB0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: M5400
  dmi.product.name: 20281
  dmi.product.version: M5400
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1802038] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Seth Arnold]

This looks like the source of the trouble:

Nov 06 21:09:57 kjhsdgf-ubu sshd[15085]: /etc/ssh/sshd_config line 125:
Subsystem 'sftp' already defined.

I hope this helps.

Thanks

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  On boot, got this error. Not expecting any magic solutions. Previous
  to this error, I updated python3 somewhat, and installed a package
  (pyseqlogo) that I moved around as I was figuring out where it should
  go.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   openssh-sftp-server:amd64: Install
   openssh-server:amd64: Install
   openssh-client:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Nov  6 21:09:58 2018
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-27 (163 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.6
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1802038] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  On boot, got this error. Not expecting any magic solutions. Previous
  to this error, I updated python3 somewhat, and installed a package
  (pyseqlogo) that I moved around as I was figuring out where it should
  go.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   openssh-sftp-server:amd64: Install
   openssh-server:amd64: Install
   openssh-client:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Nov  6 21:09:58 2018
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-27 (163 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.6
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1802038] [NEW] package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit statu

[Sl. Kjhsdgf]

Public bug reported:

On boot, got this error. Not expecting any magic solutions. Previous to
this error, I updated python3 somewhat, and installed a package
(pyseqlogo) that I moved around as I was figuring out where it should
go.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: openssh-server 1:7.6p1-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 openssh-sftp-server:amd64: Install
 openssh-server:amd64: Install
 openssh-client:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Nov  6 21:09:58 2018
ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-05-27 (163 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.6
SourcePackage: openssh
Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  On boot, got this error. Not expecting any magic solutions. Previous
  to this error, I updated python3 somewhat, and installed a package
  (pyseqlogo) that I moved around as I was figuring out where it should
  go.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   openssh-sftp-server:amd64: Install
   openssh-server:amd64: Install
   openssh-client:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Nov  6 21:09:58 2018
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-27 (163 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.6
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1801410] Re: Icons.keep.flashing

[Daniel van Vugt]

Can you please provide a photo or video of the problem "icons keep
flashing"?

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

Title:
  Icons.keep.flashing

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  lost.use.of.space.key
  very.slow.internet.connection
  Icons.keep.flashing

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Nov  2 09:56:43 2018
  DistUpgraded: 2018-11-01 23:04:23,218 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller (ThinkPad T520) [17aa:21cf]
  InstallationDate: Installed on 2017-09-21 (407 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 42424WU
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4a4b8720-cf83-49dd-b18a-63b77499e529 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-11-02 (0 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET55WW (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42424WU
  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:bvr8AET55WW(1.35):bd11/24/2011:svnLENOVO:pn42424WU:pvrThinkPadT520:rvnLENOVO:rn42424WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T520
  dmi.product.name: 42424WU
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Thu Nov  1 10:46:56 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1801976] Re: Display does not work correctly

[Daniel van Vugt]

Also, please run these commands and send the output:

  sudo apt install edid-decode
  for e in /sys/class/drm/*/edid ; do edid-decode $e ; done


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

Title:
  Display does not work correctly

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Initially everything was fine. Then came an update and now the display
  is milky and too large. I dont know what to do. What would be the
  proper BIOS Setting or how can the issue be settled?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Nov  6 18:07:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 
620M/630M/635M/640M LE] [144d:c0d1]
  InstallationDate: Installed on 2018-11-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABI.026.141024.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550P7C-T0ADE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABI.026.141024.dg:bd10/24/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP09ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550P7C-T0ADE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG SENS
  dmi.product.name: 550P5C/550P7C
  dmi.product.version: P09ABI
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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.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-server/+bug/1801976/+subscriptions

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

[Touch-packages] [Bug 1801976] Re: Display does not work correctly

[Daniel van Vugt]

That sounds unusual. Can you please attach a photo of the display when
it is "milky and too large" ?

** Tags added: hybrid nouveau

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

Title:
  Display does not work correctly

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Initially everything was fine. Then came an update and now the display
  is milky and too large. I dont know what to do. What would be the
  proper BIOS Setting or how can the issue be settled?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Nov  6 18:07:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 
620M/630M/635M/640M LE] [144d:c0d1]
  InstallationDate: Installed on 2018-11-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABI.026.141024.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550P7C-T0ADE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABI.026.141024.dg:bd10/24/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP09ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550P7C-T0ADE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG SENS
  dmi.product.name: 550P5C/550P7C
  dmi.product.version: P09ABI
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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.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-server/+bug/1801976/+subscriptions

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

[Touch-packages] [Bug 1800164] Re: Keyboard backlight control doesn't work on Asus N550JV

[Daniel van Vugt]

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

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

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

** This bug has been marked a duplicate of bug 1796550
   [regression] Keyboard brightness control keys (down/up) don't work in cosmic 
(upower 0.99.8)

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

Title:
  Keyboard backlight control doesn't work on Asus N550JV

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  Pressing Fn+F3 or Fn+F4 keys (which are the combinations to increase
  or decrease keyboard backlight brightness, respectively) doesn't do
  anything, the keyboard backlight stays off. Other key combinations,
  like adjusting display brightness or audio volume, do work.

  Keyboard backlight control worked in Kubuntu 18.04 on the same
  machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   2820 F pulseaudio
   /dev/snd/controlC1:  lastique   2820 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Oct 26 17:40:24 2018
  InstallationDate: Installed on 2013-10-11 (1840 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (6 days ago)
  WifiSyslog:
   
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JV
  dmi.product.sku: ASUS-NotebookSKU
  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/upower/+bug/1800164/+subscriptions

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

[Touch-packages] [Bug 1801898] Re: Only one of two external (displayport) displays is working without hotplug

[Daniel van Vugt]

Please run this command to send us more information about the machine:

  apport-collect 1801898

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Tags added: cosmic multimonitor

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

Title:
  Only one of two external (displayport) displays is working without
  hotplug

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in my one of 
my two external displays will not be activated without hotplugging the other 
external display.
  The display settings app shows the second display as inactive, and when 
trying to activate the settings app states that some hardware limitation stops 
it from being possible to apply the change.
  The laptop lid is closed, the internal laptop display is not active.

  Hotplugging the other external display solves the problem - after
  hotplug both external displays are active. This makes the bug annoying
  but workaroundable.

  I am not sure if this bug belongs to the Xorg package or the linux
  package.

  Hardware:
  Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two 
external displays connected through displayport (via docking station).

  $ sudo lspci -v
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 6000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu8
Candidate: 1:7.7+19ubuntu8
Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy linux-image-4.18.0-10-generic
  linux-image-4.18.0-10-generic:
Installed: 4.18.0-10.11
Candidate: 4.18.0-10.11
Version table:
   *** 4.18.0-10.11 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

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

[Touch-packages] [Bug 1800164] [NEW] Keyboard backlight control doesn't work on Asus N550JV

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Pressing Fn+F3 or Fn+F4 keys (which are the combinations to increase or
decrease keyboard backlight brightness, respectively) doesn't do
anything, the keyboard backlight stays off. Other key combinations, like
adjusting display brightness or audio volume, do work.

Keyboard backlight control worked in Kubuntu 18.04 on the same machine.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-10-generic 4.18.0-10.11
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lastique   2820 F pulseaudio
 /dev/snd/controlC1:  lastique   2820 F pulseaudio
CurrentDesktop: KDE
Date: Fri Oct 26 17:40:24 2018
InstallationDate: Installed on 2013-10-11 (1840 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: ASUSTeK COMPUTER INC. N550JV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic  N/A
 linux-firmware 1.175
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (6 days ago)
WifiSyslog:
 
dmi.bios.date: 11/19/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N550JV.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N550JV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N550JV
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: upower (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: amd64 apport-bug cosmic kernel-bug-exists-upstream 
kernel-fixed-upstream
-- 
Keyboard backlight control doesn't work on Asus N550JV
https://bugs.launchpad.net/bugs/1800164
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to upower in Ubuntu.

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

[Touch-packages] [Bug 1801410] Re: Icons.keep.flashing

[Seth Arnold]

Ow, this looks painful:

[  OK  ] Started Disk Manager.
 Starting Firmware update daemon...
[   ***] (2 of 3) A start job is running for 
Firmware update daemon (2s / 1min 30s)
[  *** ] (3 of 3) A start job is running for 
Daily apt download activities (45s / no limit)
[  OK  ] Started Firmware update daemon.
[ ***  ] (1 of 2) A start job is running for 
Hold until boot process finishes up (1min 6s / no limit)
[***   ] (1 of 2) A start job is running for 
Hold until boot process finishes up (1min 7s / no limit)
[**] (2 of 2) A start job is running for Daily 
apt download activities (51s / no limit)
[* ] (2 of 2) A start job is running for Daily apt 
download activities (51s / no limit)
[**] (2 of 2) A start job is running for Daily 
apt download activities (52s / no limit)
[***   ] (1 of 2) A start job is running for 
Hold until boot process finishes up (1min 9s / no limit)

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

Title:
  Icons.keep.flashing

Status in xorg package in Ubuntu:
  New

Bug description:
  lost.use.of.space.key
  very.slow.internet.connection
  Icons.keep.flashing

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Nov  2 09:56:43 2018
  DistUpgraded: 2018-11-01 23:04:23,218 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller (ThinkPad T520) [17aa:21cf]
  InstallationDate: Installed on 2017-09-21 (407 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 42424WU
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4a4b8720-cf83-49dd-b18a-63b77499e529 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-11-02 (0 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET55WW (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42424WU
  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:bvr8AET55WW(1.35):bd11/24/2011:svnLENOVO:pn42424WU:pvrThinkPadT520:rvnLENOVO:rn42424WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T520
  dmi.product.name: 42424WU
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Thu Nov  1 10:46:56 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1802007] [NEW] package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.

[Tomasz Dudziak]

Public bug reported:

asdf

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-1018.21-oem 4.15.18
Uname: Linux 4.15.0-1018-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Wed Oct 31 23:53:13 2018
DuplicateSignature:
 package:ubuntu-mono:16.10+18.04.20180421.1-0ubuntu1
 Unpacking ubuntu-mono (16.10+18.04.20181005-0ubuntu1) over 
(16.10+18.04.20180421.1-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-NjXhHv/37-ubuntu-mono_16.10+18.04.20181005-0ubuntu1_all.deb
 (--unpack):
  unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
ErrorMessage: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
InstallationDate: Installed on 2018-08-30 (68 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
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: ubuntu-themes
Title: package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to 
install/upgrade: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to
  install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-
  light/status/22/gnome-netstatus-rx.svg.dpkg-new': Operation not
  permitted

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  asdf

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-1018.21-oem 4.15.18
  Uname: Linux 4.15.0-1018-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct 31 23:53:13 2018
  DuplicateSignature:
   package:ubuntu-mono:16.10+18.04.20180421.1-0ubuntu1
   Unpacking ubuntu-mono (16.10+18.04.20181005-0ubuntu1) over 
(16.10+18.04.20180421.1-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-NjXhHv/37-ubuntu-mono_16.10+18.04.20181005-0ubuntu1_all.deb
 (--unpack):
unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-08-30 (68 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  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: ubuntu-themes
  Title: package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to 
install/upgrade: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1802007] Re: package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dp

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to
  install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-
  light/status/22/gnome-netstatus-rx.svg.dpkg-new': Operation not
  permitted

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  asdf

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-1018.21-oem 4.15.18
  Uname: Linux 4.15.0-1018-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct 31 23:53:13 2018
  DuplicateSignature:
   package:ubuntu-mono:16.10+18.04.20180421.1-0ubuntu1
   Unpacking ubuntu-mono (16.10+18.04.20181005-0ubuntu1) over 
(16.10+18.04.20180421.1-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-NjXhHv/37-ubuntu-mono_16.10+18.04.20181005-0ubuntu1_all.deb
 (--unpack):
unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-08-30 (68 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  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: ubuntu-themes
  Title: package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to 
install/upgrade: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1799118] Re: executing ubuntu-bug gives warnings

[Brian Murray]

** Summary changed:

- executing ubuntu-bug gives errors
+ executing ubuntu-bug gives warnings

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

Title:
  executing ubuntu-bug gives warnings

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When I use ubuntu-bug I get the following errors.

  robert@ASUS-A88XM-A:~/Desktop$ ubuntu-bug linux

  (apport-gtk:581): Gtk-WARNING **: 01:00:16.903: Theme parsing error:
  gtk-widgets.css:3135:13: 'max-width' is not a valid property name

  (apport-gtk:581): Gtk-WARNING **: 01:00:16.904: Theme parsing error: 
gtk-widgets.css:3136:14: 'max-height' is not a valid property name
  robert@ASUS-A88XM-A:~/Desktop$ 
  (google-chrome-stable:1222): Gtk-WARNING **: 01:00:33.982: Theme parsing 
error: gtk-widgets.css:3135:13: 'max-width' is not a valid property name

  (google-chrome-stable:1222): Gtk-WARNING **: 01:00:33.982: Theme parsing 
error: gtk-widgets.css:3136:14: 'max-height' is not a valid property name
  Created new window in existing browser session.

  Ubuntu MATE 18.04 totally crashed (I had to reinstall 18.04 just to
  boot). Since I was going to have to reinstall everything, I thought to
  check and see if 18.04 was the latest. It isn't, so I decided to try
  18.10 before reinstalling everything. Unfortunately, its still very
  buggy. Both the Software Botique and the Software app are buggy. With
  the Software app down, I can't even try to load Eclipse - which is in
  the 18.04 Software app.

  When I try to report bugs with ubuntu-bug, I get yet more bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 3464 F pulseaudio
   /dev/snd/controlC0:  robert 3464 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Oct 22 01:00:17 2018
  InstallationDate: Installed on 2018-10-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=7057e77c-c1e8-4bf5-9810-7609aceb50a0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

[Eric Desrochers]

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

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in unattended-upgrades source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in unattended-upgrades source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: systemd-networkd not renaming devices on boot

[Marcos]

@Mathieu: Me and Nicorac have the same bug: if set-name is used, there will be 
no IP at boot. The bug 1768827 is about the same problem as this one (set-name 
not renaming interface at boot), which is resolved by now...
The strange thing is the inconsistency between the two installation types 
(subiquity and the legacy debian-installer). Please, could you try and install 
a vm with the debian-installer and try it yourself? Why does one work and the 
other doesn't? 

Created bug 1802004, IMO 17868827 should be closed, as renames are
working as expected now...

-- 
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 Released
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
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  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
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft 

[Touch-packages] [Bug 1792370] Re: Broken links to libmircookie packages

[Piotr Dabrowski]

I tured on localhost server, created
'cookie.php?cookie=somecookieinstring' test and access it from other
computer - everything works fine, so it's definitely NOT router fault. I
think, I'll show finger to my ISP

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

Title:
  Broken links to libmircookie packages

Status in mir package in Ubuntu:
  Invalid

Bug description:
  Can't install libmircookie via apt or dawnload from
  https://packages.ubuntu.com/xenial/libmircookie-dev. Every link to
  libmircookie package at
  http://security.ubuntu.com/ubuntu/pool/main/m/mir/ seems to be broken.
  Its wrong filename at server: libmircoieok instead libmircookie.

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

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

[Touch-packages] [Bug 1801128] Re: OpenSSH 7.7 -w tunnel bug

[Andreas Hasenack]

Debian has 7.9p1, so as soon as Disco opens up for development the next
sync will get the fix there.

** Also affects: openssh (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

Title:
  OpenSSH 7.7 -w tunnel bug

Status in openssh package in Ubuntu:
  New
Status in openssh source package in Cosmic:
  New

Bug description:
  Just upgraded to cosmic, which picks up OpenSSH 7.7.

  OpenSSH 7.7 has known bug
  https://bugzilla.mindrot.org/show_bug.cgi?id=2855 which is fixed in
  OpenSSH 7.8.  It's a regression that completely breaks -w tunneling.

  The OpenSSH bug contains a trivial two-line patch to fix the bug.  I
  downloaded the Ubuntu openssh package source, applied the patch and
  rebuilt, and can confirm that is does fix the problem.

  Any chance we could get this patch backported to Cosmic?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: openssh-client 1:7.7p1-4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Thu Nov  1 09:36:16 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: Upgraded to cosmic on 2018-11-01 (0 days ago)

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

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

[Touch-packages] [Bug 1800877] Re: iproute2/xenial: Add support for the VF Trust setting (fix IPv6 multicast under SR-IOV on Mellanox adapters)

[Brian Murray]

Hello Mauricio, or anyone else affected,

Accepted iproute2 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.3.0-1ubuntu3.16.04.4 in
a few hours, and then in the -proposed repository.

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

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

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

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

Title:
  iproute2/xenial: Add support for the VF Trust setting (fix IPv6
  multicast under SR-IOV on Mellanox adapters)

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

Bug description:
  [Impact]

   * An VM's VF cannot receive IPv6 multicast traffic
     from other VMs' VFs in the same Mellanox adapter
     _if_ its VF trust setting is not enabled, and on
     Xenial currently iproute2 _cannot_ enable it.

   * This breaks IPv6 NDP (Neighbor Discovery Protocol)
     in that scenario.

   * This upload adds three iproute2 upstream commits
     to enable/disable the VF setting, which resolves
     that problem/limitation.

  [Test Case]

   * Check 'ip link help' for the 'trust' option:

     Before:

   # ip link help 2>&1 | grep trust
   

     After:

   # ip link help 2>&1 | grep trust
   [ trust { on | off} ] ]

   * Check 'ip link show dev PF' for 'trust on|off' field in VFs.

     Before: (trust field _is not_ present)

   # ip link show dev ens1f0
   ...
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

     After: (trust field _is_ present)

   # ip link show dev ens1f0
   ...
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

   * Set the VF trust on/off and check it:

   Set VF 0 trust on:

   # ip link set ens1f0 vf 0 trust on
   # ip link show dev ens1f0 | grep trust
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust on
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

   Set VF 0 trust off:

   # ip link set ens1f0 vf 0 trust off
   # ip link show dev ens1f0 | grep trust
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

  [Regression Potential]

   * Regression potential is low because the commits just add the
     netlink attribute for the userspace-kernel interface and the
     ways to set/clear it, and show the current value to the user.

   * Regressions could happen _if_ the user turns the setting on
     (it's disabled by default) and there's a problem/bug likely
     in _other_ component that depends on that setting (which is
     something to fix on such component).

  [Other Info]

   * The users that reported this problem have verified
     the test package with these changes, and confirmed
     that it now works correctly for IPv6 NDP/multicast.

   * Upstream commits:
   
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=dddf1b44126e
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe9322781e63
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=b6d77d9ee312

   * Only affect Xenial release :

   # rmadison iproute2
   iproute2 | 4.3.0-1ubuntu3.16.04.3 | xenial-updates
   iproute2 | 4.15.0-2ubuntu1| bionic 
   iproute2 | 4.18.0-1ubuntu2| cosmic
   iproute2 | 4.18.0-1ubuntu2| disco  

   # iproute2 upstream vcs

   $ git describe --contains dddf1b44126e
   v4.4.0~67

   $ git describe --contains b6d77d9ee312
   v4.5.0~47

   $ git describe --contains 

[Touch-packages] [Bug 1792370] Re: Broken links to libmircookie packages

[Piotr Dabrowski]

Wow. After changing to 'c%6f%6fkie' everything seems to be ok.

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

Title:
  Broken links to libmircookie packages

Status in mir package in Ubuntu:
  Invalid

Bug description:
  Can't install libmircookie via apt or dawnload from
  https://packages.ubuntu.com/xenial/libmircookie-dev. Every link to
  libmircookie package at
  http://security.ubuntu.com/ubuntu/pool/main/m/mir/ seems to be broken.
  Its wrong filename at server: libmircoieok instead libmircookie.

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

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

[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.40.1~18.04.2

---
netplan.io (0.40.1~18.04.2) bionic; urgency=medium

  * Fix typo breaking rename on 'netplan apply'. (LP: #1770082)

netplan.io (0.40.1~18.04.1) bionic; urgency=medium

  * Backport netplan 0.40.1 to 18.04. (LP: #1793309)

netplan.io (0.40.1) cosmic; urgency=medium

  * tests/generate.py: use random.sample() instead of random.choices() to
better support older pythons.
  * Deal gracefully with empty files on 'netplan apply' (LP: #1795343)

netplan.io (0.40) cosmic; urgency=medium

  * New upstream release:
- networkd: route source is PreferredSource= not From=
- Improve NetworkManager error reporting on unrenderable routes.
- Don't render ipv4 dns-search unless we have an ipv4 address.
  (LP: #1786726)
- Set permissive umask on networkd .network, .link and .netdev files
  (LP: #1736965, LP: #1768560)
- Fix support for link-scope routes. (LP: #1747455)
- Update man pages for deletion of replug code.
- Spell Gratuitous ARP correctly and make it work. (LP: #1756701)
- Many typo fixes for documentation. (LP: #1783940)
- Various build system fixes.
- Fix integration tests:
  - iproute2 output changes for link-scope routes
  - fix stability of networkd igmp-resend test
  - fix manual_addresses test now that networkd lists ~. domain
- Deduplicate code for parsing interface options
- Add support for optional-addresses.

netplan.io (0.39) cosmic; urgency=medium

  * New upstream release:
- Allow link-local addresses to be configured. (LP: #1771704)
- Forces bridges with no addresses to be brought online. (LP: #1736975)

netplan.io (0.38) cosmic; urgency=medium

  * New upstream release:
- Write udev .rules files to /run/udev/rules.d to enforce interface
  renaming. (LP: #1770082)
- Don't traceback for 'netplan ip leases' when iface is not managed or
  doesn't DHCP (LP: #1768823)
- Fix duplicate "/" path separator in error messages (LP: #1771440)
- Fix incorrect terminal reset in 'netplan try' on Ctrl-C. (LP: #1768798)
- Updated doc entries: mtu, fix fwmark->mark, cleanup optional.
  (LP: #1768783)
- Added documentation validation at build.
- Added configuration example for multi-ip interfaces.
  * tests/integration.py: fix test_eth_and_bridge autopkg test harder.
  * debian/control:
- Add iproute2 to Depends.
- Add python3-netifaces to Depends, Build-Depends.

 -- Mathieu Trudel-Lapierre   Mon, 22 Oct 2018
15:02:30 -0400

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Won't Fix
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the 

[Touch-packages] [Bug 1792370] Re: Broken links to libmircookie packages

[Manfred Hampl]

What do you get when changing each occurrence of 'cookie' into
'c%6f%6fkie' in the url?

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

Title:
  Broken links to libmircookie packages

Status in mir package in Ubuntu:
  Invalid

Bug description:
  Can't install libmircookie via apt or dawnload from
  https://packages.ubuntu.com/xenial/libmircookie-dev. Every link to
  libmircookie package at
  http://security.ubuntu.com/ubuntu/pool/main/m/mir/ seems to be broken.
  Its wrong filename at server: libmircoieok instead libmircookie.

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

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

[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Keith Myers]

● whoopsie.service - crash report submission daemon
   Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Wed 2018-10-31 11:57:10 PDT; 5 days ago
 Main PID: 1457 (whoopsie)
Tasks: 3 (limit: 4915)
   CGroup: /system.slice/whoopsie.service
   └─1457 /usr/bin/whoopsie -f

Nov 05 00:22:37 Serenity whoopsie[1457]: [00:22:37] offline
Nov 05 00:27:08 Serenity whoopsie[1457]: [00:27:08] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 05 00:27:08 Serenity whoopsie[1457]: [00:27:08] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 05 00:27:08 Serenity whoopsie[1457]: [00:27:08] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 05 00:27:09 Serenity whoopsie[1457]: [00:27:09] online
Nov 06 05:12:37 Serenity whoopsie[1457]: [05:12:37] offline
Nov 06 05:17:08 Serenity whoopsie[1457]: [05:17:08] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 06 05:17:08 Serenity whoopsie[1457]: [05:17:08] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 06 05:17:08 Serenity whoopsie[1457]: [05:17:08] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Nov 06 05:17:10 Serenity whoopsie[1457]: [05:17:10] online

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: systemd-networkd not renaming devices on boot

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.40.1~18.04.2

---
netplan.io (0.40.1~18.04.2) bionic; urgency=medium

  * Fix typo breaking rename on 'netplan apply'. (LP: #1770082)

netplan.io (0.40.1~18.04.1) bionic; urgency=medium

  * Backport netplan 0.40.1 to 18.04. (LP: #1793309)

netplan.io (0.40.1) cosmic; urgency=medium

  * tests/generate.py: use random.sample() instead of random.choices() to
better support older pythons.
  * Deal gracefully with empty files on 'netplan apply' (LP: #1795343)

netplan.io (0.40) cosmic; urgency=medium

  * New upstream release:
- networkd: route source is PreferredSource= not From=
- Improve NetworkManager error reporting on unrenderable routes.
- Don't render ipv4 dns-search unless we have an ipv4 address.
  (LP: #1786726)
- Set permissive umask on networkd .network, .link and .netdev files
  (LP: #1736965, LP: #1768560)
- Fix support for link-scope routes. (LP: #1747455)
- Update man pages for deletion of replug code.
- Spell Gratuitous ARP correctly and make it work. (LP: #1756701)
- Many typo fixes for documentation. (LP: #1783940)
- Various build system fixes.
- Fix integration tests:
  - iproute2 output changes for link-scope routes
  - fix stability of networkd igmp-resend test
  - fix manual_addresses test now that networkd lists ~. domain
- Deduplicate code for parsing interface options
- Add support for optional-addresses.

netplan.io (0.39) cosmic; urgency=medium

  * New upstream release:
- Allow link-local addresses to be configured. (LP: #1771704)
- Forces bridges with no addresses to be brought online. (LP: #1736975)

netplan.io (0.38) cosmic; urgency=medium

  * New upstream release:
- Write udev .rules files to /run/udev/rules.d to enforce interface
  renaming. (LP: #1770082)
- Don't traceback for 'netplan ip leases' when iface is not managed or
  doesn't DHCP (LP: #1768823)
- Fix duplicate "/" path separator in error messages (LP: #1771440)
- Fix incorrect terminal reset in 'netplan try' on Ctrl-C. (LP: #1768798)
- Updated doc entries: mtu, fix fwmark->mark, cleanup optional.
  (LP: #1768783)
- Added documentation validation at build.
- Added configuration example for multi-ip interfaces.
  * tests/integration.py: fix test_eth_and_bridge autopkg test harder.
  * debian/control:
- Add iproute2 to Depends.
- Add python3-netifaces to Depends, Build-Depends.

 -- Mathieu Trudel-Lapierre   Mon, 22 Oct 2018
15:02:30 -0400

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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 Released
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 

[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

[Mario Vukelic]

To be clear, the above debugging output is with xkb-data
2.23.1-1ubuntu1.18.10.1 installed and therefore the DISabling of
airplane mode by the dedicated key being broken

$ aptitude show xkb-data
Package: xkb-data
Version: 2.23.1-1ubuntu1.18.10.1
State: installed

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

[Mario Vukelic]

@Sebastien: That's the thing, on the Dell XPS 15 9575 there IS a
regression with xkb-data 2.23.1-1ubuntu1.18.10.1.

On this machine, the airplane mode key worked perfectly out-of-the-box
(i.e., the key enabled AND disabled the airplane mode) with the
development version of  Cosmic, using xkb-data 2.23. See my comment #13
further up in this bug.

Here's the debug output for gnome-settings-daemon:

[*** Airplane mode is off, Wifi and BT are on ***]

/usr/lib/gnome-settings-daemon/gsd-rfkill -v
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 
'WLAN' (idx=1): soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 
'BLUETOOTH' (idx=11): soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added Bluetooth rfkill 
with ID 11
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.185: Registered client at 
path /org/gnome/SessionManager/Client29
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.187: Opened rfkill-input 
inhibitor.

[*** Here I am pressing the airplane mode key to enable Airplane mode >
Wifi/BT goes off ***]

(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.352: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.353: Changed Bluetooth rfkill 
with ID 11

[*** Here I am pressing the airplane mode key again to DISable Airplane
mode > Wifi/BT should go back on. This fails and the airplane mode re-
engages immediately as described ***]

(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed Bluetooth rfkill 
with ID 11
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed Bluetooth rfkill 
with ID 11

[*** Here I am pressing DISabling Airplane mode from the Gnome panel
menu > Wifi/BT goes back on. This works ***]

(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed Bluetooth rfkill 
with ID 11

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Touch-packages] [Bug 1801762] Re: Dual-signed things should be easy to verify with one key

[TJ]

Julian - I hadn't realised there are two gpgv's!

Having found apt's own /usr/lib/methods/gpgv

I have been able to create a shell wrapper that can feed it the expected
request headers and parse the response headers to ensure a GPGVOutput:
GOODSIG ...

It's a proof of concept right now; if this approach is preferred then
I'll tidy it up and publish.

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

Title:
  Dual-signed things should be easy to verify with one key

Status in apt package in Ubuntu:
  New
Status in debmirror package in Ubuntu:
  New
Status in gnupg2 package in Ubuntu:
  New
Status in ubuntu-keyring package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  As part of Ubuntu key rotation strategy, we rely on dual-signing
  (inline, or detached) such that validation with at least one key
  available in a keyring should be trusted, without using web-of-trust.

  However, it seems to be only correctly so far implemented by the apt's
  gpgv method.

  Ideally, we should ship an easy enough to use the helper that is `like
  gpgv` to use, and possibly reusing apt's gpgv code and/or exposing it
  via apt-key's verify.

  The problem seems to be that 1 good sig + 1 no public key available,
  results in gpgv exiting with 2, instead of 0 or 1.

  Ideally it should be easy enough to use gpgv/gpg to verify that at
  least one signature is good, and decrypt/extract signed contents only.

  More details and reproducers to follow.

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

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

[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Cristian Aravena Romero]

Brian,

caravena@romanescu:~$ sudo systemctl status whoopsie.service
● whoopsie.service - crash report submission daemon
   Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Tue 2018-11-06 07:33:02 -03; 6h ago
 Main PID: 1665 (whoopsie)
Tasks: 3 (limit: 4915)
   Memory: 3.1M
   CGroup: /system.slice/whoopsie.service
   └─1665 /usr/bin/whoopsie -f

nov 06 11:33:26 romanescu whoopsie[1665]: [11:33:26] offline
nov 06 11:33:27 romanescu whoopsie[1665]: [11:33:27] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
nov 06 11:33:27 romanescu whoopsie[1665]: [11:33:27] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
nov 06 11:33:27 romanescu whoopsie[1665]: [11:33:27] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
nov 06 11:33:29 romanescu whoopsie[1665]: [11:33:29] online
nov 06 12:03:38 romanescu whoopsie[1665]: [12:03:38] offline
nov 06 12:03:40 romanescu whoopsie[1665]: [12:03:40] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
nov 06 12:03:40 romanescu whoopsie[1665]: [12:03:40] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
nov 06 12:03:40 romanescu whoopsie[1665]: [12:03:40] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
nov 06 12:03:41 romanescu whoopsie[1665]: [12:03:41] online

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Cristian Aravena Romero]

** Attachment added: "sudo systemctl status whoopsie.service"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5209737/+files/sudo_systemctl_status_whoopsie.service.txt

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1801976] [NEW] Display does not work correctly

[HeinzDiedrichsen]

Public bug reported:

Initially everything was fine. Then came an update and now the display
is milky and too large. I dont know what to do. What would be the proper
BIOS Setting or how can the issue be settled?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Tue Nov  6 18:07:43 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 620M/630M/635M/640M 
LE] [144d:c0d1]
InstallationDate: Installed on 2018-11-06 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P09ABI.026.141024.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP550P7C-T0ADE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABI.026.141024.dg:bd10/24/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP09ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550P7C-T0ADE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: SAMSUNG SENS
dmi.product.name: 550P5C/550P7C
dmi.product.version: P09ABI
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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.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

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


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

Title:
  Display does not work correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  Initially everything was fine. Then came an update and now the display
  is milky and too large. I dont know what to do. What would be the
  proper BIOS Setting or how can the issue be settled?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Nov  6 18:07:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 
620M/630M/635M/640M LE] [144d:c0d1]
  InstallationDate: Installed on 2018-11-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABI.026.141024.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550P7C-T0ADE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 

[Touch-packages] [Bug 1726803] Re: unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess insta

[Balint Reczey]

Verified with shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1:
...
ubuntu@autopkgtest:/var/cache/apt/archives$ sudo  rm 
/var/lib/shim-signed/mok/MOK.der
ubuntu@autopkgtest:/var/cache/apt/archives$ sudo   update-secureboot-policy 
--new-key
Generating a new Secure Boot signing key:
Generating a 2048 bit RSA private key
...+++
...+++
writing new private key to '/var/lib/shim-signed/mok/MOK.priv'
-
root@autopkgtest:/var/cache/apt/archives# echo /var/lib/dkms/zzz >> 
/var/lib/shim-signed/dkms-list
root@autopkgtest:/var/cache/apt/archives# env DEBIAN_FRONTEND=noninteractive 
update-secureboot-policy --enroll-key; echo $?
Running in non-interactive mode, doing nothing.
0
root@autopkgtest:/var/cache/apt/archives# cat > /var/lib/shim-signed/dkms-list 
< /var/lib/dkms
> /var/lib/dkms/nvidia-1
> /var/lib/dkms/r8168
> EOF
root@autopkgtest:/var/cache/apt/archives#  mkdir /var/lib/dkms/nvidia
root@autopkgtest:/var/cache/apt/archives# env DEBIAN_FRONTEND=noninteractive 
update-secureboot-policy --enroll-key; echo $?
Running in non-interactive mode, doing nothing.
0
root@autopkgtest:/var/cache/apt/archives#  cat > /var/lib/shim-signed/dkms-list 
< /var/lib/dkms
> /var/lib/dkms/r8168
> EOF
root@autopkgtest:/var/cache/apt/archives# env DEBIAN_FRONTEND=noninteractive 
update-secureboot-policy --enroll-key; echo $?
Running in non-interactive mode, doing nothing.
--- /var/lib/shim-signed/dkms-list  2018-11-06 17:47:43.490071095 +0100
+++ /var/lib/shim-signed/dkms-list.new  2018-11-06 17:47:43.490071095 +0100
@@ -1,2 +1,3 @@
 /var/lib/dkms
+/var/lib/dkms/nvidia
 /var/lib/dkms/r8168
1


** Description changed:

  [Impact]
  
   * When Secure Boot is enabled and MOK is not set and a new dkms module
  is installed sim-signed asks for a Secure Boot MOK, or aborts package
  installation in non-interactive mode. When unattended-upgrades performed
  the upgrade the aborted installation leaves an unconfigured system
  behind that may even fail to boot. In nvdidia's special case the new
  module is actually just a new version of the nvidia module which should
  be fine to install.
  
   * The fix in shim-signed now handles nvidia dkms module directory
  renames as simple upgrades and also does not handle module removals as a
  reason to abort installation.
  
  [Test Case (shim-signed)]
  
  1. Set up Bionic system with Secure Boot enabled.
  
  2. Install packagages to trigger MOK enrollment and enroll the key:
  
-  apt install dkms shim-signed r8168-dkms
+  apt install dkms shim-signed r8168-dkms
  
  3. Create a new key to be enrolled again:
  
-  rm /var/lib/shim-signed/mok/MOK.der
-  update-secureboot-policy  --new-key
+  rm /var/lib/shim-signed/mok/MOK.der
+  update-secureboot-policy  --new-key
  
  4. Simulate module removal and test that the command returns 0:
-  
+ 
  # echo /var/lib/dkms/zzz >> /var/lib/shim-signed/dkms-list
  # env DEBIAN_FRONTEND=noninteractive update-secureboot-policy  --enroll-key; 
echo $?
  Running in non-interactive mode, doing nothing.
  0
  
  5.  Simulate nvidia module rname and test that the command returns 0:
  
  # cat > /var/lib/shim-signed/dkms-list < /var/lib/shim-signed/dkms-list  < 
/etc/apt/apt.conf.d/51unattended-upgrades-all
  
  5. Observe u-u keeping back the new package:
  unattended-upgrade --verbose --dry-run --debug
  ...
  Checking: r8168-dkms ([])
  pkg new-dkms-dep may trigger secure boot key prompt
  sanity check failed
  ...
  
  [Regression Potential (shim-signed)]
  
  * The fix lets installation of nvidia dkms module upgrades continue and also 
lets dkms module removals continue when MOK is not set and those should not 
cause regressions themselves. In case of an implementation mistake a new module 
installation could go undetected and could cause the system not load a dkms 
module on next boot.
  In practice not loading new modules rarely cause regressions, but if a module 
is converted from being in the kernel to a dkms module upon an upgrade this is 
possible.
   * I tested the module addition, removal, nvidia module upgrade and not 
module change cases with stubs pretending that the system is secure-boot 
capable an found the changed script working properly.
  
  [Regression Potential (unattended-upgrades)]
  
  * Since the fix is holding back packages from installation it is
  expected that systems that would have otherwise broke during the
  installation would not receive all updates. Since exact detection of the
  installation failure reported here does not seem possible u-u holds back
  more packages than it would be absolutely necessary.
  
  * Administrators are expected to set up email notifications about the
  updates performed by u-u and act on held back packages.
  
  * Since updates pulling in new packages are fairly rare especially in
  the -security pocket which u-u installs from by default unwanted
  regressions are 

[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Brian Murray]

I've done some digging into this and now I'm curious about the output of
'sudo systemctl status whoopsie.service'. Please let me know!

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1799625] Re: Enable journald support

[Dmitry Shachnev]

Please see the linked Debian bug for the latest status on this.

TL;DR: We are not going to built with journald support for now, as it
can break tests of some reverse dependencies.

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

Title:
  Enable journald support

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Debian:
  Unknown
Status in Fedora:
  Unknown

Bug description:
  ...

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

-- 
Mailing list: https://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 1801918] Re: storage pool with persistent device names fails

[Jan Marquardt]

Christian, thank you for pointing me in the right direction. Adding

filter = [ "a|/dev/disk/by-path/pci-*|" ]

to /etc/lvm/lvm.conf solved this issue. (There is no need to restart any
service after changing this file. ;))

You can find the thread on the mailing list under this link:
https://www.redhat.com/archives/libvirt-users/2018-October/msg00059.html

I'll add a response there soon.

Best Regards

Jan

Am 06.11.18 um 15:48 schrieb  Christian Ehrhardt :
> I now used:
>   filter =[ "a|/dev/disk/by-path/virtio-pci-*|" ]
> 
> Now it really is the same way on creation and query.
> $ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
>   Physical volume "/dev/disk/by-path/virtio-pci-:00:07.0" successfully 
> created.
> $ sudo pvdisplay 
>   "/dev/disk/by-path/virtio-pci-:00:07.0" is a new physical volume of 
> "30.00 MiB"
>   --- NEW Physical volume ---
>   PV Name   /dev/disk/by-path/virtio-pci-:00:07.0
> 
> And with that finally
> $ sudo virsh pool-build testpool1
> Pool testpool1 built
> 
> $ sudo virsh pool-start testpool1
> Pool testpool1 started
> 
> I'd still be interested in the mail thread link.
> But for your case, if you want to use by-path with LVM you should adapt the 
> lvm.conf to use (only) these.
> 
> ** Changed in: libvirt (Ubuntu)
>Status: Incomplete => Invalid
> 

-- 
Artfiles New Media GmbH | Zirkusweg 1 | 20359 Hamburg
Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
E-Mail: supp...@artfiles.de | Web: http://www.artfiles.de
Geschäftsführer: Harald Oltmanns | Tim Evers
Eingetragen im Handelsregister Hamburg - HRB 81478

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

Title:
  storage pool with persistent device names fails

Status in libvirt package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Invalid

Bug description:
  lvm2 tools do not store by-path values in their config.
  That can drive scripts/tools (like the libvirt case here) mad.
  Simplified example:

  $ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
  $ sudo /sbin/pvs --noheadings -o pv_name,vg_name
/dev/vdc

  It is NOT using /dev/disk/by-path/virtio-pci-:00:07.0 as
  instructed, but instead did the mapping to /dev/vdd and keeps that
  from now on.

  I know that "inside" lvm all that is done via metadata and it won't matter.
  But tools around it get confused.
  Not sure yet if it is a real issue, or just "works as designed".

  
  --- started as libvirt issue - keeping old desc below ---

  I am trying to create a logical volume storage pool with persistent
  device names for the block devices, because I can't/don't want to ensure
  that /dev/sd* names are persistent through reboots.

  virsh # pool-define-as web2067 logical - -
  /dev/disk/by-path/pci-:18:00.0-scsi-0:2:2:0  web2067 /dev/web2067
  virsh # pool-build web2067

  These two steps work as expected and the pv and the vg get created, but
  when I try to start the pool I get the following error:

  virsh # pool-start web2067
  error: Failed to start pool web2067
  error: unsupported configuration: cannot find any matching source
  devices for logical volume group 'web2067'

  If I do the same steps just with /dev/sdX instead of
  /dev/disk/by-path/..., the pool gets created correctly.

  According to the libvirt mailing list /dev and /dev/disk/by-path are
  supposed to work the same way.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

@Marcos:

Please file a new bug for your own issue; include the output of
'networkctl', and report the bug number here so we can find it.

>From a quick look, I think there's no carrier detected. This could be a
driver bug.

-- 
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
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  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
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
   

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

[Mathieu Trudel-Lapierre]

Please use bug 1768827 to track such "no IP at boot" issues; there's
nothing that currently indicates that this is a regression, it needs
further investigation, but not here.

-- 
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
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  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
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  

[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

[Sebastien Bacher]

Thanks for the data Mario, seems like it's not the backend then but that there 
is a bug in the key handling. Unsure we can describe it as "regression" though, 
the feature was not working at all, now it's half working.
Or was it something that is currently working on cosmic and which isn't now?

The log doesn't have informations on gnome-settings-daemon though which
would be useful to have (but unsure what's the easiest way to put in
debug mode, maybe restart it manually with --debug?)

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Keith Myers]

This is what service apport-autoreport status shows now.  I still have
the Failed status in the error log at each boot.

keith@Serenity:~$ service apport-autoreport status
● apport-autoreport.service - Process error reports when automatic reporting is 
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor
   Active: inactive (dead) since Fri 2018-11-02 15:11:10 PDT; 3 days ago
 Main PID: 24527 (code=exited, status=0/SUCCESS)

● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; 
vendor preset: enabled)
   Active: inactive (dead) since Fri 2018-11-02 15:11:10 PDT; 3 days ago
 Main PID: 24527 (code=exited, status=0/SUCCESS)

Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: a = os.fspath(a)
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: TypeError: expected str, 
bytes or os.PathLike object, not NoneType
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: ERROR: processing 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.cr
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]:   skipping, not a crash
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: 
/var/crash/_usr_bin_yelp.1000.crash already marked for upload, skipping
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]:   skipping, not a crash
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: Collecting info for 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]:   skipping, not a crash
Nov 02 15:11:10 Serenity whoopsie-upload-all[24527]: All reports processed
Nov 02 15:11:10 Serenity systemd[1]: Started Process error reports when 
automatic reporting is enabled.

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Sebastien Bacher]

** Changed in: libdrm (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libclc (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: llvm-toolchain-7 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
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:
  New
Status in llvm-toolchain-7 source package in Bionic:
  New
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 1801918] Re: storage pool with persistent device names fails

[ Christian Ehrhardt ]

I now used:
  filter =[ "a|/dev/disk/by-path/virtio-pci-*|" ]

Now it really is the same way on creation and query.
$ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
  Physical volume "/dev/disk/by-path/virtio-pci-:00:07.0" successfully 
created.
$ sudo pvdisplay 
  "/dev/disk/by-path/virtio-pci-:00:07.0" is a new physical volume of 
"30.00 MiB"
  --- NEW Physical volume ---
  PV Name   /dev/disk/by-path/virtio-pci-:00:07.0

And with that finally
$ sudo virsh pool-build testpool1
Pool testpool1 built

$ sudo virsh pool-start testpool1
Pool testpool1 started

I'd still be interested in the mail thread link.
But for your case, if you want to use by-path with LVM you should adapt the 
lvm.conf to use (only) these.

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

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

Title:
  storage pool with persistent device names fails

Status in libvirt package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Invalid

Bug description:
  lvm2 tools do not store by-path values in their config.
  That can drive scripts/tools (like the libvirt case here) mad.
  Simplified example:

  $ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
  $ sudo /sbin/pvs --noheadings -o pv_name,vg_name
/dev/vdc

  It is NOT using /dev/disk/by-path/virtio-pci-:00:07.0 as
  instructed, but instead did the mapping to /dev/vdd and keeps that
  from now on.

  I know that "inside" lvm all that is done via metadata and it won't matter.
  But tools around it get confused.
  Not sure yet if it is a real issue, or just "works as designed".

  
  --- started as libvirt issue - keeping old desc below ---

  I am trying to create a logical volume storage pool with persistent
  device names for the block devices, because I can't/don't want to ensure
  that /dev/sd* names are persistent through reboots.

  virsh # pool-define-as web2067 logical - -
  /dev/disk/by-path/pci-:18:00.0-scsi-0:2:2:0  web2067 /dev/web2067
  virsh # pool-build web2067

  These two steps work as expected and the pv and the vg get created, but
  when I try to start the pool I get the following error:

  virsh # pool-start web2067
  error: Failed to start pool web2067
  error: unsupported configuration: cannot find any matching source
  devices for logical volume group 'web2067'

  If I do the same steps just with /dev/sdX instead of
  /dev/disk/by-path/..., the pool gets created correctly.

  According to the libvirt mailing list /dev and /dev/disk/by-path are
  supposed to work the same way.

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

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

[Touch-packages] [Bug 1801918] Re: storage pool with persistent device names fails

[ Christian Ehrhardt ]

This is again a case of please read all characters carefully :-)

definition from xml:
(gdb) p def->source.devices[i].path
$4 = 0x7f5204008e30 "/dev/disk/by-path/virtio-pci-:00:07.0"

compared against the array it built with the lvm tools
(gdb) p thisSource->devices[0]
$7 = {nfreeExtent = 0, freeExtents = 0x0, path = 0x7f51fc012b20 
"/dev/disk/by-path/pci-:00:07.0", format = 0, part_separator = 0, geometry 
= {cylinders = 0, heads = 0, sectors = 0}}

That is different:
/dev/disk/by-path/virtio-pci-:00:07.0
/dev/disk/by-path/pci-:00:07.0

Lets further improve the lvm config we have.

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

Title:
  storage pool with persistent device names fails

Status in libvirt package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Invalid

Bug description:
  lvm2 tools do not store by-path values in their config.
  That can drive scripts/tools (like the libvirt case here) mad.
  Simplified example:

  $ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
  $ sudo /sbin/pvs --noheadings -o pv_name,vg_name
/dev/vdc

  It is NOT using /dev/disk/by-path/virtio-pci-:00:07.0 as
  instructed, but instead did the mapping to /dev/vdd and keeps that
  from now on.

  I know that "inside" lvm all that is done via metadata and it won't matter.
  But tools around it get confused.
  Not sure yet if it is a real issue, or just "works as designed".

  
  --- started as libvirt issue - keeping old desc below ---

  I am trying to create a logical volume storage pool with persistent
  device names for the block devices, because I can't/don't want to ensure
  that /dev/sd* names are persistent through reboots.

  virsh # pool-define-as web2067 logical - -
  /dev/disk/by-path/pci-:18:00.0-scsi-0:2:2:0  web2067 /dev/web2067
  virsh # pool-build web2067

  These two steps work as expected and the pv and the vg get created, but
  when I try to start the pool I get the following error:

  virsh # pool-start web2067
  error: Failed to start pool web2067
  error: unsupported configuration: cannot find any matching source
  devices for logical volume group 'web2067'

  If I do the same steps just with /dev/sdX instead of
  /dev/disk/by-path/..., the pool gets created correctly.

  According to the libvirt mailing list /dev and /dev/disk/by-path are
  supposed to work the same way.

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

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

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Sebastien Bacher]

tagging as rls-cc-notfixing, while good to fix it impacts a non default
plugin and we don't think it's important enough to be actively tracked
by desktop

** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1801918] Re: storage pool with persistent device names fails

[ Christian Ehrhardt ]

lvm2 - config option intentionally starting safe, how to use it is outlined => 
invalid
libvirt - IMHO it should now work, need to debug more and wait for the 
mentioned upstream discussion => incomplete

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

Title:
  storage pool with persistent device names fails

Status in libvirt package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  Invalid

Bug description:
  lvm2 tools do not store by-path values in their config.
  That can drive scripts/tools (like the libvirt case here) mad.
  Simplified example:

  $ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
  $ sudo /sbin/pvs --noheadings -o pv_name,vg_name
/dev/vdc

  It is NOT using /dev/disk/by-path/virtio-pci-:00:07.0 as
  instructed, but instead did the mapping to /dev/vdd and keeps that
  from now on.

  I know that "inside" lvm all that is done via metadata and it won't matter.
  But tools around it get confused.
  Not sure yet if it is a real issue, or just "works as designed".

  
  --- started as libvirt issue - keeping old desc below ---

  I am trying to create a logical volume storage pool with persistent
  device names for the block devices, because I can't/don't want to ensure
  that /dev/sd* names are persistent through reboots.

  virsh # pool-define-as web2067 logical - -
  /dev/disk/by-path/pci-:18:00.0-scsi-0:2:2:0  web2067 /dev/web2067
  virsh # pool-build web2067

  These two steps work as expected and the pv and the vg get created, but
  when I try to start the pool I get the following error:

  virsh # pool-start web2067
  error: Failed to start pool web2067
  error: unsupported configuration: cannot find any matching source
  devices for logical volume group 'web2067'

  If I do the same steps just with /dev/sdX instead of
  /dev/disk/by-path/..., the pool gets created correctly.

  According to the libvirt mailing list /dev and /dev/disk/by-path are
  supposed to work the same way.

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

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

[Touch-packages] [Bug 1801918] Re: storage pool with persistent device names fails

[ Christian Ehrhardt ]

That is in fact a LVM limitation of the default config that is targetted
at low multi-scanning and general compatibility with older setups.

You'll find in /etc/lvm/lvm.conf a disabled line like:
# filter = [ "a|.*/|" ]

That means that it will consider /dev/* but not more - in particular not
/dev/disk/by-...

If you configure lvm to consider the paths you want (it will pick up the first 
it finds with metadata, so I made it ONLY by path)
  filter =[ "a|/dev/disk/by-path/.*|" ]

I wasn't sure what to reload, so I restarted all (might be too much)
$ sudo systemctl restart lvm2-lvmetad.service lvm2-monitor.service 
lvm2-lvmpolld.service

Now things work as you expected:
$ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
  Physical volume "/dev/disk/by-path/virtio-pci-:00:07.0" successfully 
created.
ubuntu@cosmic-storage-pools:~$ sudo pvdisplay 
  "/dev/disk/by-path/pci-:00:07.0" is a new physical volume of "30.00 MiB"
  --- NEW Physical volume ---
  PV Name   /dev/disk/by-path/pci-:00:07.0
  VG Name   
  PV Size   30.00 MiB
  Allocatable   NO
  PE Size   0   
  Total PE  0
  Free PE   0
  Allocated PE  0
  PV UUID   mwk7tq-fZ1C-zElW-u0Qy-KlqJ-PUK0-BVHOpz


That would fix things on the LVM side to be as libvirt expects.
Interestingly libvirt still can't start the pool now.

Haven't looked yet further, need to check what and how it parses in libvirt to 
get to the conclusion that it is not existing.
As now pvs looks like:
$ sudo /sbin/pvs --noheadings -o pv_name,vg_name
  /dev/disk/by-path/pci-:00:07.0 testpool1

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

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

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

Title:
  storage pool with persistent device names fails

Status in libvirt package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  Invalid

Bug description:
  lvm2 tools do not store by-path values in their config.
  That can drive scripts/tools (like the libvirt case here) mad.
  Simplified example:

  $ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
  $ sudo /sbin/pvs --noheadings -o pv_name,vg_name
/dev/vdc

  It is NOT using /dev/disk/by-path/virtio-pci-:00:07.0 as
  instructed, but instead did the mapping to /dev/vdd and keeps that
  from now on.

  I know that "inside" lvm all that is done via metadata and it won't matter.
  But tools around it get confused.
  Not sure yet if it is a real issue, or just "works as designed".

  
  --- started as libvirt issue - keeping old desc below ---

  I am trying to create a logical volume storage pool with persistent
  device names for the block devices, because I can't/don't want to ensure
  that /dev/sd* names are persistent through reboots.

  virsh # pool-define-as web2067 logical - -
  /dev/disk/by-path/pci-:18:00.0-scsi-0:2:2:0  web2067 /dev/web2067
  virsh # pool-build web2067

  These two steps work as expected and the pv and the vg get created, but
  when I try to start the pool I get the following error:

  virsh # pool-start web2067
  error: Failed to start pool web2067
  error: unsupported configuration: cannot find any matching source
  devices for logical volume group 'web2067'

  If I do the same steps just with /dev/sdX instead of
  /dev/disk/by-path/..., the pool gets created correctly.

  According to the libvirt mailing list /dev and /dev/disk/by-path are
  supposed to work the same way.

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

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

[Touch-packages] [Bug 1801918] Re: storage pool with persistent device names fails

[ Christian Ehrhardt ]

Error on starting the device:
  error : virStorageBackendLogicalMatchPoolSource:692 : unsupported 
configuration: cannot find any matching source devices for logical volume group 
'testpool1'

That error from the log matches the error in the UI of virsh.

The reason is that even thou it was defined by-path the lvm toolchain
has stored it as /dev/vdd and /dev/vdc

$ sudo /sbin/pvs --noheadings -o pv_name,vg_name
  /dev/vdc   testpool1
  /dev/vdd   testpool2

That is exactly the command it uses to build a list of existing VGs and then it 
looks for.
It finds the pool and then will check for the sources that are registered.

 666 /* If the pool has defined source device(s), then let's make sure  
  
 667  * they match as well; otherwise, matching can only occur on the   
  
 668  * pool's name.
  
 669  */
  
 670if (!def->source.ndevice) { 
  
 671 ret = true;
  
 672 goto cleanup;  
  
 673 }  
  
 674
  
 675 /* Let's make sure the pool's device(s) match what the pvs output has  
  
 676  * for volume group devices.   
  
 677  */
  
 678 for (i = 0; i < def->source.ndevice; i++) {
  
 679 for (j = 0; j < thisSource->ndevice; j++) {
  
 680 if (STREQ(def->source.devices[i].path, 
  
 681   thisSource->devices[j].path))
  
 682 matchcount++;  
  
 683 }  
  
 684 }  
  
 685
  
 686 /* If we didn't find any matches, then this pool has listed (a) source 
  
 687  * device path(s) that don't/doesn't match what was created for the 
pool 
 688  */
  
 689 if (matchcount == 0) { 

Since this will not match as above output has stored it as /dev/vdd it
cann't find it and will hit the issue described here.

Commands from the pool-build run:
 /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
 /sbin/vgcreate testpool1 /dev/disk/by-path/virtio-pci-:00:07.0

I cleared the vg/lv/pv configuration from my disks and did the same without any 
libvirt in play.
ubuntu@cosmic-storage-pools:~$ sudo /sbin/pvcreate 
/dev/disk/by-path/virtio-pci-:00:07.0
  Physical volume "/dev/disk/by-path/virtio-pci-:00:07.0" successfully 
created.
ubuntu@cosmic-storage-pools:~$ sudo /sbin/vgcreate testpool1 
/dev/disk/by-path/virtio-pci-:00:07.0
  Volume group "testpool1" successfully created
ubuntu@cosmic-storage-pools:~$ sudo vgdisplay 
  --- Volume group ---
  VG Name   testpool1
  System ID 
  Formatlvm2
  Metadata Areas1
  Metadata Sequence No  1
  VG Access read/write
  VG Status resizable
  MAX LV0
  Cur LV0
  Open LV   0
  Max PV0
  Cur PV1
  Act PV1
  VG Size   28.00 MiB
  PE Size   4.00 MiB
  Total PE  7
  Alloc PE / Size   0 / 0   
  Free  PE / Size   7 / 28.00 MiB
  VG UUID   0P3X39-nzR0-OtOP-3sts-W3oz-N5z6-tezzgA
   
ubuntu@cosmic-storage-pools:~$ sudo pvdisplay 
  --- Physical volume ---
  PV Name   /dev/vdc
  VG Name   testpool1
  PV Size   30.00 MiB / not usable 2.00 MiB
  Allocatable   yes 
  PE Size   4.00 MiB
  Total PE  7
  Free PE   7
  Allocated PE  0
  PV UUID   UstNOO-rYvf-9RDP-2Kfz-laI9-cMTr-5VSr16
   
ubuntu@cosmic-storage-pools:~$ sudo /sbin/pvs --noheadings -o pv_name,vg_name
  /dev/vdc   testpool1


As you can see already lvm tools do the remapping from by-path and store the 
current raw device path - there is not much libvirt can do about it.

We have to consider if it is an lvm2 issue thou - I'll re-tag the bug
here.

@Jan - could you add a link to the upstream Mailing list discussion you
referred please?

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

** Changed in: libvirt (Ubuntu)

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:7.6p1-4ubuntu0.1

---
openssh (1:7.6p1-4ubuntu0.1) bionic-security; urgency=medium

  [ Ryan Finnie ]
  * SECURITY UPDATE: OpenSSH User Enumeration Vulnerability (LP: #1794629)
- debian/patches/CVE-2018-15473.patch: delay bailout for invalid
  authenticating user until after the packet containing the request
  has been fully parsed.
- CVE-2018-15473

 -- leo.barb...@canonical.com (Leonidas S. Barbosa)  Mon, 05 Nov 2018
08:51:29 -0300

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  In Progress
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Cosmic:
  In Progress

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[Steven Maddox]

Have updated the patch to work with 18.04, here are the instructions I
just used to build it (personally I builds like this in a VM)...
ultimately you get the file 'network-manager-
gnome_1.8.10-2ubuntu1_amd64.deb' and that is the only thing you need to
install on normal 18.04 system where you want the fix...

sudo sed -i 's/^# \(deb-src \)/\1/' /etc/apt/sources.list
sudo apt-get update
sudo apt-get build-dep network-manager-applet
wget 
http://archive.ubuntu.com/ubuntu/pool/main/n/network-manager-applet/network-manager-applet_{1.8.10.orig,1.8.10-2ubuntu1.debian}.tar.xz
tar xf network-manager-applet_*.orig.tar.xz
cd network-manager-applet-*/
tar xf ../network-manager-applet_*.debian.tar.xz
wget -P debian/patches 
http://gist.github.com/Lantizia/2f32f0ca8193a61ceefb0c8c95e92bcc/raw/hide_unmanaged_interfaces.patch
sed -i '1s/^/hide_unmanaged_interfaces.patch\n/' debian/patches/series
sudo dpkg-buildpackage -b
# Ignore the bit about not being able to sign it
# Only need to install 'network-manager-gnome_1.8.10-2ubuntu1_amd64.deb'

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:7.2p2-4ubuntu2.6

---
openssh (1:7.2p2-4ubuntu2.6) xenial-security; urgency=medium

  [ Ryan Finnie ]
  * SECURITY UPDATE: OpenSSH User Enumeration Vulnerability (LP: #1794629)
- debian/patches/CVE-2018-15473.patch: delay bailout for invalid
  authenticating user until after the packet containing the request
  has been fully parsed.
- CVE-2018-15473
  * SECURITY UPDATE: Privsep process chrashing via an out-of-sequence
- debian/patches/CVE-2016-10708.patch: fix in kex.c,
  pack.c.
- CVE-2016-10708

 -- leo.barb...@canonical.com (Leonidas S. Barbosa)  Thu, 01 Nov 2018
16:16:02 -0300

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  In Progress
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  In Progress
Status in openssh source package in Cosmic:
  In Progress

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:6.6p1-2ubuntu2.11

---
openssh (1:6.6p1-2ubuntu2.11) trusty-security; urgency=medium

  * SECURITY UPDATE: OpenSSH User Enumeration Vulnerability (LP: #1794629)
- debian/patches/CVE-2018-15473.patch: delay bailout for invalid
  authenticating user until after the packet containing the request
  has been fully parsed.
- CVE-2018-15473
  [ Leonidas S. Barbosa ]
  * SECURITY UPDATE: Privsep process chrashing via an out-of-sequence
- debian/patches/CVE-2016-10708.patch: fix in kex.c,
  pack.c.
- CVE-2016-10708

 -- Ryan Finnie   Sat, 13 Oct 2018 23:31:08 +

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10708

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  In Progress
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  In Progress
Status in openssh source package in Cosmic:
  In Progress

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1801762] Re: Dual-signed things should be easy to verify with one key

[Francis Ginther]

** Tags added: id-5be079b42925080db15a8378

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

Title:
  Dual-signed things should be easy to verify with one key

Status in apt package in Ubuntu:
  New
Status in debmirror package in Ubuntu:
  New
Status in gnupg2 package in Ubuntu:
  New
Status in ubuntu-keyring package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  As part of Ubuntu key rotation strategy, we rely on dual-signing
  (inline, or detached) such that validation with at least one key
  available in a keyring should be trusted, without using web-of-trust.

  However, it seems to be only correctly so far implemented by the apt's
  gpgv method.

  Ideally, we should ship an easy enough to use the helper that is `like
  gpgv` to use, and possibly reusing apt's gpgv code and/or exposing it
  via apt-key's verify.

  The problem seems to be that 1 good sig + 1 no public key available,
  results in gpgv exiting with 2, instead of 0 or 1.

  Ideally it should be easy enough to use gpgv/gpg to verify that at
  least one signature is good, and decrypt/extract signed contents only.

  More details and reproducers to follow.

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

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

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

[Eric Desrochers]

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

** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: init-system-helpers (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: unattended-upgrades (Ubuntu Xenial)
 Assignee: (unassigned) => Balint Reczey (rbalint)

-- 
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:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  New
Status in init-system-helpers source package in Xenial:
  New
Status in snapd source package in Xenial:
  New
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  New
Status in init-system-helpers source package in Bionic:
  New
Status in snapd source package in Bionic:
  New
Status in unattended-upgrades source package in Bionic:
  In Progress

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 regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  

[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

[Eric Desrochers]

** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: unattended-upgrades (Ubuntu Xenial)
 Assignee: (unassigned) => Balint Reczey (rbalint)

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in unattended-upgrades source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in unattended-upgrades source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

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

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

[Eric Desrochers]

** Changed in: unattended-upgrades (Ubuntu Bionic)
 Assignee: Eric Desrochers (slashd) => (unassigned)

** Changed in: unattended-upgrades (Ubuntu Bionic)
 Assignee: (unassigned) => Balint Reczey (rbalint)

-- 
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:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in init-system-helpers source package in Bionic:
  New
Status in snapd source package in Bionic:
  New
Status in unattended-upgrades source package in Bionic:
  In Progress

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 regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The upgrade on shutdown hangs when configuring the apport package.
  The hanging command is "systemctl stop apport-forward.socket". The
  system hangs until the systemd ShutdownTimeout expires and systemd
  

[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

[Eric Desrochers]

** Changed in: unattended-upgrades (Ubuntu Bionic)
 Assignee: Eric Desrochers (slashd) => (unassigned)

** Changed in: unattended-upgrades (Ubuntu Bionic)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in unattended-upgrades source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in unattended-upgrades source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: systemd-networkd not renaming devices on boot

[Marcos]

@Nicorac: Tested with static IP and had same result.

ubuntu@ubuntu:~$ cat /etc/netplan/01-netcfg.yaml 
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
eth0:
  match:
  macaddress: 08:00:27:f0:97:15
  set-name: eth0
  dhcp4: no
  addresses: [ "192.168.56.2/24" ]
  gateway4: 192.168.56.1

ubuntu@ubuntu:~$ ip address show
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
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether 08:00:27:f0:97:15 brd ff:ff:ff:ff:ff:ff

-- 
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
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run 

[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

[Eric Desrochers]

In fact more fixes are needed due to regression in the fix above the fixes are 
found here :
https://github.com/mvo5/unattended-upgrades/pull/148

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in unattended-upgrades source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in unattended-upgrades source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

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

[Touch-packages] [Bug 1801921] [NEW] /usr/bin/unattended-upgrade:ValueError:/usr/bin/unattended-upgrade@2005:main:get_allowed_origins:get_allowed_origins_legacy

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.6, the problem page at 
https://errors.ubuntu.com/problem/dedbe4a7a8dab2471082fa3cd73fc2d0dea1b6b5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 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/1801921

Title:
  /usr/bin/unattended-upgrade:ValueError:/usr/bin/unattended-
  upgrade@2005:main:get_allowed_origins:get_allowed_origins_legacy

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.6, the problem page at 
https://errors.ubuntu.com/problem/dedbe4a7a8dab2471082fa3cd73fc2d0dea1b6b5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1797224] Re: Stay on 2.0 for cosmic, update next cycle

[Sebastien Bacher]

** Tags removed: version-blocked-ff

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

Title:
  Stay on 2.0 for cosmic, update next cycle

Status in tracker package in Ubuntu:
  Triaged

Bug description:
  The new version requires the MIR situation to be sorted out

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

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

[Touch-packages] [Bug 1801910] [NEW] logrotate fails on LXC

[Marco Bertorello]

Public bug reported:

daily, I receive this alert from logrotate script in cron.daily:

/etc/cron.daily/logrotate:
Failed to kill unit rsyslog.service: Input/output error
error: error running non-shared postrotate script for /var/log/syslog of 
'/var/log/syslog
'
run-parts: /etc/cron.daily/logrotate exited with return code 1

My ubuntu is a LXC running on top of ProxmoxVE.

the problem occour when logrotate script call /usr/lib/rsyslog/rsyslog-
rotate that has this call:

systemctl kill -s HUP rsyslog.service

I already checked my disks status (because the input/output error) but
them are ok.

The same issue is present also in another LXC, ubuntu also this one,
running on another node of the same cluster

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: logrotate 3.11.0-0.1ubuntu1
ProcVersionSignature:
 
Uname: Linux 4.15.18-7-pve x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Tue Nov  6 10:26:37 2018
ProcEnviron:
 LANG=C
 SHELL=/bin/bash
 TERM=xterm
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  logrotate fails on LXC

Status in logrotate package in Ubuntu:
  New

Bug description:
  daily, I receive this alert from logrotate script in cron.daily:

  /etc/cron.daily/logrotate:
  Failed to kill unit rsyslog.service: Input/output error
  error: error running non-shared postrotate script for /var/log/syslog of 
'/var/log/syslog
  '
  run-parts: /etc/cron.daily/logrotate exited with return code 1

  My ubuntu is a LXC running on top of ProxmoxVE.

  the problem occour when logrotate script call /usr/lib/rsyslog
  /rsyslog-rotate that has this call:

  systemctl kill -s HUP rsyslog.service

  I already checked my disks status (because the input/output error) but
  them are ok.

  The same issue is present also in another LXC, ubuntu also this one,
  running on another node of the same cluster

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: logrotate 3.11.0-0.1ubuntu1
  ProcVersionSignature:
   
  Uname: Linux 4.15.18-7-pve x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Tue Nov  6 10:26:37 2018
  ProcEnviron:
   LANG=C
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1801898] Re: Only one of two external (displayport) displays is working without hotplug

[Andreas Vinsander]

I am not using wayland.

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

Title:
  Only one of two external (displayport) displays is working without
  hotplug

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in my one of 
my two external displays will not be activated without hotplugging the other 
external display.
  The display settings app shows the second display as inactive, and when 
trying to activate the settings app states that some hardware limitation stops 
it from being possible to apply the change.
  The laptop lid is closed, the internal laptop display is not active.

  Hotplugging the other external display solves the problem - after
  hotplug both external displays are active. This makes the bug annoying
  but workaroundable.

  I am not sure if this bug belongs to the Xorg package or the linux
  package.

  Hardware:
  Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two 
external displays connected through displayport (via docking station).

  $ sudo lspci -v
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 6000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu8
Candidate: 1:7.7+19ubuntu8
Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy linux-image-4.18.0-10-generic
  linux-image-4.18.0-10-generic:
Installed: 4.18.0-10.11
Candidate: 4.18.0-10.11
Version table:
   *** 4.18.0-10.11 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

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

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

[Balint Reczey]

@slashd (and all) the fix caused regressions elsewhere and it is being
partially reverted and the issue is fixed in a different way. Please
don't backport the current fix.

The candidate for fixing the issue without the regressions introduced: 
https://github.com/mvo5/unattended-upgrades/pull/148

-- 
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:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in init-system-helpers source package in Bionic:
  New
Status in snapd source package in Bionic:
  New
Status in unattended-upgrades source package in Bionic:
  In Progress

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 regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The upgrade on shutdown hangs when configuring the apport package.
  The hanging command is "systemctl stop apport-forward.socket". 

[Touch-packages] [Bug 1797064] Re: Update to 2.9.8

[Sebastien Bacher]

** Summary changed:

- Update to 2.9.8 next cycle
+ Update to 2.9.8

** Tags removed: version-blocked-ff

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

Title:
  Update to 2.9.8

Status in libxml2 package in Ubuntu:
  Triaged

Bug description:
  The new version is in Debian experimental but it's late to update on
  Ubuntu this cycle, especially with a non trivial update on a component
  like that, the update is for next cycle

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

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

[Touch-packages] [Bug 1796717] Re: Update to 0.69.0

[Sebastien Bacher]

** Summary changed:

- Update to 0.69.0 next cycle
+ Update to 0.69.0

** Tags removed: version-blocked-ff

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

Title:
  Update to 0.69.0

Status in poppler package in Ubuntu:
  Triaged

Bug description:
  The new version has new features and poppler updates require
  transition due to soname changes, that's for next cycle

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

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

[Touch-packages] [Bug 1789502] Re: Update to 0.6.50

[Sebastien Bacher]

The disco cycle is starting so that's unblocked now

** Tags removed: version-blocked-ff

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

Title:
  Update to 0.6.50

Status in accountsservice package in Ubuntu:
  In Progress

Bug description:
  The upstream changes are non trivial and there is work to update the
  patches but that would be useful to do

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

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

[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Aravind R]

I dont know how Daemo00 manage to start

sudo systemctl start whoopsie.service

shows noting

and when I run service apport-autoreport status. It shows same error:


● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2018-11-06 15:36:56 IST; 35min 
ago
  Process: 1491 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, 
status=1/FAILURE)
 Main PID: 1491 (code=exited, status=1/FAILURE)

Nov 06 15:36:52 comp systemd[1]: Starting Process error reports when automatic 
reporting is enabled...
Nov 06 15:36:56 comp whoopsie-upload-all[1491]: ERROR: whoopsie is not running
Nov 06 15:36:56 comp systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=1/FAILURE
Nov 06 15:36:56 comp systemd[1]: apport-autoreport.service: Failed with result 
'exit-code'.
Nov 06 15:36:56 comp systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1797222] Re: Update to 2.13.1 on next cycle

[Sebastien Bacher]

The disco cycle is starting so that's unblocked now

** Tags removed: version-blocked-ff

** Summary changed:

- Update to 2.13.1 on next cycle
+ Update to 2.13.1

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

Title:
  Update to 2.13.1

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Updating is not risk free and there is no reason to do that now,
  that's for next cycle

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

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

[Touch-packages] [Bug 1797059] Re: Update to 1.9.0

[Sebastien Bacher]

** Summary changed:

- Update to 1.9.0 next cycle
+ Update to 1.9.0

** Tags removed: version-blocked-ff

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

Title:
  Update to 1.9.0

Status in harfbuzz package in Ubuntu:
  Triaged

Bug description:
  The new version has changes that are not trivial, let's delay to next
  cycle

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

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

[Touch-packages] [Bug 1797063] Re: Update to 130 next cycle

[Sebastien Bacher]

The disco cycle is starting so that's unblocked now

** Tags removed: version-blocked-ff

** Summary changed:

- Update to 130 next cycle
+ Update to 130

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

Title:
  Update to 130

Status in cron package in Ubuntu:
  Triaged

Bug description:
  The new version is in Debian but the changes are not trivial enough to
  update in cosmic, that's for next cycle

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

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

[Touch-packages] [Bug 1801898] [NEW] Only one of two external (displayport) displays is working without hotplug

[Andreas Vinsander]

Public bug reported:

After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in my one of my 
two external displays will not be activated without hotplugging the other 
external display.
The display settings app shows the second display as inactive, and when trying 
to activate the settings app states that some hardware limitation stops it from 
being possible to apply the change.
The laptop lid is closed, the internal laptop display is not active.

Hotplugging the other external display solves the problem - after
hotplug both external displays are active. This makes the bug annoying
but workaroundable.

I am not sure if this bug belongs to the Xorg package or the linux
package.

Hardware:
Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two 
external displays connected through displayport (via docking station).

$ sudo lspci -v
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 6000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu8
  Candidate: 1:7.7+19ubuntu8
  Version table:
 *** 1:7.7+19ubuntu8 500
500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy linux-image-4.18.0-10-generic
linux-image-4.18.0-10-generic:
  Installed: 4.18.0-10.11
  Candidate: 4.18.0-10.11
  Version table:
 *** 4.18.0-10.11 500
500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10

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

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

Title:
  Only one of two external (displayport) displays is working without
  hotplug

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in my one of 
my two external displays will not be activated without hotplugging the other 
external display.
  The display settings app shows the second display as inactive, and when 
trying to activate the settings app states that some hardware limitation stops 
it from being possible to apply the change.
  The laptop lid is closed, the internal laptop display is not active.

  Hotplugging the other external display solves the problem - after
  hotplug both external displays are active. This makes the bug annoying
  but workaroundable.

  I am not sure if this bug belongs to the Xorg package or the linux
  package.

  Hardware:
  Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two 
external displays connected through displayport (via docking station).

  $ sudo lspci -v
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 6000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu8
Candidate: 1:7.7+19ubuntu8
Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy linux-image-4.18.0-10-generic
  linux-image-4.18.0-10-generic:
Installed: 4.18.0-10.11
Candidate: 4.18.0-10.11
Version table:
   *** 4.18.0-10.11 500
  500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

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

[Touch-packages] [Bug 1770271] Re: VegaM support

[Timo Aaltonen]

I think we'll just fix this in bionic via the HWE stack update. Backport
to xenial would basically mean updating stock bionic kernel/mesa and
then backport those to xenial. A big patchset to the kernel is unlikely
to get approved..

** Changed in: linux (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: mesa (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

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

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

[Touch-packages] [Bug 1777994] Re: the header xcb/xinput.h is missing

[Timo Aaltonen]

I don't need this in bionic, so dropping from my TODO

** Changed in: libxcb (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: libxcb (Ubuntu Bionic)
 Assignee: Timo Aaltonen (tjaalton) => (unassigned)

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

Title:
  the header xcb/xinput.h is missing

Status in libxcb package in Ubuntu:
  Fix Released
Status in libxcb source package in Bionic:
  Won't Fix

Bug description:
  I suspect this means there should be another package, libxcb-xinput-
  dev perhaps?

  I already did sudo apt install "libxcb*dev" to get all related dev
  packages, but none of them provide xcb/xinput.h.

  The result is that when building Qt from source, it's necessary to use
  a copy of this file which Qt provides
  (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing
  from the system.  So if you don't give the option -qt-xcb to
  configure, then Qt will be built without multi-touch support.

  https://bugreports.qt.io/browse/QTBUG-69045

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libxcb1-dev 1.13-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 08:32:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3802]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: libxcb
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  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: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  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.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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/libxcb/+bug/1777994/+subscriptions

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

[Timo Aaltonen]

** Changed in: xorg-server (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
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:
  New
Status in llvm-toolchain-7 source package in Bionic:
  New
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 1801891] [NEW] apt update blocked/locked, processes hung for days due to avahi-browse

[TJ]

Public bug reported:

Using 18.04 I hit a problem:

$ sudo apt -o=Debug::Acquire::gpgv=true update

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

Reading package lists...
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily 
unavailable)
E: Unable to lock directory /var/lib/apt/lists/


Investigating further I discovered a 3 day old cron job is hung:

$ date
Tue  6 Nov 08:50:20 GMT 2018

$ ps -efly | grep apt
S tj   31068  8492  0  80   0  1016  5384 pipe_w 08:48 pts/400:00:00 
grep --color=auto apt
S root 31280 1  0  80   0   860  1157 -  Nov03 ?00:00:00 
/bin/sh /usr/lib/apt/apt.systemd.daily update
S root 31285 31280  0  80   0  1748  1157 -  Nov03 ?00:00:00 
/bin/sh /usr/lib/apt/apt.systemd.daily lock_is_held update
S root 31331 31285  0  80   0  8080 15493 -  Nov03 ?00:00:00 
apt-get -qq -y update
S root 31336 31331  0  80   0  5556 19025 -  Nov03 ?00:00:00 
/usr/lib/apt/methods/http
S root 32312 31331  0  80   0  5636 19025 -  Nov03 ?00:00:00 
/usr/lib/apt/methods/http
S _apt 32314 31331  0  80   0  9548 10752 -  Nov03 ?00:00:00 
/usr/bin/python /usr/share/squid-deb-proxy-client/apt-avahi-discover 
http://apt.postgresql.org/pub/repos/apt/dists/bionic-pgdg/InRelease
S _apt 32315 32314  0  80   0  1536 10458 -  Nov03 ?00:00:00 
avahi-browse -kprtf _apt_proxy._tcp

I've successfully installed packages using "apt install" since the date
these update processes started.

Checking the mDNS proxy command manually it returns with no result:

$ avahi-browse -kprtf _apt_proxy._tcp
$

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

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

Title:
  apt update blocked/locked, processes hung for days due to avahi-browse

Status in apt package in Ubuntu:
  New

Bug description:
  Using 18.04 I hit a problem:

  $ sudo apt -o=Debug::Acquire::gpgv=true update

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  Reading package lists...
  E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource 
temporarily unavailable)
  E: Unable to lock directory /var/lib/apt/lists/

  
  Investigating further I discovered a 3 day old cron job is hung:

  $ date
  Tue  6 Nov 08:50:20 GMT 2018

  $ ps -efly | grep apt
  S tj   31068  8492  0  80   0  1016  5384 pipe_w 08:48 pts/400:00:00 
grep --color=auto apt
  S root 31280 1  0  80   0   860  1157 -  Nov03 ?00:00:00 
/bin/sh /usr/lib/apt/apt.systemd.daily update
  S root 31285 31280  0  80   0  1748  1157 -  Nov03 ?00:00:00 
/bin/sh /usr/lib/apt/apt.systemd.daily lock_is_held update
  S root 31331 31285  0  80   0  8080 15493 -  Nov03 ?00:00:00 
apt-get -qq -y update
  S root 31336 31331  0  80   0  5556 19025 -  Nov03 ?00:00:00 
/usr/lib/apt/methods/http
  S root 32312 31331  0  80   0  5636 19025 -  Nov03 ?00:00:00 
/usr/lib/apt/methods/http
  S _apt 32314 31331  0  80   0  9548 10752 -  Nov03 ?00:00:00 
/usr/bin/python /usr/share/squid-deb-proxy-client/apt-avahi-discover 
http://apt.postgresql.org/pub/repos/apt/dists/bionic-pgdg/InRelease
  S _apt 32315 32314  0  80   0  1536 10458 -  Nov03 ?00:00:00 
avahi-browse -kprtf _apt_proxy._tcp

  I've successfully installed packages using "apt install" since the
  date these update processes started.

  Checking the mDNS proxy command manually it returns with no result:

  $ avahi-browse -kprtf _apt_proxy._tcp
  $

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

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

[Touch-packages] [Bug 1801805] Re: pdf printer provided by cups-pdf has disappeared since update to 18.04

[Till Kamppeter]

** Package changed: cups (Ubuntu) => cups-pdf (Ubuntu)

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

Title:
  pdf printer provided by cups-pdf has disappeared since update to 18.04

Status in cups-pdf package in Ubuntu:
  New

Bug description:
  Since the update from Ubuntu 16.n to Ubuntu 18.04 the PDF printer
  functionality provided by cups-pdf has disappeared (on several
  machines). The "printer" just disappeared from the list of available
  printers. In all cases the functionality worked properly before. It is
  possible to install or re-install the cups-pdf via "apt-get install"
  and it does run the install. However, the "printer" remains
  unavailable, no trace. There is no error message visible of whatever
  kind. Printing from applications using Cups-PDF-printer is no longer
  possible because there is no Cups-PDF printer no more. Same bug
  applies to 18.10, too. Please advise how to get back the PDF printer
  functionality in 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cups 2.2.8-5ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  5 23:12:26 2018
  InstallationDate: Installed on 2016-09-02 (793 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  KernLog:
   [  871.633929] audit: type=1400 audit(1541455672.543:64): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/mission-control-5" 
name="/usr/local/lib/libgcrypt.so.20.1.3" pid=6089 comm="mission-control" 
requested_mask="r" denied_mask="r" fsuid=1002 ouid=0
   [  871.634375] audit: type=1400 audit(1541455672.543:65): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/mission-control-5" 
name="/usr/local/lib/libgpg-error.so.0.20.0" pid=6089 comm="mission-control" 
requested_mask="r" denied_mask="r" fsuid=1002 ouid=0
  Lpstat:
   device for DESKJET-990C-2: hp:/usb/DeskJet_990C?serial=ES0B81C11DLG
   device for Hewlett-Packard-HP-LaserJet-MFP-M725: 
hp:/net/HP_LaserJet_MFP_M725?zc=NPI02EAAF
   device for HP-LaserJet-5: socket://192.168.22.65:9100
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b563 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A556/G
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DESKJET-990C-2.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-MFP-M725.ppd', 
'/etc/cups/ppd/HP-LaserJet-5.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DESKJET-990C-2.ppd: Permission denied
   grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-MFP-M725.ppd: Permission 
denied
   grep: /etc/cups/ppd/HP-LaserJet-5.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic 
root=UUID=1f7b9a32-c877-4663-b036-c761cde32cfd ro plymouth:debug drm.debug=0xe
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2016
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB47
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: LIFEBOOK A556/G
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.18:bd09/22/2016:svnFUJITSU:pnLIFEBOOKA556/G:pvr:rvnFUJITSU:rnFJNBB47:rvr:cvnFUJITSU:ct10:cvrLIFEBOOKA556/G:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A556/G
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1801762] Re: Dual-signed things should be easy to verify with one key

[Julian Andres Klode]

That wrapper is conceptually wrong. It should be using --status-fd.

I'm in favour of not duplicating that stuff and see if we can reuse the
existing apt code, by moving it into the library and providing a tool in
apt-helper.

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

Title:
  Dual-signed things should be easy to verify with one key

Status in apt package in Ubuntu:
  New
Status in debmirror package in Ubuntu:
  New
Status in gnupg2 package in Ubuntu:
  New
Status in ubuntu-keyring package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  As part of Ubuntu key rotation strategy, we rely on dual-signing
  (inline, or detached) such that validation with at least one key
  available in a keyring should be trusted, without using web-of-trust.

  However, it seems to be only correctly so far implemented by the apt's
  gpgv method.

  Ideally, we should ship an easy enough to use the helper that is `like
  gpgv` to use, and possibly reusing apt's gpgv code and/or exposing it
  via apt-key's verify.

  The problem seems to be that 1 good sig + 1 no public key available,
  results in gpgv exiting with 2, instead of 0 or 1.

  Ideally it should be easy enough to use gpgv/gpg to verify that at
  least one signature is good, and decrypt/extract signed contents only.

  More details and reproducers to follow.

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

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

[Touch-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

[Daniel van Vugt]

Also, this is a SIGSEGV...

 OsSigHandler (signo=11

** Summary changed:

- Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() from 
_mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
+ Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from 
_mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

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

Title:
  Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
  _mesa_reference_renderbuffer_() [often when running Skype or Slack
  snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
  https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1