[Touch-packages] [Bug 1881241] [NEW] My HP laserjet 1018 stopped printing from Ubuntu 18.04

2020-05-28 Thread gwyn thomas
Public bug reported:

I originally installed 16.04 on my newly acquired Dell Studio 2 months
ago.  I then installed my HP Laserjet 1018 and it ran well.  I upgraded
to 18.04 and the printer continued to work well until this morning when
it decided not to work.  I have checked the cables which all work.  I do
have an HP 6300 connected and it works when the same cable is plugged
into it.  The 1018 printer is switched on. I did switch 1018 on and off
and it resets.  I even ran a test page on the printer but cannot print
test page from laptop.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.8
ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
Uname: Linux 4.15.0-101-generic i686
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: i386
CurrentDesktop: ubuntu:GNOME
Date: Fri May 29 07:17:56 2020
InstallationDate: Installed on 2020-03-16 (73 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
Lpstat:
 device for hplaserjet: hp:/usb/HP_LaserJet_1018?serial=KP1E25R
 device for Officejet-6300-series: 
hp:/usb/Officejet_6300_series?serial=CN87AFV0DG04M4
 device for Officejet-6300-series-Fax: 
hpfax:/usb/Officejet_6300_series?serial=CN87AFV0DG04M4
MachineType: Dell Inc. Studio 1555
Papersize: a4
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Officejet-6300-series-Fax.ppd', '/etc/cups/ppd/hplaserjet.ppd', 
'/etc/cups/ppd/Officejet-6300-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Officejet-6300-series-Fax.ppd: Permission denied
 grep: /etc/cups/ppd/hplaserjet.ppd: Permission denied
 grep: /etc/cups/ppd/Officejet-6300-series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=631b51e9-3538-4ead-a72b-e2f2a3e59676 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/03/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0C234M
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A07
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd07/03/2009:svnDellInc.:pnStudio1555:pvrA07:rvnDellInc.:rn0C234M:rvrA07:cvnDellInc.:ct8:cvrA07:
dmi.product.name: Studio 1555
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

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


** Tags: apparmor apport-bug bionic i386

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

Title:
  My HP laserjet 1018 stopped printing from Ubuntu 18.04

Status in cups package in Ubuntu:
  New

Bug description:
  I originally installed 16.04 on my newly acquired Dell Studio 2 months
  ago.  I then installed my HP Laserjet 1018 and it ran well.  I
  upgraded to 18.04 and the printer continued to work well until this
  morning when it decided not to work.  I have checked the cables which
  all work.  I do have an HP 6300 connected and it works when the same
  cable is plugged into it.  The 1018 printer is switched on. I did
  switch 1018 on and off and it resets.  I even ran a test page on the
  printer but cannot print test page from laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.8
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic i686
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 07:17:56 2020
  InstallationDate: Installed on 2020-03-16 (73 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  Lpstat:
   device for hplaserjet: hp:/usb/HP_LaserJet_1018?serial=KP1E25R
   device for Officejet-6300-series: 
hp:/usb/Officejet_6300_series?serial=CN87AFV0DG04M4
   device for Officejet-6300-series-Fax: 
hpfax:/usb/Officejet_6300_series?serial=CN87AFV0DG04M4
  MachineType: Dell Inc. Studio 1555
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Officejet-6300-series-Fax.ppd', '/etc/cups/ppd/hplaserjet.ppd', 
'/etc/cups/ppd/Officejet-6300-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Officejet-6300-series-Fax.ppd: Permission denied
   grep: /etc/cups/ppd/hplaserjet.ppd: Permission denied
   grep: /etc/cups/ppd/Officejet-6300-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=631b51e9-3538-4ead-a72b-e2f2a3e59676 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0C234M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 

[Touch-packages] [Bug 1880768] Re: usermod/userdel errantly believe user has running processes

2020-05-28 Thread Kevin Blackham
** Summary changed:

- usermod/userdel errantly believe processes are in use
+ usermod/userdel errantly believe user has running processes

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

Title:
  usermod/userdel errantly believe user has running processes

Status in shadow package in Ubuntu:
  New

Bug description:
  I have found an occasional inability to remove or modify users due to
  incorrect matching of process owners, e.g.

  # id -u bdobbs
  1047
  # usermod -u 1573552 bdobbs
  usermod: user bdobbs is currently used by process 6337
  # cat /proc/6337/status | grep Uid
  Uid:  3000400 3000400 3000400 3000400

  In `libmisc/user_busy.c` a check is performed for processes owned by a
  user which is being modified. Searching subordinate user IDs causes
  errant matches. This has been fixed upstream, and is included in
  passwd-4.8 and the issue does not appear to exist in groovy.

  https://github.com/shadow-
  maint/shadow/commit/fd4405b763d26649339069532e79bd45013c8c38 I believe
  this fix should be backported to xenial and bionic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: passwd 1:4.2-3.1ubuntu5.4
  ProcVersionSignature: Ubuntu 4.4.0-1107.118-aws 4.4.219
  Uname: Linux 4.4.0-1107-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  Date: Tue May 26 22:18:00 2020
  Ec2AMI: ami-4e79ed36
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.passwd: [deleted]

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

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


[Touch-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

2020-05-28 Thread Timo Aaltonen
** Also affects: oem-priority/bionic
   Importance: Undecided
   Status: New

** No longer affects: oem-priority/bionic

** Also affects: oem-priority/bionic
   Importance: Undecided
   Status: New

** No longer affects: oem-priority/bionic

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

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

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

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  New

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
     $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4
     $ sudo apt-get update
     $ sudo apt install linux-header-5.4.0-31-generic
     $ sudo apt install linux-image-generic-hwe-18.04-wip
     $ sudo reboot

   * install updated linux-firmware and pulseaudio
 $ sudo add-apt-repository ppa:kchsieh/training
 $ sudo apt-get update
 $ sudo apt install linux-firmware
 $ sudo apt install pulseaudio
 $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions

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


[Touch-packages] [Bug 1584716] Re: Text corruption in various Gnome apps since Xenial upgrade

2020-05-28 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Text corruption in various Gnome apps since Xenial upgrade

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Since the Ubuntu Xenial upgrade, I've had various instances of text
  corruption. I use a gnome-shell session. I (think) see this only if
  the laptop has suspended and restored.

  I'm using the intel graphics driver from ppa:oibaf/graphics-drivers
  (in a failed attempt to try and upgrade myself out of the issue), but
  it was happening before changing to a custom PPA.

  This affects such a wide array of parts of the desktop that I suspect
  it's likely to be a basic X11 driver or GTK-level bug.

  Screenshots attached.

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

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


[Touch-packages] [Bug 1881226] Re: package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

2020-05-28 Thread 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1881226

Title:
  package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed
  udev package post-installation script subprocess returned error exit
  status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
  Uname: Linux 5.3.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Thu May 28 21:49:38 2020
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2019-02-09 (474 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Shuttle Inc. DS81D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-55-generic 
root=UUID=ea9922c0-ef41-4846-8661-d5e00af2a309 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed 
udev package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-29 (0 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.14
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FS81
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  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.:bvr3.14:bd09/17/2018:svnShuttleInc.:pnDS81D:pvrV1.0:rvnShuttleInc.:rnFS81:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: R
  dmi.product.name: DS81D
  dmi.product.sku: 1.0
  dmi.product.version: V1.0
  dmi.sys.vendor: Shuttle Inc.

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

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


[Touch-packages] [Bug 1881226] [NEW] package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

2020-05-28 Thread Jeff Tostenrude
Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: udev 245.4-4ubuntu3.1
ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
Uname: Linux 5.3.0-55-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CustomUdevRuleFiles: 70-snap.core.rules
Date: Thu May 28 21:49:38 2020
ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2019-02-09 (474 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Shuttle Inc. DS81D
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-55-generic 
root=UUID=ea9922c0-ef41-4846-8661-d5e00af2a309 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: systemd
Title: package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-05-29 (0 days ago)
dmi.bios.date: 09/17/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.14
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FS81
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
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.:bvr3.14:bd09/17/2018:svnShuttleInc.:pnDS81D:pvrV1.0:rvnShuttleInc.:rnFS81:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: R
dmi.product.name: DS81D
dmi.product.sku: 1.0
dmi.product.version: V1.0
dmi.sys.vendor: Shuttle Inc.

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


** Tags: amd64 apport-package focal

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

Title:
  package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed
  udev package post-installation script subprocess returned error exit
  status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
  Uname: Linux 5.3.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Thu May 28 21:49:38 2020
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2019-02-09 (474 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Shuttle Inc. DS81D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-55-generic 
root=UUID=ea9922c0-ef41-4846-8661-d5e00af2a309 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed 
udev package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-29 (0 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.14
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FS81
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  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.:bvr3.14:bd09/17/2018:svnShuttleInc.:pnDS81D:pvrV1.0:rvnShuttleInc.:rnFS81:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: R
  dmi.product.name: DS81D
  dmi.product.sku: 1.0
  dmi.product.version: V1.0
  dmi.sys.vendor: Shuttle Inc.

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

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


[Touch-packages] [Bug 1881212] Re: Blank Screen initiates then fails

2020-05-28 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

** Changed in: 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/1881212

Title:
  Blank Screen initiates then fails

Status in Ubuntu:
  Incomplete

Bug description:
  Blank Screen initiates after timeout (usually 5 minutes but set to 1
  minute to replicate this bug), screen goes blank on both laptop and
  external Dell, but immediately comes back on. Whilst it is blanking,
  any running applications show their windows (which is not usual) but
  it appears gnome-shell and the window manager are not running (no dash
  and no window decorations).

  Disconnecting external monitor exhibits the same Blank Screen failure
  on the laptop screen.

  I have turned Automatic Screen Lock off for now to remove that as a
  cause.

  I have also had intermittent failure of gnome-shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 09:07:11 2020
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.12.3, 5.4.0-31-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.4.0-33-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2020-02-25 (93 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFCTO1WW
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-01 (27 days ago)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET47W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFCTO1WW:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFCTO1WW
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1881212] Re: Blank Screen initiates then fails

2020-05-28 Thread Daniel van Vugt
Thanks for the bug report. This sounds like gnome-shell has crashed and
is being restarted:

> Whilst it is blanking, any running applications show their windows
(which is not usual) but it appears gnome-shell and the window manager
are not running (no dash and no window decorations).

When gnome-shell crashes the apps are still running on the bare Xorg
server so it looks different.

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

Title:
  Blank Screen initiates then fails

Status in Ubuntu:
  Incomplete

Bug description:
  Blank Screen initiates after timeout (usually 5 minutes but set to 1
  minute to replicate this bug), screen goes blank on both laptop and
  external Dell, but immediately comes back on. Whilst it is blanking,
  any running applications show their windows (which is not usual) but
  it appears gnome-shell and the window manager are not running (no dash
  and no window decorations).

  Disconnecting external monitor exhibits the same Blank Screen failure
  on the laptop screen.

  I have turned Automatic Screen Lock off for now to remove that as a
  cause.

  I have also had intermittent failure of gnome-shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 09:07:11 2020
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.12.3, 5.4.0-31-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.4.0-33-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2020-02-25 (93 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFCTO1WW
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-01 (27 days ago)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET47W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFCTO1WW:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFCTO1WW
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1881199] Re: [SoundCore mini, playback] No sound at all from Rhythmbox

2020-05-28 Thread Daniel van Vugt
Please try:

  cd ~/.config
  rm -rf pulse

and the log out and in again.

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

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

Title:
  [SoundCore mini, playback] No sound at all from Rhythmbox

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After connecting via bluetooth the Soundcore Mini, I can get sound to
  play through it just fine from e.g. the Chromium browser, but not from
  Rhythmbox, which instead always plays from the laptop's internal
  speakrs.

  In the bluetooth settings, Soundcore Mini is connected. In the sound
  settings, Soundcore Mini is selected, and the "Test" button opens an
  UI that lets me play test sounds, and it works. And indeed it works
  for e.g. Google Chrome for a youtube video. But Rhythmbox plays
  through the internal speakers no matter what. I've tried restarting
  Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings
  and then running "pulseaudio -k", and then restarting Rhythmbox, to no
  avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert120462 F pulseaudio
   /dev/snd/pcmC0D0c:   albert120462 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 28 22:00:38 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-24 (1434 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SoundCore mini
  Symptom_DevicesInUse:
   Cannot stat file /proc/43906/fd/6: Permission denied
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert120462 F pulseaudio
   /dev/snd/pcmC0D0c:   albert120462 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [SoundCore mini, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FQCTO1WW
  dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-05-28 Thread Daniel van Vugt
** Summary changed:

- disk check progress no longer visible
+ Ctrl-C message displayed without any actual disk check

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

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in plymouth source package in Focal:
  New
Status in systemd source package in Focal:
  New
Status in plymouth source package in Groovy:
  New
Status in systemd source package in Groovy:
  New

Bug description:
  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

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

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


[Touch-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work

2020-05-28 Thread Jordan Liu
** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  System hangs at reboot or poweroff. kworker blocked at dp_altmode_work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expected:
  System reboots/powers off.

  Actual:
  System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing 
escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. 
  ```
  May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down.
  May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and 
block devices.
  May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to 
remaining processes...
  May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped
  ```
  Letting the computer continue to idle, an error message shows up. I've 
attached a picture because the error message does not show up in any logs. 

  Possibly a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though
  the other user did not mention the same symptoms.

  Description:Ubuntu 20.04 LTS
  Release:20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu May 28 16:53:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
  InstallationDate: Installed on 2020-05-22 (6 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20QVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET44W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme Gen2
  dmi.product.name: 20QVCTO1WW
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2
  dmi.product.version: ThinkPad X1 Extreme Gen2
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver

2020-05-28 Thread Daniel van Vugt
** Tags added: bionic

** Summary changed:

- Support kernel 5.4 Intel sound driver
+ Support kernel 5.4 Intel sound driver on bionic

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

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
     $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4
     $ sudo apt-get update
     $ sudo apt install linux-header-5.4.0-31-generic
     $ sudo apt install linux-image-generic-hwe-18.04-wip
     $ sudo reboot

   * install updated linux-firmware and pulseaudio
 $ sudo add-apt-repository ppa:kchsieh/training
 $ sudo apt-get update
 $ sudo apt install linux-firmware
 $ sudo apt install pulseaudio
 $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions

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


[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet

2020-05-28 Thread Lei Zhao
For my case, I simply cannot update the systemd to solve this problem
since the address I want to bind belongs to virtual tunnel device which
only gets added when there is a new tunnel connection. Oops!

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

Title:
  [SRU] dnsmasq doesn't start on boot because its interface isn't up yet

Status in One Hundred Papercuts:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Confirmed
Status in dnsmasq package in Debian:
  New

Bug description:
  [Impact]
  dnsmasq will fail to respond on network devices that weren't up when its
  service started, thus not binding as expected.

  [Test Case]
  TBD

  [Regression Potential]
  The fix is just configuring the order of service startup, so is unlikely to 
create any regressions.  Things to watch would be service related misbehaviors 
and general availability of the dnsmasq functionality.

  [Fix]
  Straightforward packaging fix to the service to make it delay startup
  until after the network is online.

  https://bugs.debian.org/cgi-
  bin/bugreport.cgi?att=1;bug=774970;filename=774970-network-
  online.debdiff;msg=22

  [Discussion]

  [Original Report]
  My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is 
managed manually in /etc/network/interfaces.

  During boot, dnsmasq is started before br-vz0 is created and this
  causes dnsmasq to exit:

  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up
  Jan  5 08:56:17 simon-laptop NetworkManager[937]:   NetworkManager 
(version 1.0.4) is starting...
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]: 
interface-parser: parsing file /etc/network/interfaces
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   found bridge ports 
none for br-vz0
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   adding bridge port 
none to eni_ifaces
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   management mode: 
unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq 2.75-1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  5 09:53:30 2016
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket

2020-05-28 Thread Seth Arnold
** Changed in: dbus (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  Legacy directory /var/run in /lib/systemd/system/dbus.socket

Status in D-Bus:
  New
Status in dbus package in Ubuntu:
  Fix Committed
Status in dbus package in Debian:
  Fix Released

Bug description:
  dbus/focal-proposed,now 1.12.16-2ubuntu1 amd64

  Re(o)curring after each new upgrade of dbus, for quite some time and
  still...

  $ dmesg|grep accordingly
  systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a 
path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket 
→ /run/dbus/system_bus_socket; please update the unit file accordingly.

  Originally:
  $cat /lib/systemd/system/dbus.socket
  [Unit]
  Description=D-Bus System Message Bus Socket

  [Socket]
  ListenStream=/var/run/dbus/system_bus_socket

  After change:
  $cat /lib/systemd/system/dbus.socket
  [Unit]
  Description=D-Bus System Message Bus Socket

  [Socket]
  ListenStream=/run/dbus/system_bus_socket

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

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


[Touch-packages] [Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

2020-05-28 Thread Launchpad Bug Tracker
This bug was fixed in the package wpa - 2:2.9-1ubuntu7

---
wpa (2:2.9-1ubuntu7) groovy; urgency=medium

  * debian/patches/git_roaming_interface.patch:
- backport upstream fix 'dbus: Move roam metrics to the correct
  interface', should reduces the number of events (lp: #1879087)

 -- Sebastien Bacher   Wed, 20 May 2020 19:03:27
+0200

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

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa package in Debian:
  New

Bug description:
  * Impact
  wpa ships an invalid network-manager configuration that triggers warnings

  * Test case
  $ journalctl | grep no-mac-addr-change
  should not have errors listed

  * Regression potential
  the change removes configurations which are not needed (since they set the 
value to the same one as the default) and in the wrong section, it shouldn't 
have any visible impact

  

  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity

2020-05-28 Thread Launchpad Bug Tracker
This bug was fixed in the package wpa - 2:2.9-1ubuntu7

---
wpa (2:2.9-1ubuntu7) groovy; urgency=medium

  * debian/patches/git_roaming_interface.patch:
- backport upstream fix 'dbus: Move roam metrics to the correct
  interface', should reduces the number of events (lp: #1879087)

 -- Sebastien Bacher   Wed, 20 May 2020 19:03:27
+0200

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

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

Title:
  dbus errors, frequent roaming and unstable connectivity

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Focal:
  Incomplete

Bug description:
  * Impact
  extra roaming events are been generated

  * Test case
  check the output of `journalctl -lu wpa_supplicant`, it should have warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  the roaming events should not be too frequent

  * Regression potential
  check that wifi connection keep working correctly

  --

  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:

  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  Having done a little research, at least the dbus errors seem to be
  fixed by this commit upstream:

  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756

  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work

2020-05-28 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1881213

Title:
  System hangs at reboot or poweroff. kworker blocked at dp_altmode_work

Status in xorg package in Ubuntu:
  New

Bug description:
  Expected:
  System reboots/powers off.

  Actual:
  System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing 
escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. 
  ```
  May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down.
  May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and 
block devices.
  May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to 
remaining processes...
  May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped
  ```
  Letting the computer continue to idle, an error message shows up. I've 
attached a picture because the error message does not show up in any logs. 

  Possibly a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though
  the other user did not mention the same symptoms.

  Description:Ubuntu 20.04 LTS
  Release:20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu May 28 16:53:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
  InstallationDate: Installed on 2020-05-22 (6 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20QVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET44W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme Gen2
  dmi.product.name: 20QVCTO1WW
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2
  dmi.product.version: ThinkPad X1 Extreme Gen2
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1881213] [NEW] System hangs at reboot or poweroff. kworker blocked at dp_altmode_work

2020-05-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Expected:
System reboots/powers off.

Actual:
System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing 
escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. 
```
May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down.
May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and 
block devices.
May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to 
remaining processes...
May 28 16:33: