[Touch-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Jeff P]

** Description changed:

  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.
  
  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.
  
  How I re-install pulseaudio:
  
  sudo apt-get install --reinstall pulseaudio
  
  I have tried just killing the pulseaudio service, and letting it restart
  on it's own. It restarts, but no audio. Reinstalling seems to do the
  trick though.
+ 
+ 
+ Note: File samples are after reinstalling. (working state)
  
  Thank You,
  Jeff
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  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.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.

  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

  I have tried just killing the pulseaudio service, and letting it
  restart on it's own. It restarts, but no audio. Reinstalling seems to
  do the trick though.

  
  Note: File samples are after reinstalling. (working state)

  Thank You,
  Jeff

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  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.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.11-0ubuntu51

---
apport (2.20.11-0ubuntu51) hirsute; urgency=medium

  * data/apport: Modify the check for whether or not a process is running in
the same namespace so that crashes from processes running protected in the
system.slice are considered as being from the same namespace. (LP: #1870060)
  * etc/apport/crashdb.conf: Enable Launchpad crash reports for 21.04.

 -- Brian Murray   Wed, 04 Nov 2020 13:40:41 -0800

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

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Triaged
Status in bluez source package in Focal:
  Invalid
Status in apport source package in Groovy:
  Triaged
Status in bluez source package in Groovy:
  New

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

-- 
Mailing list: https://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 1902983] Re: The display is constantly flickering

[Chris Guiver]

changed 'xorg' to 'xorg-server'

** Package changed: xorg (Ubuntu) => xorg-server (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/1902983

Title:
  The display is constantly flickering

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The display is running on intel graphics and it is constantly
  flickering when rendering gnome related programs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 5.8.14
  Uname: Linux 5.8.0-7625-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .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  455.28  Wed Sep 30 01:05:16 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Nov  5 09:45:30 2020
  DistUpgraded: 2020-08-06 15:02:44,138 DEBUG inhibit gnome-session idle
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 455.28, 5.8.0-7625-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2020-07-23 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic 
root=UUID=a1c36ce1-f1fe-444a-ace5-ef0166cc7adf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-06 (90 days ago)
  dmi.bios.date: 07/09/2020
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:br1.17:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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-server/+bug/1902983/+subscriptions

-- 
Mailing list: https://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 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5

[Alex Murray]

** Description changed:

- Ubuntu Groovy (20.10)
- kernel 5.8.0-20-generic
- neutron-linuxbridge-agent: 2:17.0.0~git2020091014.215a541bd4-0ubuntu1
- iptables: 1.8.5-3ubuntu1 (nf_tables)
- iptables-restore points to xtables-nft-multi
+ [Impact]
  
- After upgrading iptables from 1.8.4 to 1.8.5 and rebooting the neutron 
network node, neutron-linuxbridge-agent didn't properly start anymore.
+ With iptables 1.8.5 neutron-linuxbridge-agent fails to properly start.
+ 
  The log file shows many errors like:
  
  2020-10-05 10:20:37.998 551 ERROR
  neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr:
  iptables-restore: line 29 failed
  
- Downgrading iptables to 1.8.4 solves the problem.
- 
- Trying to do what the linuxbridge agent does:
- 2020-10-05 10:20:37.998 551 ERROR 
neutron.plugins.ml2.drivers.agent._common_agent *filter
- 2020-10-05 10:20:37.998 551 ERROR 
neutron.plugins.ml2.drivers.agent._common_agent :FORWARD - [0:0]
- 
- shows that
+ This can be demonstrated with a simple test case:
  
  iptables-restore 

[Touch-packages] [Bug 1902983] [NEW] The display is constantly flickering

[Surya Siddharthan]

Public bug reported:

The display is running on intel graphics and it is constantly flickering
when rendering gnome related programs

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 
5.8.14
Uname: Linux 5.8.0-7625-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.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  455.28  Wed Sep 30 01:05:16 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Thu Nov  5 09:45:30 2020
DistUpgraded: 2020-08-06 15:02:44,138 DEBUG inhibit gnome-session idle
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 455.28, 5.8.0-7625-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
InstallationDate: Installed on 2020-07-23 (104 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
 Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
 Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9570
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic 
root=UUID=a1c36ce1-f1fe-444a-ace5-ef0166cc7adf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-08-06 (90 days ago)
dmi.bios.date: 07/09/2020
dmi.bios.release: 1.17
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.17.1
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:br1.17:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
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

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


** Tags: amd64 apport-bug focal third-party-packages 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/1902983

Title:
  The display is constantly flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  The display is running on intel graphics and it is constantly
  flickering when rendering gnome related programs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 5.8.14
  Uname: Linux 5.8.0-7625-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .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: ""
  

[Touch-packages] [Bug 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5

[Alex Murray]

** Changed in: iptables (Ubuntu Groovy)
   Status: Triaged => In Progress

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

Title:
  neutron-linuxbridge-agent fails to start with iptables 1.8.5

Status in iptables package in Ubuntu:
  Fix Committed
Status in neutron package in Ubuntu:
  Invalid
Status in iptables source package in Groovy:
  In Progress
Status in neutron source package in Groovy:
  Invalid
Status in iptables source package in Hirsute:
  Fix Committed
Status in neutron source package in Hirsute:
  Invalid

Bug description:
  Ubuntu Groovy (20.10)
  kernel 5.8.0-20-generic
  neutron-linuxbridge-agent: 2:17.0.0~git2020091014.215a541bd4-0ubuntu1
  iptables: 1.8.5-3ubuntu1 (nf_tables)
  iptables-restore points to xtables-nft-multi

  After upgrading iptables from 1.8.4 to 1.8.5 and rebooting the neutron 
network node, neutron-linuxbridge-agent didn't properly start anymore.
  The log file shows many errors like:

  2020-10-05 10:20:37.998 551 ERROR
  neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr:
  iptables-restore: line 29 failed

  Downgrading iptables to 1.8.4 solves the problem.

  Trying to do what the linuxbridge agent does:
  2020-10-05 10:20:37.998 551 ERROR 
neutron.plugins.ml2.drivers.agent._common_agent *filter
  2020-10-05 10:20:37.998 551 ERROR 
neutron.plugins.ml2.drivers.agent._common_agent :FORWARD - [0:0]

  shows that

  iptables-restore 

[Touch-packages] [Bug 1899751] Re: pulseaudio - NO SOUND on DELL XPS L502X

[Daniel van Vugt]

(like bug 1902976)

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

Title:
  pulseaudio - NO SOUND on DELL XPS L502X

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  enat@Dell-XPS-L502X:~$ pulseaudio
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: Произошла ошибка при выполнении pa_pid_file_create().
  renat@Dell-XPS-L502X:~$ ubuntu-bug pulseaudio
  /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required 
(got type float).  Implicit conversion to integers using __int__ is deprecated, 
and may be removed in a future version of Python.
progress.setValue(value * 1000)
  renat@Dell-XPS-L502X:~$ 

  
  Still no Icon of the Speaker and no sound since update to beta...please fix 
it.
  Thx for a great job.

  Renat.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  renat   993 F pulseaudio
renat   996 F pipewire-media-
   /dev/snd/controlC1:  renat   996 F pipewire-media-
   /dev/snd/seq:renat   992 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 14 10:26:41 2020
  InstallationDate: Installed on 2019-07-01 (470 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-04 (9 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:br0.1:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1899751] Re: pulseaudio - NO SOUND on DELL XPS L502X

[Daniel van Vugt]

Please try uninstalling 'pipewire' because it looks like that is
stealing audio interfaces from PulseAudio.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

Title:
  pulseaudio - NO SOUND on DELL XPS L502X

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  enat@Dell-XPS-L502X:~$ pulseaudio
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: Произошла ошибка при выполнении pa_pid_file_create().
  renat@Dell-XPS-L502X:~$ ubuntu-bug pulseaudio
  /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required 
(got type float).  Implicit conversion to integers using __int__ is deprecated, 
and may be removed in a future version of Python.
progress.setValue(value * 1000)
  renat@Dell-XPS-L502X:~$ 

  
  Still no Icon of the Speaker and no sound since update to beta...please fix 
it.
  Thx for a great job.

  Renat.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  renat   993 F pulseaudio
renat   996 F pipewire-media-
   /dev/snd/controlC1:  renat   996 F pipewire-media-
   /dev/snd/seq:renat   992 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 14 10:26:41 2020
  InstallationDate: Installed on 2019-07-01 (470 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-04 (9 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:br0.1:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1902976] Re: PulseAudio doesn't work when pipewire is installed

[Daniel van Vugt]

** Summary changed:

- [Acer Aspire E5-432] After boot pulseaudio needs to be restarted
+ PulseAudio doesn't work when pipewire is installed

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

** Package changed: pulseaudio (Ubuntu) => pipewire (Ubuntu)

** Summary changed:

- PulseAudio doesn't work when pipewire is installed
+ PulseAudio doesn't work when pipewire is installed (ie. KDE)

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

Title:
  PulseAudio doesn't work when pipewire is installed (ie. KDE)

Status in pipewire package in Ubuntu:
  New

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://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 1902976] Re: [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

[Pablo Pedrotti]

Uninstalling pipewire fixed the issue. Now both the speakers and the
microphone work properly.

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

Title:
  [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://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 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases

[Haw Loeung]

Attached /var/log/syslog.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902960/+attachment/5431334/+files/syslog

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases

[Launchpad Bug Tracker]

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

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

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases

[Haw Loeung]

Spun up a new unit in Azure and also ran into this:

| https://paste.ubuntu.com/p/zd6z8dZ5Zr/

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902976] Re: [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

[Daniel van Vugt]

It looks like pipewire might have stolen some of the audio interfaces
from pulseaudio. Please try uninstalling pipewire.

** Summary changed:

- After boot pulseaudio needs to be restarted
+ [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

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

Title:
  [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://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 1902976] [NEW] After boot pulseaudio needs to be restarted

[Pablo Pedrotti]

Public bug reported:

After an upgrade pulseaudio does not run properly after boot unless I
restart the service with the command systemctl --user restart
pulseaudio. Reinstalling the service with the comand apt-get install
--reinstall pulseaudio also solves the issue.

I am currently running Kubuntu 20.10 and the pulseaudio version is
1:13.99.2-1ubuntu2.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
  ppedrotti   5420 F pulseaudio
 /dev/snd/seq:ppedrotti   1567 F pipewire
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Nov  4 23:13:09 2020
InstallationDate: Installed on 2020-10-17 (18 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
dmi.bios.date: 12/07/2015
dmi.bios.release: 0.0
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Robin_BA
dmi.board.vendor: Acer
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.10
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
dmi.product.family: BSW
dmi.product.name: Aspire E5-432
dmi.product.sku: Aspire E5-432
dmi.product.version: V1.10
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug groovy

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/bugs/1902976/+attachment/5431303/+files/alsa-info.txt

** Attachment removed: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902976/+attachment/5431303/+files/alsa-info.txt

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

Title:
  After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://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 1902853] Re: Failure to create core GL context with llvmpipe when using GLX_ARB_context_flush_control

[Daniel van Vugt]

I would suggest reporting the issue upstream but they will ask you to
test a newer version first. So please try live booting Ubuntu 20.10 from
USB (which includes Mesa 20.2) and tell us if it has the same problem:

  https://ubuntu.com/download/desktop

If the problem persists then please open a bug upstream at
https://gitlab.freedesktop.org/groups/mesa/-/issues and then tell us the
new issue ID.

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

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

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

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

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

Title:
  Failure to create core GL context with llvmpipe when using
  GLX_ARB_context_flush_control

Status in libsdl2 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  When using llvmpipe on the non-HWE xorg version GL core context
  creation fails when using "GLX_ARB_context_flush_control" even though
  the driver reports that the extension is supported.

  Apologies if xorg is the wrong package here, this could be a libgl1
  -mesa-dri/glx bug instead, it's unclear to me where the fault lies in
  the graphics stack.

  xserver-common:
Installed: 2:1.19.6-1ubuntu4.7
Candidate: 2:1.19.6-1ubuntu4.7
  linux-generic:
Installed: 4.15.0.122.109
Candidate: 4.15.0.122.109

  Steps to reproduce on Ubuntu Server:
  1. Install Ubuntu 18.04 server edition in a VM, or other hardware without a 
physical graphics device
  2. Install the desktop with "sudo apt install ubuntu-desktop"
  3. Reboot
  4. Compile and run the attached file

  Steps to reproduce on Ubuntu Desktop:
  1. Install Ubuntu 18.04 desktop edition in a VM, or other hardware without a 
physical graphics device
  2. Remove the HWE packages with "apt remove *-hwe-18.04" and then "apt 
install xserver-xorg-core ubuntu-desktop xserver-xorg xserver-xorg-video-all 
xserver-xorg-input-all libgl1-mesa-dri libgl1-mesa-glx" to get things back to 
normal
  3. Reboot
  4. Compile and run the attached file

  Both examples produce:
  "Could not create GL context: BadValue (integer parameter out of range for 
operation)"

  For both cases, upgrading to (or staying on) the HWE stack allows
  creating the core 3.3 context successfully.

  
  Debugging:

  I've stepped all the way into libxcb for the context creation at
  src/glx.c:3258, with a call to
  "xcb_glx_create_context_attribs_arb_checked", but haven't managed to
  link this up to a received request in another process. The request is
  rejected with BadValue.

  BadVaue in this instance could mean one of two things according to GL spec:
  1. The GLX_RENDER_TYPE attribute is invalid
  2. An attribute or it's bitmask are not recognized.

  We can likely rule out 1 as GLX_RENDER_TYPE is correctly set to
  opengl. Option 2 allows looking at it at a higher level. SDL2 adds
  `GLX_CONTEXT_RELEASE_BEHAVIOUR_ARB=GLX_CONTEXT_RELEASE_BEHAVIOUR_FLUSH_ARB`
  to the attributes (at src/video/x11/SDL_x11opengl.c:720) by default
  when it detects the `GLX_ARB_context_flush_control` extension is
  present, which should be a no-op and the default setting. `glxinfo`
  and other gl functions all show that `GLX_ARB_context_flush_control`
  is present, but removing that usage from the attributes list (by
  removing lines 720 to 726 avoids the issue and we are given a valid GL
  context.

  Due to this, I think something in the graphics stack is rejecting the
  usage of GLX_ARB_context_flush_control, even though it's claiming to
  support it through other gl calls. The llvmpipe GL driver reports core
  support up to 3.3 as well, so this shouldn't be an issue. I also
  suspect it's simply something that's been fixed more recently, as
  installing the newer HWE versions of xorg (and the kernel) fixes the
  issue.

  
  I wouldn't expect to have to upgrade to the HWE stack to be able to get a 
working GL context this way, so I'm reporting this to check if it's a known 
issue or if there's a fix that can be made.

  The attached file depends on "libsdl2-dev" and can be compiled and run with:
  "g++ main.cpp -I/usr/include/SDL2 -lSDL2 -lGL && ./a.out"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:16:16 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter 

[Touch-packages] [Bug 1902899] Re: Color management is not quite good

[Daniel van Vugt]

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

This sounds like bug 938751. Please let us know if the workaround for
that doesn't fix your issue.

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

** This bug has been marked a duplicate of bug 938751
   Images are washed out or colors are skewed in some apps (particularly Image 
Viewer and Chrome)

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

Title:
  Color management is not quite good

Status in Ubuntu:
  New

Bug description:
  While attempting to work with software like Figma, Inskcape and Gimp I
  noticed that the screen I have doesn't show colors like in my iMac or
  in WIndows. When I plug the same display on my laptop running Ubuntu
  20.04 the colors just looks very opaque and desaturated. I looked on
  the web for a tool to fix this but it just doesn't exist. I think this
  could be a bug or a a problem with drivers. But theres no proprietary
  drivers for this machine. The open source Intel drivers are just
  terrible. I suggest Ubuntu developers include potentiometers to manage
  color saturation, contrast, brightness and temperature under the
  "Color" tab on Ubuntu settings pannel. When I go to the color section
  of the settings pannel it only allows me to chose a color profile but
  I can't even adjust color settings. I really wish Linux systems be
  more usable when it comes to work with graphic software in the future.

  My system info:

  Lenovo Ideapad s145
  Ubuntu 20.04.1 LTS
  Processor: Intel® Core™ i3-8130U CPU @ 2.20GHz × 4 
  Graphics: Mesa Intel® UHD Graphics 620 (KBL GT2)
  GNOME version: 3.36.3
  X11
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 12:08:10 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: darling-mach, 0.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3fdf]
  InstallationDate: Installed on 2020-10-14 (21 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81XM
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=a08ea31a-d24d-4a85-b391-c1950060f906 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 10/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CSCN10WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvrCSCN10WW:bd10/12/2019:svnLENOVO:pn81XM:pvrLenovoIdeaPadS145-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IKB:
  dmi.product.family: IdeaPad S145-15IKB
  dmi.product.name: 81XM
  dmi.product.sku: LENOVO_MT_81XM_BU_idea_FM_IdeaPad S145-15IKB
  dmi.product.version: Lenovo IdeaPad S145-15IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103+git2011040630.5dea8f~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2011040730.58e708~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To 

[Touch-packages] [Bug 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

[Daniel van Vugt]

If the problem is just the window decorations then this is an Xwayland
bug (source package 'xorg-server').

But I can't tell right now if parts of Firefox itself are also missing.
And either way, the problem could be triggered by Firefox itself.

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

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

** Tags added: xrandr-scaling

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

Title:
  Scaling one monitor (to 1.5x in my case) can cause Firefox to lose
  window features (titlebar, buttons, bookmark bar)

Status in firefox package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.

  While Firefox is already open, after logging in with the lock screen,
  or modifying display settings, sometimes Firefox will lose the
  titlebar, address bar, buttons, and bookmark bar. The website being
  displayed will still show, however not all features are usable (right
  click menu, mouse icon doesn't change).

  Reproduction steps:

  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - Lock screen or leave computer alone until the screen locks.
  - Login
  - Firefox may have lost the window chrome

  Workaround:

  - Open Display Settings
  - Change display settings or zoom level, then change back.

  Computer info:

  - Ubuntu 20.04.1
  - Fractional Scaling enabled
  - NVidia GeForce GTX 1080/PCIe/SSE2
  - Gnome 3.36.3
  - X11
  - Samsung LU32J590 4K (3840x2160) @ 1.5x
  - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:31:17 2020
  DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
  InstallationDate: Installed on 2018-04-28 (920 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
  dmi.bios.date: 04/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.80
  dmi.board.name: X99 Extreme4
  dmi.board.vendor: ASRock
  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.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  

[Touch-packages] [Bug 1574243] Re: Unable to adjust screen backlight on login screen on Macbook Pro (early 2015)

[user 76543456789]

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645251/+files/CurrentDmesg.txt

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645265/+files/XorgLog.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645266/+files/XorgLogOld.txt

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

Title:
  Unable to adjust screen backlight on login screen on Macbook Pro
  (early 2015)

Status in xorg package in Ubuntu:
  New

Bug description:
  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu

  Fresh install of 16.04.

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Don't know. The guide to identify the package told me all login screen
  issues were "LightDM". ubuntu-bug told me that package was not
  installed.

  3) What you expected to happen

  To be able to adjust screen backlight brightness with the dedicated
  hardware buttons on the login screen, in order to be able log in. This
  works as expected whenever I'm logged in.

  4) What happened instead

  I had to log in from an almost black login screen with no backlight.

  I believe this bug was present in 15.10 as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 24 13:58:00 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:162b] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Broadwell-U Integrated Graphics [106b:013f]
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=dd7fd213-44e3-45de-afe3-efd8c5825c1e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B16.1602111810
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B16.1602111810:bd02/11/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 24 02:40:40 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41002 
   vendor APP
  xserver.version: 2:1.18.3-1ubuntu2

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

-- 
Mailing list: https://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 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Daniel van Vugt]

Since every model of laptop has slightly different audio hardware, and
slightly different problems, we should open a separate bug for each
model. This bug is about the Asus ZenBook UX425IA.

For other machine types please open a new bug by running:

  ubuntu-bug pulseaudio

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

Title:
  [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.

  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

  I have tried just killing the pulseaudio service, and letting it
  restart on it's own. It restarts, but no audio. Reinstalling seems to
  do the trick though.

  Thank You,
  Jeff

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  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.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Jay Jones]

I lost audio as well and have to reinstall pulseaudio everytime I boot the 
computer to get it back-- otherwise you have Dummy Output only.  Everything 
worked fine until I updated this batch (from /var/log/apt/history.log):
Upgrade: netplan.io:amd64 (0.100-0ubuntu4~20.04.2, 0.100-0ubuntu4~20.04.3), 
libsystemd0:amd64 (245.4-4ubuntu3.2, 245.4-4ubuntu3.3), libasound2-data:amd64 
(1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1), systemd-coredump:amd64 
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), udev:amd64 (245.4-4ubuntu3.2, 
245.4-4ubuntu3.3), alsa-utils:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), 
libudev1:amd64 (245.4-4ubuntu3.2, 245.4-4ubuntu3.3), systemd-timesyncd:amd64 
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), libnss-myhostname:amd64 
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), systemd-sysv:amd64 (245.4-4ubuntu3.2, 
245.4-4ubuntu3.3), chromium-codecs-ffmpeg-extra:amd64 
(1:85.0.4183.83-0ubuntu0.20.04.1, 1:85.0.4183.83-0ubuntu0.20.04.2), 
libpam-systemd:amd64 (245.4-4ubuntu3.2, 245.4-4ubuntu3.3), systemd:amd64 
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), libnss-systemd:amd64 (245.4-4ubuntu3.2, 
245.4-4ubuntu3.3), libasound2:amd64 (1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1), 
libnetplan0:amd64 (0.100-0ubuntu4~20.04.2, 0.100-0ubuntu4~20.04.3), 
libatopology2:amd64 (1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1)

Running 5.8.0-25 kernel on Renoir 4700U laptop (HP Envy x360 13)

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

Title:
  [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.

  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

  I have tried just killing the pulseaudio service, and letting it
  restart on it's own. It restarts, but no audio. Reinstalling seems to
  do the trick though.

  Thank You,
  Jeff

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  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.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Daniel van Vugt]

Yes we plan on it eventually (bug 1902485).

** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030
   Importance: Unknown
   Status: Unknown

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

Title:
  [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1902960] SystemdDelta.txt

[David Lawson]

apport information

** Attachment added: "SystemdDelta.txt"
   
https://bugs.launchpad.net/bugs/1902960/+attachment/5431251/+files/SystemdDelta.txt

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] UdevDb.txt

[David Lawson]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1902960/+attachment/5431252/+files/UdevDb.txt

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] acpidump.txt

[David Lawson]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1902960/+attachment/5431253/+files/acpidump.txt

** Description changed:

  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to have
  broken DNS resolution across much of our Azure fleet earlier today.  We
  ended up mitigating this by forcing reboots on the associated instances,
  no combination of networkctl reload, reconfigure, systemctl daemon-
  reexec, systemctl daemon-reload, netplan generate, netplan apply would
  get resolvectl to have a DNS server again.  The main symptom appears to
  have been systemd-networkd believing it wasn't managing the eth0
  interfaces:
  
- 
- ubuntu@machine-1:~$ sudo networkctl   

  
- IDX LINK TYPE OPERATIONAL SETUP   

 
-   1 lo   loopback carrier unmanaged   

 
-   2 eth0 etherroutableunmanaged   

 
-   

 2 links listed.
+ ubuntu@machine-1:~$ sudo networkctl
+ IDX LINK TYPE OPERATIONAL SETUP
+   1 lo   loopback carrier unmanaged
+   2 eth0 etherroutableunmanaged
+   2 
links listed.
  
  Which eventually made them lose their DNS resolvers:
  
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):
  
  After rebooting, we see this behaving properly:
  
  ubuntu@machine-1:~$ sudo networkctl list
- IDX LINK TYPE OPERATIONAL SETUP 
-   1 lo   loopback carrier unmanaged 
-   2 eth0 etherroutableconfigured
+ IDX LINK TYPE OPERATIONAL SETUP
+   1 lo   loopback carrier unmanaged
+   2 eth0 etherroutableconfigured
  
  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16
  
- 
  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
-  -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
- +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
- +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
- +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
- \-08.0  Microsoft Corporation Hyper-V virtual VGA
+  -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
+ +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
+ +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
+ +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
+ \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
-  
+ 
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 

[Touch-packages] [Bug 1902960] ProcCpuinfoMinimal.txt

[David Lawson]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1902960/+attachment/5431248/+files/ProcCpuinfoMinimal.txt

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] Dependencies.txt

[David Lawson]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1902960/+attachment/5431245/+files/Dependencies.txt

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] ProcCpuinfo.txt

[David Lawson]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1902960/+attachment/5431247/+files/ProcCpuinfo.txt

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] ProcModules.txt

[David Lawson]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1902960/+attachment/5431250/+files/ProcModules.txt

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] ProcInterrupts.txt

[David Lawson]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1902960/+attachment/5431249/+files/ProcInterrupts.txt

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] Lspci.txt

[David Lawson]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1902960/+attachment/5431246/+files/Lspci.txt

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  ubuntu@machine-1:~$ sudo networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableunmanaged
    2 
links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
  +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
  +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
  +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
  \-08.0  Microsoft Corporation Hyper-V virtual VGA
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: systemd 245.4-4ubuntu3.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1031-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090008
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases

[David Lawson]

apport information

** Tags added: apport-collected focal uec-images

** Description changed:

  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to have
  broken DNS resolution across much of our Azure fleet earlier today.  We
  ended up mitigating this by forcing reboots on the associated instances,
  no combination of networkctl reload, reconfigure, systemctl daemon-
  reexec, systemctl daemon-reload, netplan generate, netplan apply would
  get resolvectl to have a DNS server again.  The main symptom appears to
  have been systemd-networkd believing it wasn't managing the eth0
  interfaces:
  
  
  ubuntu@machine-1:~$ sudo networkctl   

  
  IDX LINK TYPE OPERATIONAL SETUP   

 
1 lo   loopback carrier unmanaged   

 
2 eth0 etherroutableunmanaged   

 


 2 links listed.
  
  Which eventually made them lose their DNS resolvers:
  
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):
  
  After rebooting, we see this behaving properly:
  
  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP 
1 lo   loopback carrier unmanaged 
2 eth0 etherroutableconfigured
  
  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16
  
  
  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.10
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ Lspci-vt:
+  -[:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled)
+ +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
+ +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
+ +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
+ \-08.0  Microsoft Corporation Hyper-V virtual VGA
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: Microsoft Corporation Virtual Machine
+ Package: systemd 245.4-4ubuntu3.3
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure 
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
+ ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
+ Tags:  focal uec-images
+ Uname: Linux 5.4.0-1031-azure x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 12/07/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 090008
+ dmi.board.name: Virtual Machine
+ dmi.board.vendor: Microsoft Corporation
+ dmi.board.version: 7.0
+ dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Microsoft Corporation
+ dmi.chassis.version: 7.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
+ dmi.product.name: Virtual Machine
+ dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
+ dmi.product.version: 7.0
+ dmi.sys.vendor: Microsoft Corporation

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1902960/+attachment/5431244/+files/CurrentDmesg.txt

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended 

[Touch-packages] [Bug 1902960] [NEW] Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases

[David Lawson]

Public bug reported:

The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to have
broken DNS resolution across much of our Azure fleet earlier today.  We
ended up mitigating this by forcing reboots on the associated instances,
no combination of networkctl reload, reconfigure, systemctl daemon-
reexec, systemctl daemon-reload, netplan generate, netplan apply would
get resolvectl to have a DNS server again.  The main symptom appears to
have been systemd-networkd believing it wasn't managing the eth0
interfaces:


ubuntu@machine-1:~$ sudo networkctl 


IDX LINK TYPE OPERATIONAL SETUP 

   
  1 lo   loopback carrier unmanaged 

   
  2 eth0 etherroutableunmanaged 

   


   2 links listed.

Which eventually made them lose their DNS resolvers:

ubuntu@machine-1:~$ sudo resolvectl dns
Global:
Link 2 (eth0):

After rebooting, we see this behaving properly:

ubuntu@machine-1:~$ sudo networkctl list
IDX LINK TYPE OPERATIONAL SETUP 
  1 lo   loopback carrier unmanaged 
  2 eth0 etherroutableconfigured

2 links listed.
ubuntu@machine-1:~$ sudo resolvectl dns
Global:
Link 2 (eth0): 168.63.129.16


This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.

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

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing reboots on the
  associated instances, no combination of networkctl reload,
  reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
  generate, netplan apply would get resolvectl to have a DNS server
  again.  The main symptom appears to have been systemd-networkd
  believing it wasn't managing the eth0 interfaces:

  
  ubuntu@machine-1:~$ sudo networkctl   

  
  IDX LINK TYPE OPERATIONAL SETUP   

 
1 lo   loopback carrier unmanaged   

 
2 eth0 etherroutableunmanaged   

 


 2 links listed.

  Which eventually made them lose their DNS resolvers:

  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0):

  After rebooting, we see this behaving properly:

  ubuntu@machine-1:~$ sudo networkctl list
  IDX LINK TYPE OPERATIONAL SETUP 
1 lo   loopback carrier unmanaged 
2 eth0 etherroutableconfigured

  2 links listed.
  ubuntu@machine-1:~$ sudo resolvectl dns
  Global:
  Link 2 (eth0): 168.63.129.16

  
  This appears to be specifically linked to the upgrade, i.e. we were able to 
provoke the issue by upgrading the systemd package, so I suspect it's part of 
the packaging in the upgrade process.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

[Brian Murray]

** Also affects: apport (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

** Changed in: apport (Ubuntu Groovy)
   Importance: Undecided => High

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

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Triaged
Status in bluez source package in Focal:
  Invalid
Status in apport source package in Groovy:
  Triaged
Status in bluez source package in Groovy:
  New

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

-- 
Mailing list: https://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 1902899] Re: Color management is not quite good

[Flávio Vivório Salles]

I uninstalled Oibaf graphics right now in order to perform extra
debugging if not too technical. And because I didn't notice any
improvements after installing Oibaf.

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

Title:
  Color management is not quite good

Status in xorg package in Ubuntu:
  New

Bug description:
  While attempting to work with software like Figma, Inskcape and Gimp I
  noticed that the screen I have doesn't show colors like in my iMac or
  in WIndows. When I plug the same display on my laptop running Ubuntu
  20.04 the colors just looks very opaque and desaturated. I looked on
  the web for a tool to fix this but it just doesn't exist. I think this
  could be a bug or a a problem with drivers. But theres no proprietary
  drivers for this machine. The open source Intel drivers are just
  terrible. I suggest Ubuntu developers include potentiometers to manage
  color saturation, contrast, brightness and temperature under the
  "Color" tab on Ubuntu settings pannel. When I go to the color section
  of the settings pannel it only allows me to chose a color profile but
  I can't even adjust color settings. I really wish Linux systems be
  more usable when it comes to work with graphic software in the future.

  My system info:

  Lenovo Ideapad s145
  Ubuntu 20.04.1 LTS
  Processor: Intel® Core™ i3-8130U CPU @ 2.20GHz × 4 
  Graphics: Mesa Intel® UHD Graphics 620 (KBL GT2)
  GNOME version: 3.36.3
  X11
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 12:08:10 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: darling-mach, 0.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3fdf]
  InstallationDate: Installed on 2020-10-14 (21 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81XM
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=a08ea31a-d24d-4a85-b391-c1950060f906 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 10/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CSCN10WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvrCSCN10WW:bd10/12/2019:svnLENOVO:pn81XM:pvrLenovoIdeaPadS145-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IKB:
  dmi.product.family: IdeaPad S145-15IKB
  dmi.product.name: 81XM
  dmi.product.sku: LENOVO_MT_81XM_BU_idea_FM_IdeaPad S145-15IKB
  dmi.product.version: Lenovo IdeaPad S145-15IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103+git2011040630.5dea8f~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2011040730.58e708~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5

[Jamie Strandboge]

FYI, 1.8.5-3ubuntu3 was uploaded to hirsute-proposed yesterday.
1.8.5-3ubuntu2.20.10.1 is in the unapproved queue for groovy-proposed.
Alex said he'd do the SRU paperwork.

** Changed in: iptables (Ubuntu Hirsute)
   Status: Triaged => Fix Committed

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

Title:
  neutron-linuxbridge-agent fails to start with iptables 1.8.5

Status in iptables package in Ubuntu:
  Fix Committed
Status in neutron package in Ubuntu:
  Invalid
Status in iptables source package in Groovy:
  Triaged
Status in neutron source package in Groovy:
  Invalid
Status in iptables source package in Hirsute:
  Fix Committed
Status in neutron source package in Hirsute:
  Invalid

Bug description:
  Ubuntu Groovy (20.10)
  kernel 5.8.0-20-generic
  neutron-linuxbridge-agent: 2:17.0.0~git2020091014.215a541bd4-0ubuntu1
  iptables: 1.8.5-3ubuntu1 (nf_tables)
  iptables-restore points to xtables-nft-multi

  After upgrading iptables from 1.8.4 to 1.8.5 and rebooting the neutron 
network node, neutron-linuxbridge-agent didn't properly start anymore.
  The log file shows many errors like:

  2020-10-05 10:20:37.998 551 ERROR
  neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr:
  iptables-restore: line 29 failed

  Downgrading iptables to 1.8.4 solves the problem.

  Trying to do what the linuxbridge agent does:
  2020-10-05 10:20:37.998 551 ERROR 
neutron.plugins.ml2.drivers.agent._common_agent *filter
  2020-10-05 10:20:37.998 551 ERROR 
neutron.plugins.ml2.drivers.agent._common_agent :FORWARD - [0:0]

  shows that

  iptables-restore 

[Touch-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

[Brian Murray]

** Description changed:

+ [Impact]
+ apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.
+ 
+ [Test Case]
+ On an Ubuntu desktop system perform the following step
+ 1) sudo pkill -11 upowerd
+ 
+ With the current version of apport there will not be a crash file for
+ upowerd in /var/crash/. With the version of apport in -proposed there
+ will be a crash file for upowerd in /var/crash/.
+ 
+ [Regression Potential]
+ In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.
+ 
+ [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes
  
  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Confirmed
Status in bluez source package in Focal:
  Invalid

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

-- 
Mailing list: https://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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

[Michael Nazzareno Trimarchi]

Dear Sebastian, the problem that the station patch was backported
already but wrongly. I have just fixed in this package

This is coming from change log

wpa (2:2.6-15ubuntu1) bionic; urgency=low

  * Merge from Debian unstable.  Remaining changes:
- debian/patches/wpa_service_ignore-on-isolate.patch: add
  IgnoreOnIsolate=yes so that when switching "runlevels" in oem-config
  will not kill off wpa and cause wireless to be unavailable on first
  boot.
- debian/patches/session-ticket.patch: disable the TLS Session Ticket
  extension to fix auth with 802.1x PEAP on some hardware.
- debian/patches/android_hal_fw_path_change.patch: add a DBus method
  for requesting a firmware change when working with the Android HAL;
  this is used to set a device in P2P or AP mode; conditional to
  CONFIG_ANDROID_HAL being enabled.
- debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL.
- debian/control: Build-Depends on android-headers to get the required
  wifi headers for the HAL support.
- debian/patches/dbus-available-sta.patch: Make the list of connected
  stations available on DBus for hotspot mode; along with some of the
  station properties, such as rx/tx packets, bytes, capabilities, etc.

Up you have the patch that break the package. I just made it working
properly patch the package



  * Updated debian/patches/dbus-available-sta.patch for new getter API

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  New

Bug description:
  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc. 
  The regression was introduced when someone try to have the Station attribute 
supported

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

-- 
Mailing list: https://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 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

[Allan Bogh]

** Description changed:

  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.
  
- While Firefox is already open, after logging into the lock screen,
+ While Firefox is already open, after logging in with the lock screen,
  sometimes Firefox will lose the titlebar, address bar, buttons, and
  bookmark bar. The website being displayed will still show, however not
  all features are usable (right click menu, mouse icon doesn't change).
  
  Reproduction steps:
  
  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - Lock screen or leave computer alone until the screen locks.
  - Login
  - Firefox may have lost the window chrome
  
  Workaround:
  
  - Open Display Settings
  - Change display settings or zoom level, then change back.
  
  Computer info:
  
  - Ubuntu 20.04.1
  - Fractional Scaling enabled
  - NVidia GeForce GTX 1080/PCIe/SSE2
  - Gnome 3.36.3
  - X11
  - Samsung LU32J590 4K (3840x2160) @ 1.5x
  - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:31:17 2020
  DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
  InstallationDate: Installed on 2018-04-28 (920 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
  dmi.bios.date: 04/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.80
  dmi.board.name: X99 Extreme4
  dmi.board.vendor: ASRock
  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.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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

** Description changed:

  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.
  
- While Firefox is already open, after logging in with the lock screen,
- sometimes Firefox will lose the titlebar, address bar, buttons, and
- bookmark bar. The website being displayed will still show, however not
- all features are usable (right click menu, mouse icon doesn't change).
+ While Firefox is already open, after logging in with the lock 

[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Gunnar Hjalmarsson]

Good catch, @Rasmus. I see the same thing, and posted my theory about
what causes it here:

https://gitlab.gnome.org/GNOME/pango/-/issues/483#note_953154

Hmm.. I'm afraid this can be called a regression. Even if the wrong
styles were shown previously, selecting any of those at least didn't
cause gnome-terminal to crash.

@Łukasz: What do you think? Myself can't help thinking (again) about the
alternative solution we discussed shortly, i.e. replacing this gtk
change in groovy with a simple gnome-terminal patch which would give us
the focal behavior back.

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

[Jorge Niedbalski]

Hello Karsten,

Can you check comments https://bugs.launchpad.net/dhcp/+bug/1872118/comments/62
 and https://bugs.launchpad.net/dhcp/+bug/1872118/comments/63 and validate the 
versions?

* Also, could be possible to upload the crash report here? and the
output of dpkg -l

Thanks,

Jorge

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

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in isc-dhcp source package in Focal:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

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

-- 
Mailing list: https://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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Darko Veberic]

indeed, i get a crash if i click on the following fonts: Bitstream Vera
Sans Mono, DejaVu Sans Mono, Inconsolata, MathJax_Vector-Bold, and
Terminus.

note that in the font chooser these font names appear to be rendered not
in their particular typeface but with the default system font so is
seems there is the bug still lingering somewhere.

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

[Allan Bogh]

I've attached an image of Netflix showing on the Dell monitor after I
changed the zoom level back to 1.5x for the Samsung monitor. The image
shows Firefox without the window border. Netflix was not in fullscreen
mode.

** Attachment added: "Netflix on Dell monitor without window features, not in 
fullscreen mode"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902921/+attachment/5431155/+files/Screenshot_2020-11-04_09-55-18.png

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

Title:
  Scaling one monitor (to 1.5x in my case) can cause Firefox to lose
  window features (titlebar, buttons, bookmark bar)

Status in xorg package in Ubuntu:
  New

Bug description:
  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.

  While Firefox is already open, after logging into the lock screen,
  sometimes Firefox will lose the titlebar, address bar, buttons, and
  bookmark bar. The website being displayed will still show, however not
  all features are usable (right click menu, mouse icon doesn't change).

  Reproduction steps:

  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - Lock screen or leave computer alone until the screen locks.
  - Login
  - Firefox may have lost the window chrome

  Workaround:

  - Open Display Settings
  - Change display settings or zoom level, then change back.

  Computer info:

  - Ubuntu 20.04.1
  - Fractional Scaling enabled
  - NVidia GeForce GTX 1080/PCIe/SSE2
  - Gnome 3.36.3
  - X11
  - Samsung LU32J590 4K (3840x2160) @ 1.5x
  - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:31:17 2020
  DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
  InstallationDate: Installed on 2018-04-28 (920 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
  dmi.bios.date: 04/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.80
  dmi.board.name: X99 Extreme4
  dmi.board.vendor: ASRock
  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.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Touch-packages] [Bug 1902921] [NEW] Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

[Allan Bogh]

Public bug reported:

One monitor is a 4K monitor scaled to 1.5x, the other is a normal
1920x1080 monitor scaled to 1x.

While Firefox is already open, after logging into the lock screen,
sometimes Firefox will lose the titlebar, address bar, buttons, and
bookmark bar. The website being displayed will still show, however not
all features are usable (right click menu, mouse icon doesn't change).

Reproduction steps:

- Change zoom level of one or more monitors to >1.0 but less than 2.0 (have not 
tested with non-fractional zooms)
- Open Firefox and browse to any website
- Lock screen or leave computer alone until the screen locks.
- Login
- Firefox may have lost the window chrome

Workaround:

- Open Display Settings
- Change display settings or zoom level, then change back.

Computer info:

- Ubuntu 20.04.1
- Fractional Scaling enabled
- NVidia GeForce GTX 1080/PCIe/SSE2
- Gnome 3.36.3
- X11
- Samsung LU32J590 4K (3840x2160) @ 1.5x
- Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 09:31:17 2020
DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
InstallationDate: Installed on 2018-04-28 (920 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
dmi.bios.date: 04/06/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.80
dmi.board.name: X99 Extreme4
dmi.board.vendor: ASRock
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.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
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

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


** Tags: amd64 apport-bug focal possible-manual-nvidia-install ubuntu

** Description changed:

  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.
  
  While Firefox is already open, after logging into the lock screen,
  sometimes Firefox will lose the titlebar, address bar, buttons, and
  bookmark bar. The website being displayed will still show, however not
  all features are usable (right click menu, mouse icon doesn't change).
  
  Reproduction steps:
  
  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - 

[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Rasmus Underbjerg Pinnerup]

Thanks for the speedy work! I'm afraid I'm registering problems with the
update, however.

I just got gir1.2-gtk-3.0 through -proposed, and whereas it works as
intended in so far as I can now choose Ubuntu Mono in Gnome Terminal and
get the regular font face, it seemingly introduces a bug where gnome-
terminal crashes, when I try to select certain typefaces.

For instance, when I open up Preferences of go to the font selection
box, as soon as I click on e.g. "DejaVu Sans Mono", gnome-terminal just
closes. When I open it again, it's still using the previously set font.
The problem also occurs with "Inconsolata", but seemingly not with any
other fonts I have installed, whether fonts that ship with Ubuntu or
fonts I've installed on my own.

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1902109] Re: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted

[Bug Watch Updater]

** Bug watch added: Red Hat Bugzilla #1894485
   https://bugzilla.redhat.com/show_bug.cgi?id=1894485

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

Title:
  rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted

Status in GLibC:
  Confirmed
Status in glibc package in Ubuntu:
  New
Status in rsync package in Ubuntu:
  Triaged

Bug description:
  Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
  This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it 
returned "no" before.

  Steps to reproduce:

  # Emulate /proc not being mounted
  $ mount --bind / /mnt
  $ chroot /mnt rsync -a /bin/ls .
  rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not 
supported (95)
  rsync error: some files/attrs were not transferred (see previous errors) 
(code 3) at main.c(1330) [sender=3.2.3]

  I reported this issue upstream in
  https://github.com/WayneD/rsync/issues/109 but the rsync developer
  says it's a problem in libc, and it might well be.

  Simple C code to reproduce the problem without rsync:

  printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));

  If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
  when /proc isn't mounted, yet it succeeds if it is mounted.

  Python had a similar issue, and they ended up avoiding
  AC_CHECK_FUNC(lchmod) under Linux:

  https://bugs.python.org/issue34652
  
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140

  ```c
  if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
  fi
  ```

  So I'm not sure which package is causing the bug here. Should autoconf
  return false? Should libc implement lchown without the bug? Or should
  rsync skip lchmod under Linux, like python did?

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

-- 
Mailing list: https://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 1902109]

[Tom Hughes]

Also rsync in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1894485

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

Title:
  rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted

Status in GLibC:
  Confirmed
Status in glibc package in Ubuntu:
  New
Status in rsync package in Ubuntu:
  Triaged

Bug description:
  Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
  This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it 
returned "no" before.

  Steps to reproduce:

  # Emulate /proc not being mounted
  $ mount --bind / /mnt
  $ chroot /mnt rsync -a /bin/ls .
  rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not 
supported (95)
  rsync error: some files/attrs were not transferred (see previous errors) 
(code 3) at main.c(1330) [sender=3.2.3]

  I reported this issue upstream in
  https://github.com/WayneD/rsync/issues/109 but the rsync developer
  says it's a problem in libc, and it might well be.

  Simple C code to reproduce the problem without rsync:

  printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));

  If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
  when /proc isn't mounted, yet it succeeds if it is mounted.

  Python had a similar issue, and they ended up avoiding
  AC_CHECK_FUNC(lchmod) under Linux:

  https://bugs.python.org/issue34652
  
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140

  ```c
  if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
  fi
  ```

  So I'm not sure which package is causing the bug here. Should autoconf
  return false? Should libc implement lchown without the bug? Or should
  rsync skip lchmod under Linux, like python did?

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

-- 
Mailing list: https://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 1901026] Re: [GDB] No socket file connection support

[Matthias Klose]

from what I see, all these are unrelated to the bug fix, but problems
with the test infrastructure.

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

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

-- 
Mailing list: https://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 1902907] [NEW] Developer Options shows 'groovy-proposed' instead of 'hirsute-proposed' (software-properties-gtk on 21.04 Hirsute Hippo)

[Rudra Saraswat]

Public bug reported:

When testing Hirsute Hippo (21.04), I found that software-properties-gtk
shows 'groovy-proposed' instead of 'hirsute-proposed'. This is from a
live session in VirtualBox.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: software-properties-gtk 0.99.3
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.455
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Nov  4 16:16:14 2020
LiveMediaBuild: Ubuntu Unity 21.04
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

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

Title:
  Developer Options shows 'groovy-proposed' instead of 'hirsute-
  proposed' (software-properties-gtk on 21.04 Hirsute Hippo)

Status in software-properties package in Ubuntu:
  New

Bug description:
  When testing Hirsute Hippo (21.04), I found that software-properties-
  gtk shows 'groovy-proposed' instead of 'hirsute-proposed'. This is
  from a live session in VirtualBox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: software-properties-gtk 0.99.3
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Nov  4 16:16:14 2020
  LiveMediaBuild: Ubuntu Unity 21.04
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash

[Wladimir Mutel]

Lubuntu 18.04 is based on LXDE, not LXQt, and so it uses lightdm, not sddm.
greeter is lightdm-gtk-greeter, which causes traps in libglib like these :

ноя 04 16:50:48 user-desktop kernel: traps: lightdm-gtk-gre[673] trap int3 
ip:b6f929d0 sp:bf9e9e20 error:0 in libglib-2.0.so.0.5600.4[b6f44000+12e000]
ноя 04 16:50:52 user-desktop kernel: traps: lightdm-gtk-gre[736] trap int3 
ip:b6fe49d0 sp:bfbcfcd0 error:0 in libglib-2.0.so.0.5600.4[b6f96000+12e000]
ноя 04 16:50:54 user-desktop kernel: traps: lightdm-gtk-gre[798] trap int3 
ip:b70149d0 sp:bf839010 error:0 in libglib-2.0.so.0.5600.4[b6fc6000+12e000]
ноя 04 16:50:56 user-desktop kernel: traps: lightdm-gtk-gre[860] trap int3 
ip:b70669d0 sp:bf9a2f40 error:0 in libglib-2.0.so.0.5600.4[b7018000+12e000]
ноя 04 16:50:57 user-desktop kernel: traps: lightdm-gtk-gre[922] trap int3 
ip:b701a9d0 sp:bfe9c750 error:0 in libglib-2.0.so.0.5600.4[b6fcc000+12e000]
ноя 04 16:50:59 user-desktop kernel: traps: lightdm-gtk-gre[984] trap int3 
ip:b6fa19d0 sp:bfb4dcb0 error:0 in libglib-2.0.so.0.5600.4[b6f53000+12e000]

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

Title:
  upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes
  lightdm to crash

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Reproduction :
   take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock 
G41C-VS/G41M-VS3/G31M-S with Intel E3300/E3400, or Asrock P4I45GL with Intel 
Pentium4 2.40GHz) ;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor

  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

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

-- 
Mailing list: https://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 1900124] Re: Please merge klibc 2.0.8-1 (main) from Debian unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package klibc - 2.0.8-5ubuntu1

---
klibc (2.0.8-5ubuntu1) hirsute; urgency=medium

  * Merge with Debian; remaining changes:
- Keep Ubuntu specific debian/patches/cf-protection.patch

klibc (2.0.8-5) experimental; urgency=medium

  * alpha: Fix definitions of _NSIG and struct sigaction
  * ia64: Fix definition of struct sigaction

klibc (2.0.8-4) experimental; urgency=medium

  * signal: Note another reason to define _KLIBC_NEEDS_SA_RESTORER
  * signal: Add sysconfig setting to force SA_SIGINFO on
  * s390: Force SA_SIGINFO on and use rt_sigreturn
  * alpha: Force SA_SIGINFO on
  * sparc: Force SA_SIGINFO on

klibc (2.0.8-3) experimental; urgency=medium

  * s390: Define __sigreturn() on both s390 and s390x
  * Revert "alpha: Set sa_restorer for signals and disable executable stack"
  * alpha: Pass restorer to rt_sigaction() and disable executable stack

klibc (2.0.8-2) experimental; urgency=medium

  * {alpha,s390,sparc}: Set sa_restorer for signals and disable executable
stack

 -- Matthias Klose   Mon, 02 Nov 2020 13:12:53 +0100

** Changed in: klibc (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 klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1900124

Title:
  Please merge klibc 2.0.8-1 (main) from Debian unstable (main)

Status in klibc package in Ubuntu:
  Fix Released

Bug description:
  Please merge klibc 2.0.8-1 (main) from Debian unstable (main)

  Most of the Ubuntu patches have been accepted upstream.

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

-- 
Mailing list: https://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 1902898] Re: power-button action inconsistent between user session and greeter

[Iain Lane]

Issue here I think is that we use per-session overrides for the majority
of our Ubuntu customisations, and these don't apply to greeter sessions.

** Tags added: rls-hh-incoming

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Focal:
  Confirmed
Status in ubuntu-settings source package in Groovy:
  New
Status in ubuntu-settings source package in Hirsute:
  New

Bug description:
  When a user is logged in to the Ubuntu desktop, a power button event
  will cause the user to be prompted to choose if they'd like to proceed
  with a shutdown. However, if the system is sitting at a greeter
  screen, a power button event will instead attempt a suspend w/o
  prompting. This is due to a different set of defaults for the greeter
  and the user:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

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

-- 
Mailing list: https://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 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs

[Sami Pietila]

** Description changed:

- I have asked question in askubuntu about "Too many levels of symbolic
+ I have asked question at askubuntu about "Too many levels of symbolic
  links” error when trying to use systemd to mount sshfs
  (https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic-
  links-error-when-using-systemd)
  
  I have not got any responses, so I am submitting a bug report. If this
  is not a bug, please advice how to mount sshfs share with systemd.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 16:17:04 2020
  InstallationDate: Installed on 2019-11-03 (367 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81H1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago)
  dmi.bios.date: 08/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8PCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 530S-14ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
  dmi.product.family: ideapad 530S-14ARR
  dmi.product.name: 81H1
  dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
  dmi.product.version: Lenovo ideapad 530S-14ARR
  dmi.sys.vendor: LENOVO

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

Title:
  "Too many levels of symbolic links” error when using systemd to mount
  sshfs

Status in systemd package in Ubuntu:
  New

Bug description:
  I have asked question at askubuntu about "Too many levels of symbolic
  links” error when trying to use systemd to mount sshfs
  (https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic-
  links-error-when-using-systemd)

  I have not got any responses, so I am submitting a bug report. If this
  is not a bug, please advice how to mount sshfs share with systemd.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 16:17:04 2020
  InstallationDate: Installed on 2019-11-03 (367 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81H1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago)
  dmi.bios.date: 08/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8PCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 530S-14ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
  dmi.product.family: ideapad 530S-14ARR
  dmi.product.name: 81H1
  dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
  dmi.product.version: Lenovo ideapad 530S-14ARR
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1902899] [NEW] Color management is not quite good

[Flávio Vivório Salles]

Public bug reported:

While attempting to work with software like Figma, Inskcape and Gimp I
noticed that the screen I have doesn't show colors like in my iMac or in
WIndows. When I plug the same display on my laptop running Ubuntu 20.04
the colors just looks very opaque and desaturated. I looked on the web
for a tool to fix this but it just doesn't exist. I think this could be
a bug or a a problem with drivers. But theres no proprietary drivers for
this machine. The open source Intel drivers are just terrible. I suggest
Ubuntu developers include potentiometers to manage color saturation,
contrast, brightness and temperature under the "Color" tab on Ubuntu
settings pannel. When I go to the color section of the settings pannel
it only allows me to chose a color profile but I can't even adjust color
settings. I really wish Linux systems be more usable when it comes to
work with graphic software in the future.

My system info:

Lenovo Ideapad s145
Ubuntu 20.04.1 LTS
Processor: Intel® Core™ i3-8130U CPU @ 2.20GHz × 4 
Graphics: Mesa Intel® UHD Graphics 620 (KBL GT2)
GNOME version: 3.36.3
X11
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 12:08:10 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: darling-mach, 0.1, 5.4.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:3fdf]
InstallationDate: Installed on 2020-10-14 (21 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81XM
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=a08ea31a-d24d-4a85-b391-c1950060f906 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 10/12/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: CSCN10WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15IKB
dmi.modalias: 
dmi:bvnLENOVO:bvrCSCN10WW:bd10/12/2019:svnLENOVO:pn81XM:pvrLenovoIdeaPadS145-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IKB:
dmi.product.family: IdeaPad S145-15IKB
dmi.product.name: 81XM
dmi.product.sku: LENOVO_MT_81XM_BU_idea_FM_IdeaPad S145-15IKB
dmi.product.version: Lenovo IdeaPad S145-15IKB
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.103+git2011040630.5dea8f~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2011040730.58e708~oibaf~f
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug focal third-party-packages 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/1902899

Title:
  Color management is not quite good

Status in xorg package in Ubuntu:
  New

Bug description:
  While attempting to work with software like Figma, Inskcape and Gimp I
  noticed that the screen I have doesn't show colors like in my iMac or
  in WIndows. When I plug the same display on my laptop running Ubuntu
  20.04 the colors just looks very opaque and desaturated. I looked on
  the web for a tool to fix this but it just doesn't exist. I think this
  could be a bug or a a problem 

[Touch-packages] [Bug 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash

[Wladimir Mutel]

** Description changed:

  Reproduction :
-  take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock 
G41C-VS/G31M-S with Intel E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) 
;
+  take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock 
G41C-VS/G41M-VS3/G31M-S with Intel E3300/E3400, or Asrock P4I45GL with Intel 
Pentium4 2.40GHz) ;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor
  
  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

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

Title:
  upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes
  lightdm to crash

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Reproduction :
   take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock 
G41C-VS/G41M-VS3/G31M-S with Intel E3300/E3400, or Asrock P4I45GL with Intel 
Pentium4 2.40GHz) ;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor

  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

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

-- 
Mailing list: https://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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Gunnar Hjalmarsson]

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

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1902898] [NEW] power-button action inconsistent between user session and greeter

[dann frazier]

Public bug reported:

When a user is logged in to the Ubuntu desktop, a power button event
will cause the user to be prompted to choose if they'd like to proceed
with a shutdown. However, if the system is sitting at a greeter screen,
a power button event will instead attempt a suspend w/o prompting. This
is due to a different set of defaults for the greeter and the user:

For a logged-in desktop user, they
see:

$ gsettings get org.gnome.settings-daemon.plugins.power
power-button-action 'interactive'

But the gdm user sees:
$ sudo machinectl shell gdm@ /bin/bash
Connected to the local host. Press ^] three times within 1s to exit session.
gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action
'suspend'

Changing the gdm user's setting to "interactive" using gsettings causes
the greeter to begin prompting, consistent with the logged in user
experience.

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

** Affects: ubuntu-settings (Ubuntu Focal)
 Importance: Undecided
 Status: Confirmed

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

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

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

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

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

** Changed in: ubuntu-settings (Ubuntu Focal)
   Status: New => Confirmed

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Focal:
  Confirmed
Status in ubuntu-settings source package in Groovy:
  New
Status in ubuntu-settings source package in Hirsute:
  New

Bug description:
  When a user is logged in to the Ubuntu desktop, a power button event
  will cause the user to be prompted to choose if they'd like to proceed
  with a shutdown. However, if the system is sitting at a greeter
  screen, a power button event will instead attempt a suspend w/o
  prompting. This is due to a different set of defaults for the greeter
  and the user:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

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

-- 
Mailing list: https://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 1902760] Re: Please merge linker bugfix into Ubuntu 20.04 LTS

[Brian Murray]

** Tags added: rls-ff-incoming

** Tags added: focal

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

Title:
  Please merge linker bugfix into Ubuntu 20.04 LTS

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  New

Bug description:
  Binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=26262
  fixes a problem that Intel Fortran is running into when using the -ipo
  option to request link time optimization. Please merge the fix into
  Ubuntu 20.04 LTS

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

-- 
Mailing list: https://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 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash

[Wladimir Mutel]

I found it happens on non-Intel CPUs and VGAs as well.
Like, Gigabyte M61PME-S2 with Sempron LE-1200

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

Title:
  upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes
  lightdm to crash

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Reproduction :
   take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock 
G41C-VS/G31M-S with Intel E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) 
;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor

  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

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

-- 
Mailing list: https://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 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash

[Sebastien Bacher]

Thank you for your bug report, what lightdm greeter do you use? It's
similar to bug #1902879. Also doesn't lubuntu use sddm as its login
manager?

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

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

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

Title:
  upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes
  lightdm to crash

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Reproduction :
   take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock 
G41C-VS/G31M-S with Intel E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) 
;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor

  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

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

-- 
Mailing list: https://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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Gunnar Hjalmarsson]

@Darko: Yeah, it's indeed different compared to focal. But as was stated
on the upstream issue, it's an intentional design change, and probably
better for most use cases given this gtk fix.

Thanks for verifying!

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1901026] Re: [GDB] No socket file connection support

[Luis]

What exactly are the regressions? I checked the logs and I don't really
know how to parse them. They don't seem to be GDB tests, but rather some
other components' tests.

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

-- 
Mailing list: https://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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Ladislav Petrus]

@seb128 , upstream (pulseaudio) asks whether it would be possible to
test an Ubuntu build of the pulseaudio 13.99.3 package by us.  Are you
able to provide a 13.99.3 pulseaudio packages for us to test?

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

Title:
  [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash

[Wladimir Mutel]

** Description changed:

  Reproduction :
-  take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS/G31M-S with Intel 
E3300) ;
+  take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS/G31M-S with Intel 
E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) ;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor
  
  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

** Description changed:

  Reproduction :
-  take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS/G31M-S with Intel 
E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) ;
+  take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock 
G41C-VS/G31M-S with Intel E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) 
;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor
  
  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

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

Title:
  upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes
  lightdm to crash

Status in systemd package in Ubuntu:
  New

Bug description:
  Reproduction :
   take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock 
G41C-VS/G31M-S with Intel E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) 
;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor

  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

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

-- 
Mailing list: https://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 1902891] [NEW] "Too many levels of symbolic links” error when using systemd to mount sshfs

[Sami Pietila]

Public bug reported:

I have asked question in askubuntu about "Too many levels of symbolic
links” error when trying to use systemd to mount sshfs
(https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic-
links-error-when-using-systemd)

I have not got any responses, so I am submitting a bug report. If this
is not a bug, please advice how to mount sshfs share with systemd.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 16:17:04 2020
InstallationDate: Installed on 2019-11-03 (367 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 81H1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago)
dmi.bios.date: 08/17/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 8PCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 530S-14ARR
dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
dmi.product.family: ideapad 530S-14ARR
dmi.product.name: 81H1
dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
dmi.product.version: Lenovo ideapad 530S-14ARR
dmi.sys.vendor: LENOVO

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


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

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

Title:
  "Too many levels of symbolic links” error when using systemd to mount
  sshfs

Status in systemd package in Ubuntu:
  New

Bug description:
  I have asked question in askubuntu about "Too many levels of symbolic
  links” error when trying to use systemd to mount sshfs
  (https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic-
  links-error-when-using-systemd)

  I have not got any responses, so I am submitting a bug report. If this
  is not a bug, please advice how to mount sshfs share with systemd.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 16:17:04 2020
  InstallationDate: Installed on 2019-11-03 (367 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81H1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago)
  dmi.bios.date: 08/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8PCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 530S-14ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
  dmi.product.family: ideapad 530S-14ARR
  dmi.product.name: 81H1
  dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
  dmi.product.version: Lenovo ideapad 530S-14ARR
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1901026] Autopkgtest regression report (gdb/8.1.1-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gdb (8.1.1-0ubuntu1) for bionic have 
finished running.
The following regressions have been reported in tests triggered by the package:

linux-raspi2-5.3/5.3.0-1036.38 (armhf)
apport/2.20.9-0ubuntu7.18 (i386)
plasma-workspace/unknown (armhf)
python3.6/unknown (armhf)
python3.7/unknown (armhf, amd64)
linux-kvm/unknown (amd64)
linux-hwe-5.4/5.4.0-52.57~18.04.1 (armhf)
linux-hwe-5.0/unknown (amd64)
linux-hwe-5.0/5.0.0-62.67 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#gdb

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

-- 
Mailing list: https://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 1902225] Autopkgtest regression report (gdb/8.1.1-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gdb (8.1.1-0ubuntu1) for bionic have 
finished running.
The following regressions have been reported in tests triggered by the package:

linux-raspi2-5.3/5.3.0-1036.38 (armhf)
apport/2.20.9-0ubuntu7.18 (i386)
plasma-workspace/unknown (armhf)
python3.6/unknown (armhf)
python3.7/unknown (armhf, amd64)
linux-kvm/unknown (amd64)
linux-hwe-5.4/5.4.0-52.57~18.04.1 (armhf)
linux-hwe-5.0/unknown (amd64)
linux-hwe-5.0/5.0.0-62.67 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#gdb

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  SRU: update gdb 8.1.1 for 18.04 LTS

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  gdb 8.1.1 is a minor bug fix release for 8.1. Some of the issues fixed
  in 8.1.1 are already fixed in the branch update in 8.1-0ubuntu3:

   * gdb 8.1.1 release.
  This is a minor corrective release over GDB 8.1, fixing following issues:
  - PR gdb/23028 (inconsistent disassemble of vcvtpd2dq)
  - PR gdb/23053 (Fix -D_GLIBCXX_DEBUG gdb-add-index regression)
  - PR gdb/23127 ([AArch64] GDB cannot be used for debugging software that
uses high Virtual Addresses)
  - PR server/23158 (gdbserver no longer functional on Windows)
  - PR breakpoints/23210 ([8.1/8.2 Regression] Bogus Breakpoint address
adjusted from 0xf7fe7dd3 to 0xf7fe7dd3)
  Already fixed in 8.1-0ubuntu3:
  - PR gdb/22824 (misleading description of new rbreak Python function in
GDB 8.1 NEWS file)
  - PR gdb/22849 (ctrl-c doesn't work in extended-remote)
  - PR gdb/22907 ([Regression] gdbserver doesn't work with filename-only
binaries).
* Allow remote debugging over a Unix local domain socket. LP: #1901026.

  This minor version update fixes four upstream issues (not counting the
  Windows specific issue), plus allows remote debugging over a Unix
  local domain socket., a patch taken from the 8.2 development.

  Validation: The tests run during build time are passing, and the
  remote debugging is checked to be working (no automated test case).

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

-- 
Mailing list: https://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 1901026] Re: [GDB] No socket file connection support

[Luis]

Nevermind. I double checked the package I was using, and turns out I
used an old package without the socket patch (the non-temporal sorting
of packages threw me off).

Testing this on x86-64, I can now see the following:

GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set debug remote 1
(gdb) tar rem /var/run/dbus/system_bus_socket
Remote debugging using /var/run/dbus/system_bus_socket
Sending packet: 
$qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Remote
 communication error.  Target disconnected.: Connection reset by peer.

As opposed to the previous error message. So this looks good! Thanks for
considering this backport.

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

-- 
Mailing list: https://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 1901026] Re: [GDB] No socket file connection support

[Luis]

I gave this a try and, unfortunately, it didn't work right. It seems
there may be more patches require to make this work. I'm investigating
what those are.

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

-- 
Mailing list: https://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 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash

[Wladimir Mutel]

** Description changed:

  Reproduction :
-  take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS with Intel E3300) ;
-  install Lubuntu 18.04 i386 on it ;
-  install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
-  reboot and watch black screen with blinking text cursor
+  take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS/G31M-S with Intel 
E3300) ;
+  install Lubuntu 18.04 i386 on it ;
+  install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
+  reboot and watch black screen with blinking text cursor
  
  Fix :
-  switch into text console or log in as sudo-capable user over the network
-  look at lightdm crashes in dmesg
-  download past version of systemd packages (237-3ubuntu10.42)
-  install them by dpkg
-  reboot and enjoy your graphic screen again
+  switch into text console or log in as sudo-capable user over the network
+  look at lightdm crashes in dmesg
+  download past version of systemd packages (237-3ubuntu10.42)
+  install them by dpkg
+  reboot and enjoy your graphic screen again

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

Title:
  upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes
  lightdm to crash

Status in systemd package in Ubuntu:
  New

Bug description:
  Reproduction :
   take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS/G31M-S with Intel 
E3300) ;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor

  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

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

-- 
Mailing list: https://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 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)

[Alkis Georgopoulos]

Thank you Łukasz, I filed it in LP: #1902879.

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

Title:
  memlock setting in systemd (pid 1) too low for containers (bionic)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]
  * Since systemd commit fb3ae275cb ("main: bump RLIMIT_NOFILE for the root 
user substantially") [https://github.com/systemd/systemd/commit/fb3ae275cb], 
which is present in Bionic, the memlock ulimit value was bumped to 16M. It's an 
adjustable limit, but the default (in previous Ubuntu releases/systemd 
versions) was really small.
  * Although bumping this value was a good thing, 16M is not enough and we can 
see failures on mlock'ed allocations on Bionic, like the one hereby reported by 
Kees or the recent introduced cryptsetup build failures (due to PPA builder 
updates to Bionic) - see https://bugs.launchpad.net/bugs//1891473.

  * It's especially harmful in containers to have such "small" limit, so
  we are hereby SRUing a more recent bump from upstream systemd, in the
  form of commit 91cfdd8d29 ("core: bump mlock ulimit to 64Mb")
  [https://github.com/systemd/systemd/commit/91cfdd8d29]. Latest Ubuntu
  releases, like Focal and subsequent ones, already include this patch
  so effectively we're putting Bionic on-par with newer releases.

  * A discussion about this topic (leading to this SRU) is present in
  ubuntu-devel ML: https://lists.ubuntu.com/archives/ubuntu-
  devel/2020-September/041159.html.

  [Test Case]
  * The straightforward test is to just look "ulimit -l" and "ulimit -Hl" in a 
current Bionic system, and then install an updated version with the hereby 
proposed SRU to see such limit bump from 16M to 64M (after a reboot) - a 
version containing this fix is available at my PPA as of 2020-09-10 [0] (likely 
to be deleted in next month or so).

  * A more interesting test is to run a Focal container in a current
  Bionic system and try to build the cryptsetup package - it'll fail in
  some tests. After updating the host (Bionic) systemd to include the
  mlock bump patch, the build succeeds in the Focal container.

  [Regression Potential]
  * Since it's a simple bump and it makes Bionic behave like Focal, I don't 
foresee regressions. One potential issue would be if some users rely on the 
lower default limit (16M) and this value is bumped by a package update, but 
that could be circumvented by setting a lower limit in limits.conf. The 
benefits for such bump are likely much bigger than any "regression" caused for 
users relying on such default limit.

  
  [0] https://launchpad.net/~gpiccoli/+archive/ubuntu/test1830746

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

-- 
Mailing list: https://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 1902871] [NEW] upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash

[Wladimir Mutel]

Public bug reported:

Reproduction :
 take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS with Intel E3300) ;
 install Lubuntu 18.04 i386 on it ;
 install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
 reboot and watch black screen with blinking text cursor

Fix :
 switch into text console or log in as sudo-capable user over the network
 look at lightdm crashes in dmesg
 download past version of systemd packages (237-3ubuntu10.42)
 install them by dpkg
 reboot and enjoy your graphic screen again

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

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

Title:
  upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes
  lightdm to crash

Status in systemd package in Ubuntu:
  New

Bug description:
  Reproduction :
   take a bog-standard system with Intel CPU and Intel graphics (mobo like 
Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS with Intel E3300) ;
   install Lubuntu 18.04 i386 on it ;
   install all latest upgrades including systemd packages of version 
237-3ubuntu10.43 ;
   reboot and watch black screen with blinking text cursor

  Fix :
   switch into text console or log in as sudo-capable user over the network
   look at lightdm crashes in dmesg
   download past version of systemd packages (237-3ubuntu10.42)
   install them by dpkg
   reboot and enjoy your graphic screen again

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

-- 
Mailing list: https://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 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)

[Łukasz Zemczak]

Hey Alkis! Can you please fill in a new bug report with all the detailed
information and tag it wit 'regression-update'? Thank you!

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

Title:
  memlock setting in systemd (pid 1) too low for containers (bionic)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]
  * Since systemd commit fb3ae275cb ("main: bump RLIMIT_NOFILE for the root 
user substantially") [https://github.com/systemd/systemd/commit/fb3ae275cb], 
which is present in Bionic, the memlock ulimit value was bumped to 16M. It's an 
adjustable limit, but the default (in previous Ubuntu releases/systemd 
versions) was really small.
  * Although bumping this value was a good thing, 16M is not enough and we can 
see failures on mlock'ed allocations on Bionic, like the one hereby reported by 
Kees or the recent introduced cryptsetup build failures (due to PPA builder 
updates to Bionic) - see https://bugs.launchpad.net/bugs//1891473.

  * It's especially harmful in containers to have such "small" limit, so
  we are hereby SRUing a more recent bump from upstream systemd, in the
  form of commit 91cfdd8d29 ("core: bump mlock ulimit to 64Mb")
  [https://github.com/systemd/systemd/commit/91cfdd8d29]. Latest Ubuntu
  releases, like Focal and subsequent ones, already include this patch
  so effectively we're putting Bionic on-par with newer releases.

  * A discussion about this topic (leading to this SRU) is present in
  ubuntu-devel ML: https://lists.ubuntu.com/archives/ubuntu-
  devel/2020-September/041159.html.

  [Test Case]
  * The straightforward test is to just look "ulimit -l" and "ulimit -Hl" in a 
current Bionic system, and then install an updated version with the hereby 
proposed SRU to see such limit bump from 16M to 64M (after a reboot) - a 
version containing this fix is available at my PPA as of 2020-09-10 [0] (likely 
to be deleted in next month or so).

  * A more interesting test is to run a Focal container in a current
  Bionic system and try to build the cryptsetup package - it'll fail in
  some tests. After updating the host (Bionic) systemd to include the
  mlock bump patch, the build succeeds in the Focal container.

  [Regression Potential]
  * Since it's a simple bump and it makes Bionic behave like Focal, I don't 
foresee regressions. One potential issue would be if some users rely on the 
lower default limit (16M) and this value is bumped by a package update, but 
that could be circumvented by setting a lower limit in limits.conf. The 
benefits for such bump are likely much bigger than any "regression" caused for 
users relying on such default limit.

  
  [0] https://launchpad.net/~gpiccoli/+archive/ubuntu/test1830746

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

-- 
Mailing list: https://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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Darko Veberic]

i tested it after installing libgtk-3-0 libgtk-3-common from proposed. i
can confirm that the gnome-terminal settings custom font now shows only
"ubuntu mono" when "ubuntu" is typed into the search box and therefore
solves the issue.

nevertheless, note that this is still different than what we see in
focal, namely typing "ubuntu" into the search shows ubuntu mono
{regular, italics, bold, bold-italics}. it's probably fine to allow
selecting only the regular font since italics is useless as a terminal
font and bold is used for emphasis anyway...

packages installed: libgtk-3-common (3.24.23-1ubuntu1.1) over
(3.24.23-1ubuntu1), libgtk-3-0:amd64 (3.24.23-1ubuntu1.1) over
(3.24.23-1ubuntu1)

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

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1902538] Re: Every cycle python-apt breaks until updated for the new distro codename

[Julian Andres Klode]

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

Dupe of 1727470. FWIW, python-apt 2.1.15 does not hard code codenames
anymore, so won't have this issue.

** Changed in: python-apt (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: python-apt (Ubuntu)
   Status: Invalid => Fix Committed

** This bug has been marked a duplicate of bug 1727470
   [RFE] Automatically update the Ubuntu version strings in python-apt

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

Title:
  Every cycle python-apt breaks until updated for the new distro
  codename

Status in Ubuntu MATE:
  New
Status in python-apt package in Ubuntu:
  Fix Committed
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  The problem is currently happening in hirsute (fixed with the python-
  apt in proposed, software-properties fails to start due a python-apt
  error

File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
605, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
  raise NoDistroTemplateException(
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/hirsute

  Could we try to handle the missing codename in a way that doesn't make
  python-apt users blow up every cycle until we play catching up?

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

-- 
Mailing list: https://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 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt

[Julian Andres Klode]

Not syncing this, want to get the existing upload migrated first. Which
is Stuck on apt-clone regression.

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

Title:
  [RFE] Automatically update the Ubuntu version strings in python-apt

Status in Ubuntu Translations:
  Triaged
Status in python-apt package in Ubuntu:
  Fix Committed

Bug description:
  Every time there is a new Ubuntu release, some strings need to be
  manually translated although the only thing that is changing is the
  Ubuntu version and code name. Please, consider updating these strings
  automatically based on a translated template. It would help many
  translators.

  These strings are:
  Ubuntu xx.yy 'Code Name'
  Cdrom with Ubuntu xx.yy 'Code Name'

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

-- 
Mailing list: https://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 1662244] Re: lightdm causes all greeters to fail to start

[Alkis Georgopoulos]

What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1662244/comments/14 avoids the segfault:

* soft memlock 262144
* hard memlock 262144

Should all lightdm users manually put that in limits.conf, or should we
expect some update?

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

Title:
  lightdm causes all greeters to fail to start

Status in Light Display Manager:
  Invalid
Status in LightDM GTK+ Greeter:
  Invalid
Status in lightdm package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  lightdm is failing to start. Best guess is because of unity-session-
  manager. This is from .xsession-errors.

  dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
  upstart: click-user-hooks main process (4028) terminated with status 1
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon respawning too fast, stopped
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application respawning too fast, stopped
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  upstart: dbus main process (4023) killed by TERM signal

  
  I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've 
reverted kernel versions and that didn't work. I've moved aside $HOME/.cache 
and that didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 10:21:29 2017
  InstallationDate: Installed on 2015-07-20 (566 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago)

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

-- 
Mailing list: https://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 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)

[Alkis Georgopoulos]

What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1662244/comments/14 avoids the segfault:

* soft memlock 262144
* hard memlock 262144

Should all lightdm users manually put that in limits.conf, or should we
expect some update?

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

Title:
  memlock setting in systemd (pid 1) too low for containers (bionic)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]
  * Since systemd commit fb3ae275cb ("main: bump RLIMIT_NOFILE for the root 
user substantially") [https://github.com/systemd/systemd/commit/fb3ae275cb], 
which is present in Bionic, the memlock ulimit value was bumped to 16M. It's an 
adjustable limit, but the default (in previous Ubuntu releases/systemd 
versions) was really small.
  * Although bumping this value was a good thing, 16M is not enough and we can 
see failures on mlock'ed allocations on Bionic, like the one hereby reported by 
Kees or the recent introduced cryptsetup build failures (due to PPA builder 
updates to Bionic) - see https://bugs.launchpad.net/bugs//1891473.

  * It's especially harmful in containers to have such "small" limit, so
  we are hereby SRUing a more recent bump from upstream systemd, in the
  form of commit 91cfdd8d29 ("core: bump mlock ulimit to 64Mb")
  [https://github.com/systemd/systemd/commit/91cfdd8d29]. Latest Ubuntu
  releases, like Focal and subsequent ones, already include this patch
  so effectively we're putting Bionic on-par with newer releases.

  * A discussion about this topic (leading to this SRU) is present in
  ubuntu-devel ML: https://lists.ubuntu.com/archives/ubuntu-
  devel/2020-September/041159.html.

  [Test Case]
  * The straightforward test is to just look "ulimit -l" and "ulimit -Hl" in a 
current Bionic system, and then install an updated version with the hereby 
proposed SRU to see such limit bump from 16M to 64M (after a reboot) - a 
version containing this fix is available at my PPA as of 2020-09-10 [0] (likely 
to be deleted in next month or so).

  * A more interesting test is to run a Focal container in a current
  Bionic system and try to build the cryptsetup package - it'll fail in
  some tests. After updating the host (Bionic) systemd to include the
  mlock bump patch, the build succeeds in the Focal container.

  [Regression Potential]
  * Since it's a simple bump and it makes Bionic behave like Focal, I don't 
foresee regressions. One potential issue would be if some users rely on the 
lower default limit (16M) and this value is bumped by a package update, but 
that could be circumvented by setting a lower limit in limits.conf. The 
benefits for such bump are likely much bigger than any "regression" caused for 
users relying on such default limit.

  
  [0] https://launchpad.net/~gpiccoli/+archive/ubuntu/test1830746

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

-- 
Mailing list: https://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 1662244] Re: lightdm causes all greeters to fail to start

[Alkis Georgopoulos]

Hi, a recent systemd update in 18.04 makes slick-greeter segfault.
So all Ubuntu MATE 18.04 users now get black screens instead of lightdm.

It's related to memory limits so I'm cross-referencing it here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746

This didn't help:

[LightDM]
lock-memory=false

Can I put something in /etc/security/limits.conf to see if it helps?

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

Title:
  lightdm causes all greeters to fail to start

Status in Light Display Manager:
  Invalid
Status in LightDM GTK+ Greeter:
  Invalid
Status in lightdm package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  lightdm is failing to start. Best guess is because of unity-session-
  manager. This is from .xsession-errors.

  dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
  upstart: click-user-hooks main process (4028) terminated with status 1
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon respawning too fast, stopped
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application respawning too fast, stopped
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  upstart: dbus main process (4023) killed by TERM signal

  
  I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've 
reverted kernel versions and that didn't work. I've moved aside $HOME/.cache 
and that didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 10:21:29 2017
  InstallationDate: Installed on 2015-07-20 (566 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago)

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

-- 
Mailing list: https://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 1902538] Re: Every cycle python-apt breaks until updated for the new distro codename

[corrado venturini]

Same problem on Ubuntu installed from Ubuntu 21.04 "Hirsute Hippo" -
Alpha amd64 (20201104)

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

Title:
  Every cycle python-apt breaks until updated for the new distro
  codename

Status in Ubuntu MATE:
  New
Status in python-apt package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  The problem is currently happening in hirsute (fixed with the python-
  apt in proposed, software-properties fails to start due a python-apt
  error

File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
605, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
  raise NoDistroTemplateException(
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/hirsute

  Could we try to handle the missing codename in a way that doesn't make
  python-apt users blow up every cycle until we play catching up?

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

-- 
Mailing list: https://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 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)

[Alkis Georgopoulos]

Hi, this update makes slick-greeter segfault, so Ubuntu MATE 18.04 users
doing normal updates now get a black screen with a flicking cursor.

A temporary workaround is to enable autologin in
/etc/lightdm/lightdm.conf:

[Seat:*]
autologin-guest=false
autologin-user=administrator
autologin-user-timeout=0

*** What would be a proper fix for this? ***

A related discussion about memory limits and lightdm issues exists in this bug 
report:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1662244

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

Title:
  memlock setting in systemd (pid 1) too low for containers (bionic)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]
  * Since systemd commit fb3ae275cb ("main: bump RLIMIT_NOFILE for the root 
user substantially") [https://github.com/systemd/systemd/commit/fb3ae275cb], 
which is present in Bionic, the memlock ulimit value was bumped to 16M. It's an 
adjustable limit, but the default (in previous Ubuntu releases/systemd 
versions) was really small.
  * Although bumping this value was a good thing, 16M is not enough and we can 
see failures on mlock'ed allocations on Bionic, like the one hereby reported by 
Kees or the recent introduced cryptsetup build failures (due to PPA builder 
updates to Bionic) - see https://bugs.launchpad.net/bugs//1891473.

  * It's especially harmful in containers to have such "small" limit, so
  we are hereby SRUing a more recent bump from upstream systemd, in the
  form of commit 91cfdd8d29 ("core: bump mlock ulimit to 64Mb")
  [https://github.com/systemd/systemd/commit/91cfdd8d29]. Latest Ubuntu
  releases, like Focal and subsequent ones, already include this patch
  so effectively we're putting Bionic on-par with newer releases.

  * A discussion about this topic (leading to this SRU) is present in
  ubuntu-devel ML: https://lists.ubuntu.com/archives/ubuntu-
  devel/2020-September/041159.html.

  [Test Case]
  * The straightforward test is to just look "ulimit -l" and "ulimit -Hl" in a 
current Bionic system, and then install an updated version with the hereby 
proposed SRU to see such limit bump from 16M to 64M (after a reboot) - a 
version containing this fix is available at my PPA as of 2020-09-10 [0] (likely 
to be deleted in next month or so).

  * A more interesting test is to run a Focal container in a current
  Bionic system and try to build the cryptsetup package - it'll fail in
  some tests. After updating the host (Bionic) systemd to include the
  mlock bump patch, the build succeeds in the Focal container.

  [Regression Potential]
  * Since it's a simple bump and it makes Bionic behave like Focal, I don't 
foresee regressions. One potential issue would be if some users rely on the 
lower default limit (16M) and this value is bumped by a package update, but 
that could be circumvented by setting a lower limit in limits.conf. The 
benefits for such bump are likely much bigger than any "regression" caused for 
users relying on such default limit.

  
  [0] https://launchpad.net/~gpiccoli/+archive/ubuntu/test1830746

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

-- 
Mailing list: https://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 1901090] Re: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory

[Launchpad Bug Tracker]

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

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

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

Title:
  run-parts: failed to stat component /etc/network/if-post-down.d/avahi-
  daemon: No such file or directory

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  avahi-daemon 0.7-4ubuntu7 installs a symlink /etc/network/if-post-
  down.d/avahi-daemon -> ../if-up.d/avahi-daemon but doesn't install the
  symlink target /etc/network/if-up.d/avahi-daemon

  That makes ifdown complain:

  $ sudo ifdown enp2s0f3
  run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: 
No such file or directory

  The problem only occurs if avahi-daemon is installed from scratch; if
  it is upgraded from older versions, the missing file is still there
  according to this line in /var/lib/dpkg/status:

  /etc/network/if-up.d/avahi-daemon 6dbf1a91ab420a99d1205972d6401e67
  obsolete

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

-- 
Mailing list: https://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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Johan Segerstedt]

I have reported the issue upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1030
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030

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

Title:
  [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1902538] Re: Ubuntu Mate 21.04 Software & Updates fails to run

[Sebastien Bacher]

The issue should be fixed with this update

https://launchpad.net/ubuntu/+source/python-apt/2.1.3ubuntu3

it does sound like we should do better than having software-properties
bail out every start of cycle until python-apt is updated, I'm going to
repurpose the bug for that issue

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu)
   Status: New => Fix Committed

** Summary changed:

- Ubuntu Mate 21.04 Software & Updates fails to run
+ Every cycle python-apt breaks until updated for the new distro codename

** Description changed:

- When trying to open "Software & Updates" it shows in the dock, but fails
- to run. I realize that now I am unable to restore packages that were
- disabled during the install.
+ The problem is currently happening in hirsute (fixed with the python-apt
+ in proposed, software-properties fails to start due a python-apt error
+ 
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
605, in reload_sourceslist
+ self.distro.get_sources(self.sourceslist)
+   File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
+ raise NoDistroTemplateException(
+ aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/hirsute
+ 
+ Could we try to handle the missing codename in a way that doesn't make
+ python-apt users blow up every cycle until we play catching up?

** Changed in: python-apt (Ubuntu)
   Status: Fix Committed => Confirmed

** Tags added: rls-hh-incoming

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

Title:
  Every cycle python-apt breaks until updated for the new distro
  codename

Status in Ubuntu MATE:
  New
Status in python-apt package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  The problem is currently happening in hirsute (fixed with the python-
  apt in proposed, software-properties fails to start due a python-apt
  error

File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
605, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
  raise NoDistroTemplateException(
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/hirsute

  Could we try to handle the missing codename in a way that doesn't make
  python-apt users blow up every cycle until we play catching up?

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

-- 
Mailing list: https://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 1902853] [NEW] Failure to create core GL context with llvmpipe when using GLX_ARB_context_flush_control

[Marc]

Public bug reported:

When using llvmpipe on the non-HWE xorg version GL core context creation
fails when using "GLX_ARB_context_flush_control" even though the driver
reports that the extension is supported.

Apologies if xorg is the wrong package here, this could be a libgl1
-mesa-dri/glx bug instead, it's unclear to me where the fault lies in
the graphics stack.

xserver-common:
  Installed: 2:1.19.6-1ubuntu4.7
  Candidate: 2:1.19.6-1ubuntu4.7
linux-generic:
  Installed: 4.15.0.122.109
  Candidate: 4.15.0.122.109

Steps to reproduce on Ubuntu Server:
1. Install Ubuntu 18.04 server edition in a VM, or other hardware without a 
physical graphics device
2. Install the desktop with "sudo apt install ubuntu-desktop"
3. Reboot
4. Compile and run the attached file

Steps to reproduce on Ubuntu Desktop:
1. Install Ubuntu 18.04 desktop edition in a VM, or other hardware without a 
physical graphics device
2. Remove the HWE packages with "apt remove *-hwe-18.04" and then "apt install 
xserver-xorg-core ubuntu-desktop xserver-xorg xserver-xorg-video-all 
xserver-xorg-input-all libgl1-mesa-dri libgl1-mesa-glx" to get things back to 
normal
3. Reboot
4. Compile and run the attached file

Both examples produce:
"Could not create GL context: BadValue (integer parameter out of range for 
operation)"

For both cases, upgrading to (or staying on) the HWE stack allows
creating the core 3.3 context successfully.


Debugging:

I've stepped all the way into libxcb for the context creation at
src/glx.c:3258, with a call to
"xcb_glx_create_context_attribs_arb_checked", but haven't managed to
link this up to a received request in another process. The request is
rejected with BadValue.

BadVaue in this instance could mean one of two things according to GL spec:
1. The GLX_RENDER_TYPE attribute is invalid
2. An attribute or it's bitmask are not recognized.

We can likely rule out 1 as GLX_RENDER_TYPE is correctly set to opengl.
Option 2 allows looking at it at a higher level. SDL2 adds
`GLX_CONTEXT_RELEASE_BEHAVIOUR_ARB=GLX_CONTEXT_RELEASE_BEHAVIOUR_FLUSH_ARB`
to the attributes (at src/video/x11/SDL_x11opengl.c:720) by default when
it detects the `GLX_ARB_context_flush_control` extension is present,
which should be a no-op and the default setting. `glxinfo` and other gl
functions all show that `GLX_ARB_context_flush_control` is present, but
removing that usage from the attributes list (by removing lines 720 to
726 avoids the issue and we are given a valid GL context.

Due to this, I think something in the graphics stack is rejecting the
usage of GLX_ARB_context_flush_control, even though it's claiming to
support it through other gl calls. The llvmpipe GL driver reports core
support up to 3.3 as well, so this shouldn't be an issue. I also suspect
it's simply something that's been fixed more recently, as installing the
newer HWE versions of xorg (and the kernel) fixes the issue.


I wouldn't expect to have to upgrade to the HWE stack to be able to get a 
working GL context this way, so I'm reporting this to check if it's a known 
issue or if there's a fix that can be made.

The attached file depends on "libsdl2-dev" and can be compiled and run with:
"g++ main.cpp -I/usr/include/SDL2 -lSDL2 -lGL && ./a.out"

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 09:16:16 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2020-11-03 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

[Touch-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

[Sebastien Bacher]

I'm using focal, the bug as tagged as incoming for series up to hirsute,
is it supposed to be mostly an issue for bionic? Maybe that station
attribute patch should be backported to bionic as a first step?

Could you give a more direct reference to that patch? Grepping for 'station' in 
debian/patches only returns
CVE-2019-16275.patch:connected station dropping its association.

It's still unclear to me what a real user facing scenario impact of the
issue would be. Would installing connman instead of network-manager and
trying to do some action

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

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  New

Bug description:
  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc. 
  The regression was introduced when someone try to have the Station attribute 
supported

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

-- 
Mailing list: https://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 1900729] Please test proposed package

[Łukasz Zemczak]

Hello Darko, or anyone else affected,

Accepted gtk+3.0 into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.23-1ubuntu1.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Łukasz Zemczak]

Ok, I think I have enough information to give a green light for this
change (especially that the Iain was +1 on getting it in as a single
fix).

** Description changed:

  [Impact]
  
  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.
  
  [Test case]
  
  * Install the binaries built from gtk+3.0 in groovy-proposed
  
  * Relogin
  
  * Open gnome-terminal -> Preferences and open the window for selecting a
  custom font for the profile. Find that it shows regular fonts only.
  
  [ Regression risk ]
  
  The upstream commit was written explicitly to fix this issue, so the
- regression risk should be low.
+ regression risk should be low. Please note that the only affected file
+ is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
+ itself ought to limit the regression risk.
  
  [Original description]
  
  trying to change the font in gnome-terminal, only the italics version of
  the ubuntu mono font is shown, as can be seen in the attachment. on the
  other hand, when changing fonts in the appearance settings, i can see
  all variants of the ubuntu fonts...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: gtk+3.0 (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

[You-Sheng Yang]

Verified 1.22.10-1ubuntu2.2 from focal-proposed with packages network-
manager, libnm0, gir1.2-nm-1.0, network-manager-config-connectivity-
ubuntu installed.

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

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set.
  (The driver will manager itself.) When the network-manager managers
  the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS
  resumed from suspend.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi function still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * This patch modifies the wake on lan parameters, please test that
  the corresponding feature still works fine with the different
  configuration values.

   1. Magic packet test:
    Set Wake on Wireless to off
    Send magic packet to the system
    Ensure it does not wake up

    Set Wake on Wirless to on
    Send magic packet to the system
    Ensure it does wake up

   2. Wi-Fi function test after resumed from suspend:
    After resume from suspend, the Wi-Fi should work normally.
    Scan APs.
    Connect to an AP.

  [Other Info]

   * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
  check (!597) · Merge Requests · NetworkManager / NetworkManager ·
  GitLab -
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639

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

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