[Touch-packages] [Bug 1903396] Re: libnl-route-3-200 unresolved symbols

[Launchpad Bug Tracker]

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

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

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

Title:
  libnl-route-3-200 unresolved symbols

Status in libnl3 package in Ubuntu:
  Expired

Bug description:
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"

  $ arch
  x86_64

  Getting a link error when trying to build Wireshark from source on
  Ubuntu Focal. I need to build Wireshark for plugin development.

  Steps to reproduce:
  1. Obtain source code from https://gitlab.com/wireshark/wireshark
  2. Install build dependencies as per CI ./tools/debian-setup.sh 
--install-optional --install-test-deps -y
  3. mkdir build
  4. cmake ..
  5. make
  6. Observer error:

  [ 88%] Linking CXX executable run/wireshark
  /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference 
to `nla_get_s32'
  /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference 
to `nl_strerror_l'
  collect2: error: ld returned 1 exit status
  make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1
  make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2
  make: *** [Makefile:141: all] Error 2

  Those two symbols are not present in any of the other libnl libraries,
  static or dynamic.

  /usr/include/libnl3/netlink/attr.h:119:extern int32_t
  nla_get_s32(const struct nlattr *);

  $ dpkg -S /usr/include/libnl3/netlink/attr.h
  libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h

  $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0
  libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0

  I can build and install libnl-3.2.25 from source and I don't get the
  linking issues anymore if I replace the .so files installed by the
  .debs, so it's possible that there is soemthing wrong with the
  packaging of libnl-route-3-200.deb.

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

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

[Touch-packages] [Bug 1911369] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [radeon] Horizontal lines of screen corruption after last update.

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  A clean install is fine if I don't take updates.  If I do take the
  updates and reboot then I get heavy video corruption.  This just
  started today.

  This is a dual boot system.  The windows system has no issues.
  Appears to be software and not a hardware issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 21:18:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 
7950 Boost] [1002:3000]
  InstallationDate: Installed on 2021-01-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.release: 3.96
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.96
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z420 Workstation
  dmi.product.sku: D8N02UC#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1911369] Re: screen corruption after last update.

[Daniel van Vugt]

Please try an older kernel like:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.89/amd64/

** Tags added: radeon

** Summary changed:

- screen corruption after last update.
+ [radeon] Horizontal lines of screen corruption after last update.

** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu)

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

** No longer affects: xserver-xorg-video-ati (Ubuntu)

** Tags added: regression-update

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

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

Title:
  [radeon] Horizontal lines of screen corruption after last update.

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  A clean install is fine if I don't take updates.  If I do take the
  updates and reboot then I get heavy video corruption.  This just
  started today.

  This is a dual boot system.  The windows system has no issues.
  Appears to be software and not a hardware issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 21:18:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 
7950 Boost] [1002:3000]
  InstallationDate: Installed on 2021-01-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.release: 3.96
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.96
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z420 Workstation
  dmi.product.sku: D8N02UC#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1911237] Re: Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go black (lose signal) after logging in

[Daniel van Vugt]

** Summary changed:

- Thinkpad P1 2nd gen and Thunderbold 3 Workstation Dock
+ Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go black 
(lose signal) after logging in

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

Title:
  Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go
  black (lose signal) after logging in

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The dock is Type 40AN .

  I already reported a bug, and was asked to run ubuntu-bug xorg, which I did 
and arrived here.
  Probably you want to merge them. Please also mind the tons of reports from 
other users, which report the same or similar issues in the Ubuntu Forum, in 
the thread which I did open. Please see the other bug for a link.

  In the current configuration I did downgrade the dock to an older
  firmware version as mentioned in my other bug ticket, and also by many
  other users in the Ubuntu Forum, since this is the only way it works
  at least partially, so that I'm able to submit this bug report.

  The symptom right now is that I bootet with two 4 K Monitors connected, and 
could see at least for a while (at time of login screen) the magenta 
background, but then, after logging in, the 2 external Monitors get black and 
say something similar to 'Input Signal not Found'. 
  Opposed to this, when I open within Gnome the Settings > Displays ( or 
similar, I have it in German), then it tells me there that I have 2 external 
Monitors connected, which I can move around in that dialog, choose primary 
dialog etc.

  On the console, where I run ubuntu-bug, I get this messages
  (repeatedly):

  Errors:
  Program binary could not be loaded. Binary is not compatible with current 
driver/hardware combination. Driver build date Oct 22 2020. Please check build 
information of source that generated the binary.

  wind:~ $ [8190:8190:0112/191237.346935:ERROR:shared_context_state.cc(74)] 
Skia shader compilation error
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.4.35-custom-patched-26c16f9d9 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/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.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/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: Tue Jan 12 19:09:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.38, 5.4.0-58-generic, x86_64: installed
   nvidia, 455.38, 5.4.35-custom-patched-26c16f9d9, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-58-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.35-custom-patched-26c16f9d9, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f]
  InstallationDate: Installed on 2020-05-05 (251 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20QT000RGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.35-custom-patched-26c16f9d9 
root=UUID=07e75e73-7d85-45e9-90a7-a83ea1f47c1c ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET49W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QT000RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  

[Touch-packages] [Bug 1911369] [NEW] screen corruption after last update.

[Norm Petroff]

Public bug reported:

A clean install is fine if I don't take updates.  If I do take the
updates and reboot then I get heavy video corruption.  This just started
today.

This is a dual boot system.  The windows system has no issues.  Appears
to be software and not a hardware issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 12 21:18:27 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 
7950 Boost] [1002:3000]
InstallationDate: Installed on 2021-01-13 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Hewlett-Packard HP Z420 Workstation
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2019
dmi.bios.release: 3.96
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J61 v03.96
dmi.board.name: 1589
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 0.00
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53335X G=D
dmi.product.name: HP Z420 Workstation
dmi.product.sku: D8N02UC#ABA
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
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 corruption focal ubuntu

** Attachment added: "Screen Corruption."
   
https://bugs.launchpad.net/bugs/1911369/+attachment/5452470/+files/screen_corruption.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/1911369

Title:
  screen corruption after last update.

Status in xorg package in Ubuntu:
  New

Bug description:
  A clean install is fine if I don't take updates.  If I do take the
  updates and reboot then I get heavy video corruption.  This just
  started today.

  This is a dual boot system.  The windows system has no issues.
  Appears to be software and not a hardware issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 21:18:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 
7950 Boost] [1002:3000]
  InstallationDate: Installed on 2021-01-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.release: 3.96
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.96
  dmi.board.name: 1589
  

[Touch-packages] [Bug 1911219] Re: Xorg freeze

[Daniel van Vugt]

Next time the freeze happens, please reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Please also check for crashes using these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment


** Tags added: nouveau

** Summary changed:

- Xorg freeze
+ [nouveau] Xorg freeze

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

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

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

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

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

Title:
  [nouveau] Xorg freeze

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Also freezes when trying to open Libre Office new documents

  Not sure if it is the video that is causing issues

  Mouse and keyboard seems to be frozen and cant do anything without a
  hard reboot

  Some times the video keeps playing even if everything is frozen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 11:29:12 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1212]
  InstallationDate: Installed on 2021-01-09 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=598990d0-29d6-4e5b-a8aa-3c75c00bd284 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-970A-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-970A-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1910928] Re: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

[Daniel van Vugt]

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  New

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1883694] Proposed package upload rejected

[Chris Halse Rogers]

An upload of glib2.0 to focal-proposed has been rejected from the upload
queue for the following reason: "The bug reference in the changelog is
for https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1883694 which
is the already-fixed SRU bug for 2.64.3. Please file a new bug to track
this new SRU.".

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

Title:
  [SRU] New upstream release 2.64.3

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

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium
  +
  +  * No-change backport from unstable / groovy to focal.
  +
  + -- Iain Lane   Tue, 16 Jun 2020 11:53:34 +0100
  +
  +glib2.0 (2.64.3-1) unstable; urgency=medium
  +
  +  * Team upload
  +
  +  [ Laurent Bigonville ]
  +  * Drop the libgio-fam package, and install the fam GIO plugin in
  +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915)
  +  * Stop building the libgio-fam package on kFreeBSD ports.
  +It is no longer necessary now that gkqueuefilemonitor is available.
  +
  +  [ Simon McVittie ]
  +  * Clarify changelog entry regarding Hurd and kFreeBSD
  +  * New upstream stable release
  +
  + -- Simon McVittie   Fri, 29 May 2020 20:24:33 +0100

  The gio-fam related changes do not affect Ubuntu, as they are for
  hurd/kfreebsd only.

  Upstream NEWS diff:

  * Stability improvements for various unit tests

  * Bugs fixed:
   - #1954 gdbus-server-auth intermittent failure
   - #2094 Deprecation warnings when compiling with 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28
   - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64
   - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64
   - !1473 CI: Switch to new Windows runners (2.64)
   - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64
   - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after 
g_ptr_array_extend_and_steal()” to glib-2-64
   - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to 
glib-2-64
   - !1486 Backport !1472 “gthread: ignore deprecated declarations in static 
inline functions” to glib-2-64
   - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to 
glib-2-64
   - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64

  * Translation updates:
   - Chinese (Taiwan)
   - German

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.
  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

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

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

[Touch-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive

[Pierre Wilch]

I had the same problem.
- Since this bug only appeared by me by consulting the proprieties of the file 
with Nautilus, and did not occur with linux mint 20 and Nemo, I reported it as 
bug 1890958 in Nautilus.
- Since updates beginning of the year 2021 I can no longer reproduce it. It 
seems to be solved.
- Ubuntu team, can you confirm it here (or not?), so people who spent time to 
report this to help you could sleep on their two ears and use ubuntu 20.04 
again, with no fear of such dangerous bugs?

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

Title:
  date modified is wrong for files on an exfat formatted drive

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  When using exfat formatted drives (e.g. my camera card) with focal
  fossa any access causes the date modified to be set, even when it
  would not normally be set, and it is set a month into the future.

  Installing exfat-fuse and exfat-utils results in the correct
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 17:27:30 2020
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat

[Brian Murray]

Hello bugproxy, or anyone else affected,

Accepted elfutils into groovy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/elfutils/0.181-1ubuntu0.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.

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

Title:
  Ubuntu 20.10 - elfutils unwinding broken for s390 compat

Status in Ubuntu on IBM z Systems:
  In Progress
Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Groovy:
  Fix Committed
Status in elfutils source package in Hirsute:
  Fix Released

Bug description:
  SRU Bug Template:
  =

  [Impact]

   * There is an endianess problem in pid_memory_read that impacts
  s390x.

   * Due to this elfutils biarch test fails on s390x doing unwinding for
  a 32 bit process.

  [Fix]

   * e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess 
problem in pid_memory_read"
   
  [Test Case]

   * Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM 
that comes with elfutils 0.181 or 0.182.
   
   * Run the test script: 'run-backtrace-native-biarch.sh'
   
   * It either core dumps without the patch  in place - look for 
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
   
   [Where problems could occur]
   
   * If the translation is not done right (shift of the upper 4 bytes + down on 
big endian 64 bit targets) the situation is broken in the same way, and things 
stay the same.
   
   * But in worst case the changes in 'pid_memory_read' of 
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures 
other than s390x, in case the check for the endiness is wrong.
   
   * But the changes are quite traceable and the additional code that fixes the 
endianess problem is really only active on a big endian architecture.
   
   [Other]
   
   * The fix is upstream accepted with elfutils > 0.182.
  __

  ---Problem Description---
  libdw unwinding fails for 32 bit binaries.

  Elfutils biarch test currently fails on s390x doing unwinding for a 32
  bit process.

  FAIL: run-backtrace-native-biarch.sh
  

  0x557e7000  0x557eb000  /root/elfutils/tests/backtrace-child-biarch
  0x7dba4000  0x7dd51000  /usr/lib/libc-2.32.so
  0x7dd53000  0x7dd7  /usr/lib/libpthread-2.32.so
  0x7dd7f000  0x7dda6000  /usr/lib/ld-2.32.so
  TID 376858:
  # 0 0x7dd6668a  raise
  # 1 0x7fd0ef60 - 1  
  /root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information 
found
  backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL && 
strcmp (symname, "sigusr2") == 0' failed.
  ./test-subr.sh: line 84: 376822 Aborted (core dumped) 
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH" 
$VALGRIND_CMD "$@"
  backtrace-child-biarch: no main
  FAIL run-backtrace-native-biarch.sh (exit status: 1)

  Patch has already been posted and upstream committed:
  https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html

  Please pick up the following commit for the next release:
  commit e4d985a3c1c873f77d20fa0cd421458cc2824996
  Author: Andreas Krebbel 
  Date:   Thu Nov 19 20:32:24 2020 +0100

  IBM Z: Fix endianess problem in pid_memory_read

  The cached reads lack the big endian adjustments done in the fallback
  path.

  Signed-off-by: Andreas Krebbel 

  The patch applies cleanly ontop of elfutils_0.181-1.

  
  strace right now is not built with unwinding support for IBM Z although both 
variants should work - libdw and libunwind.

  Other distros use libdw from 

[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child

[Sergio Durigan Junior]

** Changed in: sssd (Ubuntu Focal)
 Assignee: Sergio Durigan Junior (sergiodj) => Marco Trevisan (Treviño) 
(3v1n0)

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

Title:
  Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for
  p11_child

Status in ca-certificates package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Focal:
  New
Status in sssd source package in Focal:
  New

Bug description:
  [ Impact ]

  SSSD supports in 20.04 two security backends: NSS and OpenSSL
  (speaking in past tense as upstream dropped NSS support completely).

  Those two backends are used for various generic crypto features (so
  they are interchangeable), but also for the management of the PKCS#11
  modules for smart cards.

  In this case, the main problem is that by using NSS it also relies on
  the presence of a "system NSS" database [1] that is something present
  in Fedora and RHEL, but not in ubuntu or generic Linux distributions.

  In order to make SSSD to find a smart card module, we would then need to 
create a such database that mentions a p11kit proxy that will eventually load 
the p11-kit module and then add the card CA certificate to the same DB (see 
more details in [2]).
  And even in such case... It will not work at login phase.

  This is making support for Smart-card based authentication in 20.04
  quite complicated, and hard to implement in professional environments
  (see bug #1865226).

  As per this, recompiling SSSD's p11_child to use OpenSSL (as it
  already happens starting from 20.10) would be enough to make the this
  tool (the one in charge for smartcard authentications and certificate
  matching) to be able to get the smartcard devices from p11-kit allowed
  modules and to check their certificate using CA certificates in the
  ubuntu system ca certificate files (or other configured file).

  One more mayor reason to do this, is also that if we fix 20.04 now to
  use the "proper" method, people who will configure smartcard access
  there via SSSD (not easily possible right now) won't be affected by
  future migrations.

  
  [ Proposed Implementations ]

  1) Use p11-kit and openssl for p11_child, by changing the build/test system 
(preferred)
     https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child

  2) Build both versions and package things accordingly (hackish)
     https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1

  3) Recompile SSSD completely to use libcrypto as backend

  The option 3) has been finally choosen, but we also require migration
  scripts on upgrade.

  
  [ Test case ]

  With a smartcard reader available (and with a card in its slot) as reported 
by:
   $ p11-kit list-modules

  launch:
   $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \
     --nssdb=/etc/ssl/certs/ca-certificates.crt

  The tool should find your card:

  (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module 
List:
  (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common 
name: [p11-kit-trust].
  (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll 
name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so].
  (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): 
Description [/etc/ssl/certs/ca-certificates.crt  
PKCS#11 Kit ] Manufacturer [PKCS#11 Kit 
] flags [1] removable [false] token present [true].
  (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common 
name: [opensc-pkcs11].
  (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll 
name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so].
  (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): 
Description [VMware Virtual USB CCID 00 00   
VMware  ] Manufacturer [VMware  
] flags [7] removable [true] token present [true].
  (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found 
[MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of 
module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so].

  Then:
   1) If you previously configured SSSD match rules and/or CA certificates:
  - You should still get your certificate public key printed as output
  - Configured login with smartcard should continue working

   2) If SSSD was not configured to do smartcard authentication:
  - p11_child may fail if the card certificate was not previously added to
    the trusted DB, but this is outside of this test case.
  - What it matters is that the card is found.

  [ Regression potential ]

  While the change may involve quite different code paths 

[Touch-packages] [Bug 1895207] Re: package libpam-runtime 1.3.1-5ubuntu4.1 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess returned error exit status 12

[Launchpad Bug Tracker]

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

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

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

Title:
  package libpam-runtime 1.3.1-5ubuntu4.1 failed to install/upgrade:
  installed libpam-runtime package post-installation script subprocess
  returned error exit status 128

Status in pam package in Ubuntu:
  Confirmed

Bug description:
  Dear Sirs/Madams,  I am simply reporting this as the "pam package"
  directs.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-runtime 1.3.1-5ubuntu4.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Sep 10 22:56:49 2020
  DuplicateSignature:
   package:libpam-runtime:1.3.1-5ubuntu4.1
   Setting up libpam-runtime (1.3.1-5ubuntu4.1) ...
   Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134,  line 1.
   dpkg: error processing package libpam-runtime (--configure):
installed libpam-runtime package post-installation script subprocess 
returned error exit status 128
  ErrorMessage: installed libpam-runtime package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2020-09-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: pam
  Title: package libpam-runtime 1.3.1-5ubuntu4.1 failed to install/upgrade: 
installed libpam-runtime package post-installation script subprocess returned 
error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

[Dan Streetman]

> Have the same problem, here is the log:

that log doesn't show the reported problematic log messages

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

Title:
  systemd-shutdown cannot detach DM

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  when powering down the system systemd cannot unmount /

  systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
  systemd-shutdown[1]: Failed to finalize  DM devices, ignoring
  reboot: Power down

  as a result at each startup the filesystem is checked:

  Press Ctrl+C to cancel all filesystem checks in progress

  If systemd cannot unmount / that might not be a problem but it should
  be less noisy and not result in a filesystem check after each reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 11:40:05 2020
  MachineType: Dell Inc. Latitude 7410
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0M5G57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7410
  dmi.product.sku: 09CD
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1742804] Re: Failed to add PIDs to scope's control group

[Dan Streetman]

> I get it too, but on a fresh Kubuntu 20.10!

I just tested on groovy and see no failure.

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

Title:
  Failed to add PIDs to scope's control group

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  [impact]

  systemd-run --user --scope fails

  [test case]

  $ systemd-run --user --scope echo hello
  Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
  See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.

  [regression potential]

  large.  this is fixed upstream by a large sequence of patches, and
  would need careful attention applying them all to make sure no
  regressions were introduced.

  If I, or anyone else, attempts this backport, they definitely need to
  add more detail to this section.

  [scope]

  This is fixed upstream by this large PR:
  https://github.com/systemd/systemd/pull/8125

  That's included starting in systemd v238, so just missed the Bionic
  version.  This is fixed already in all releases after Bionic, and
  needed only for Bionic.

  [original description]

  
  When I launch applications with flatpak, "journalctl -f" shows the following:

  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Failed to add PIDs to scope's control group: Permission denied
  Jan 11 22:44:13 localhost systemd[1244]: Failed to start 
flatpak-org.kde.krita-8134.scope.
  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Unit entered failed state.

  I explicitly mentioned "Kubuntu" in the summary, because I experience
  this only under Kubuntu (17.10 and 18.04), NOT under the regular
  Gnome-based Ubuntu Desktop (17.10). At first this error message seemed
  harmless, because it looked like it had no effect. But now I noticed
  that with certain flatpak apps, the file open dialog would not pop up.
  And I too experienced this only under Kubuntu, not Ubuntu or Fedora
  (all tested). So there might be a connection.

  I first reported this to flatpak:

  https://github.com/flatpak/flatpak/issues/1216

  There it was suggested to try the following command:

  $ systemd-run --user --scope echo hello
  Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
  See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.

  ...and this one also fails.

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

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

[Touch-packages] [Bug 1911237] Re: Thinkpad P1 2nd gen and Thunderbold 3 Workstation Dock

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Thinkpad P1 2nd gen and Thunderbold 3 Workstation Dock

Status in xorg package in Ubuntu:
  New

Bug description:
  The dock is Type 40AN .

  I already reported a bug, and was asked to run ubuntu-bug xorg, which I did 
and arrived here.
  Probably you want to merge them. Please also mind the tons of reports from 
other users, which report the same or similar issues in the Ubuntu Forum, in 
the thread which I did open. Please see the other bug for a link.

  In the current configuration I did downgrade the dock to an older
  firmware version as mentioned in my other bug ticket, and also by many
  other users in the Ubuntu Forum, since this is the only way it works
  at least partially, so that I'm able to submit this bug report.

  The symptom right now is that I bootet with two 4 K Monitors connected, and 
could see at least for a while (at time of login screen) the magenta 
background, but then, after logging in, the 2 external Monitors get black and 
say something similar to 'Input Signal not Found'. 
  Opposed to this, when I open within Gnome the Settings > Displays ( or 
similar, I have it in German), then it tells me there that I have 2 external 
Monitors connected, which I can move around in that dialog, choose primary 
dialog etc.

  On the console, where I run ubuntu-bug, I get this messages
  (repeatedly):

  Errors:
  Program binary could not be loaded. Binary is not compatible with current 
driver/hardware combination. Driver build date Oct 22 2020. Please check build 
information of source that generated the binary.

  wind:~ $ [8190:8190:0112/191237.346935:ERROR:shared_context_state.cc(74)] 
Skia shader compilation error
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.4.35-custom-patched-26c16f9d9 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/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.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/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: Tue Jan 12 19:09:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.38, 5.4.0-58-generic, x86_64: installed
   nvidia, 455.38, 5.4.35-custom-patched-26c16f9d9, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-58-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.35-custom-patched-26c16f9d9, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f]
  InstallationDate: Installed on 2020-05-05 (251 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20QT000RGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.35-custom-patched-26c16f9d9 
root=UUID=07e75e73-7d85-45e9-90a7-a83ea1f47c1c ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET49W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QT000RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Touch-packages] [Bug 1911237] [NEW] Thinkpad P1 2nd gen and Thunderbold 3 Workstation Dock

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The dock is Type 40AN .

I already reported a bug, and was asked to run ubuntu-bug xorg, which I did and 
arrived here.
Probably you want to merge them. Please also mind the tons of reports from 
other users, which report the same or similar issues in the Ubuntu Forum, in 
the thread which I did open. Please see the other bug for a link.

In the current configuration I did downgrade the dock to an older
firmware version as mentioned in my other bug ticket, and also by many
other users in the Ubuntu Forum, since this is the only way it works at
least partially, so that I'm able to submit this bug report.

The symptom right now is that I bootet with two 4 K Monitors connected, and 
could see at least for a while (at time of login screen) the magenta 
background, but then, after logging in, the 2 external Monitors get black and 
say something similar to 'Input Signal not Found'. 
Opposed to this, when I open within Gnome the Settings > Displays ( or similar, 
I have it in German), then it tells me there that I have 2 external Monitors 
connected, which I can move around in that dialog, choose primary dialog etc.

On the console, where I run ubuntu-bug, I get this messages
(repeatedly):

Errors:
Program binary could not be loaded. Binary is not compatible with current 
driver/hardware combination. Driver build date Oct 22 2020. Please check build 
information of source that generated the binary.

wind:~ $ [8190:8190:0112/191237.346935:ERROR:shared_context_state.cc(74)] Skia 
shader compilation error
-

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.4.35-custom-patched-26c16f9d9 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/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.38  Thu Oct 22 06:06:59 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/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: Tue Jan 12 19:09:11 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 455.38, 5.4.0-58-generic, x86_64: installed
 nvidia, 455.38, 5.4.35-custom-patched-26c16f9d9, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-58-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.35-custom-patched-26c16f9d9, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f]
InstallationDate: Installed on 2020-05-05 (251 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20QT000RGE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.35-custom-patched-26c16f9d9 
root=UUID=07e75e73-7d85-45e9-90a7-a83ea1f47c1c ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET49W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QT000RGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET49W(1.36):bd11/19/2020:svnLENOVO:pn20QT000RGE:pvrThinkPadP1Gen2:rvnLENOVO:rn20QT000RGE:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P1 Gen 2
dmi.product.name: 20QT000RGE
dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
dmi.product.version: ThinkPad P1 Gen2
dmi.sys.vendor: LENOVO
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2020-05-06T01:05:34.863982

[Touch-packages] [Bug 1904793] Re: upower abruptly thinks battery has gone to 1% and hibernates

[Lee Trager]

Upstream bug reported at
https://gitlab.freedesktop.org/upower/upower/-/issues/136

** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #136
   https://gitlab.freedesktop.org/upower/upower/-/issues/136

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

Title:
  upower abruptly thinks battery has gone to 1% and hibernates

Status in upower package in Ubuntu:
  New

Bug description:
  Whenever I go on battery after 20-30 minutes upower will very abruptly
  think my battery is at 1% and force my laptop to hibernate. This seems
  to happen at random times, I've seen it when my battery was reported
  to be 90%, 76%, 45%, 25%, etc. If I try to resume Ubuntu locks up
  forcing me to hard reset the machine. I suspect this is because upower
  thinks my battery is still at 1% when its not. My laptops firmware
  correctly reports the battery level and shows that I have plenty of
  power remaining. The last few times this happened I kept powertop up
  which shows that I do have plenty of power even when upower thinks I
  have none. Essentially this makes my laptop unusable on battery.

  Laptop: Lenovo X1 Carbon Extreme Gen 2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: upower 0.99.11-2
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Nov 18 13:59:24 2020
  InstallationDate: Installed on 2019-12-29 (325 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (25 days ago)

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

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

[Touch-packages] [Bug 1889668] Re: set-cpufreq error when cpu is offline

[scottku]

Sure, that works.

Wouldn't small patch to the set-cpufreq as described at the end of my
report would also fix the problem for everybody without the need for
additional configuration? I assume ondemand.service and the set-cpufreq
script will be around on 20.04 for some time.

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

Title:
  set-cpufreq error when cpu is offline

Status in systemd package in Ubuntu:
  New

Bug description:
  I have hyperthreading disabled on my Ubuntu 19.10 machine, which makes
  some processors in /sys/devices/system/cpu/cpu* have their "online"
  set to 0.

  However, when the for-loop in /lib/systemd/set-cpufreq iterates over
  the processors, it doesn't check if the processor is online before
  trying to write the governor name into scaling_governor.

  The script appears to have the same bug in Ubuntu 20.04.

  I modified the script to print the cpu it is trying to set before doing so, 
and I get the following:
  Setting powersave scheduler for all CPUs
  /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
  /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
  /sys/devices/system/cpu/cpu10/cpufreq/scaling_governor
  /lib/systemd/set-cpufreq: 43: echo: echo: I/O error

  Since the script doesn't continue to try other processors in the loop,
  it means that only cpu0 and cpu1 on my machine get set to powersave
  and the others remain with the performance governor. The cpufreq-info
  command confirms this.

  Checking if the processor has online==1 before writing, or putting the
  echo within a "set +e" "set -e" pair would fix the problem (although
  the latter approach would still print error messages).

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

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

[Touch-packages] [Bug 1911219] [NEW] Xorg freeze

[Sam John]

Public bug reported:


Also freezes when trying to open Libre Office new documents

Not sure if it is the video that is causing issues

Mouse and keyboard seems to be frozen and cant do anything without a
hard reboot

Some times the video keeps playing even if everything is frozen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 12 11:29:12 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Within the last few days
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1212]
InstallationDate: Installed on 2021-01-09 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=598990d0-29d6-4e5b-a8aa-3c75c00bd284 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F10
dmi.board.name: GA-970A-D3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-970A-D3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
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 freeze 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/1911219

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Also freezes when trying to open Libre Office new documents

  Not sure if it is the video that is causing issues

  Mouse and keyboard seems to be frozen and cant do anything without a
  hard reboot

  Some times the video keeps playing even if everything is frozen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 11:29:12 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1212]
  InstallationDate: Installed on 2021-01-09 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=598990d0-29d6-4e5b-a8aa-3c75c00bd284 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: 

[Touch-packages] [Bug 1911059] Re: gce: 247.1-4ubuntu1 causes loss of networking

[Balint Reczey]

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  gce: 247.1-4ubuntu1 causes loss of networking

Status in systemd package in Ubuntu:
  New

Bug description:
  Summary
  ===
  On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud 
instance to loose network access.

  Expected Result
  ===
  Working network access

  Actual Result
  ===
  After upgrade, network access is lost and serial console is filled with 
messages about IPv4 martian source and ll header, see below.

  Steps to Reproduce
  ===
  1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image
  2. sudo apt update
  3. sudo apt install systemd
  4. ssh is lost

  The images, built with this version do not appear to be able to start
  networking.

  Logs
  ===
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915720] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915724] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978762] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978803] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042242] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042302] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105412] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105448] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168141] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168178] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00

  $ journalctl --no-pager -u systemd-net
  -- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 
21:52:03 UTC. --
  Jan 11 21:30:35 ubuntu systemd[1]: Starting Network Service...
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: Enumeration completed
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Interface name change 
detected, ens4 has been renamed to eth0.
  Jan 11 21:30:35 ubuntu systemd[1]: Started Network Service.
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: eth0: Interface name change 
detected, eth0 has been renamed to ens4.
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: IPv6 successfully enabled
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Link UP
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Gained carrier
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: DHCPv4 address 
10.138.0.56/32 via 10.138.0.1
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Classless static routes 
received from DHCP server: ignoring router option
  Jan 11 21:30:37 ubuntu systemd-networkd[413]: ens4: Gained IPv6LL
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[413]: ens4: DHCPv6 
lease lost
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Network 
Service...
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: 
systemd-networkd.service: Succeeded.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Network Service.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Starting Network 
Service...
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: 
Gained IPv6LL
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: Enumeration 
completed
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Started Network Service.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: 
DHCPv4 address 10.138.0.56/32 via 10.138.0.1

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

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

[Touch-packages] [Bug 1908502] Re: [MIR] libtiff5 dependency on libdeflate0

[Sebastien Bacher]

** Tags added: update-excuse

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

Title:
  [MIR] libtiff5 dependency on libdeflate0

Status in libdeflate package in Ubuntu:
  Incomplete
Status in tiff package in Ubuntu:
  Confirmed

Bug description:
  tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as
  a dependency to libtiff5, making the package uninstallable.

  Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate
  support to make libtiff5 installable again.

  Either this package stays this way, or it needs a MIR for libdeflate.

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package python-apt - 2.1.7

---
python-apt (2.1.7) unstable; urgency=medium

  * SECURITY UPDATE: various memory and file descriptor leaks (LP: #1899193)
- python/arfile.cc, python/generic.h, python/tag.cc, python/tarfile.cc:
  fix file descriptor and memory leaks
- python/apt_instmodule.cc, python/apt_instmodule.h, python/arfile.h:
  Avoid reference cycle with control,data members in apt_inst.DebFile
  objects
- tests/test_cve_2020_27351.py: Test cases for DebFile (others not easily
  testable)
  * Regression fixes for the updates merged too:
- arfile.cc: Fix segmentation fault when opening fd, track lifetime 
correctly
  (Closes: #977000)
- arfile: Regression: Collect file<->deb/ar reference cycles

 -- Julian Andres Klode   Thu, 10 Dec 2020 15:35:32
+0100

** Changed in: python-apt (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 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:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released

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 1849406] Re: Ubuntu 19.10: "Cdrom" to "Physical media"

[Launchpad Bug Tracker]

This bug was fixed in the package python-apt - 2.1.7

---
python-apt (2.1.7) unstable; urgency=medium

  * SECURITY UPDATE: various memory and file descriptor leaks (LP: #1899193)
- python/arfile.cc, python/generic.h, python/tag.cc, python/tarfile.cc:
  fix file descriptor and memory leaks
- python/apt_instmodule.cc, python/apt_instmodule.h, python/arfile.h:
  Avoid reference cycle with control,data members in apt_inst.DebFile
  objects
- tests/test_cve_2020_27351.py: Test cases for DebFile (others not easily
  testable)
  * Regression fixes for the updates merged too:
- arfile.cc: Fix segmentation fault when opening fd, track lifetime 
correctly
  (Closes: #977000)
- arfile: Regression: Collect file<->deb/ar reference cycles

 -- Julian Andres Klode   Thu, 10 Dec 2020 15:35:32
+0100

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

Title:
  Ubuntu 19.10: "Cdrom" to "Physical media"

Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  Do this: open the app Software & Updates > select first tab named
  Ubuntu Software (if not already by default) > observe section
  Installable from CD-ROM/DVD

  In those good ol' days, Ubuntu was installable only from a CD and
  later from a DVD. Nowadays, USB thumb drives are superceding this,
  which makes the whole string wrong, even the title.

  So, I propose this:
  Installable from physical media
  Physical media with Ubuntu [...]

  This makes it future-proof as well, since god-knows-what is going to
  exist in the future to boot Ubuntu from, but it will be physical media
  for sure.

  Care to fix this? Also, I would gladly make a PR request to speed up
  the process (provided you tell me how).

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

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

[Touch-packages] [Bug 1911208] Re: package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-firmware 1.187.7 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Automatic update failed.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.7
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   2435 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue Jan 12 14:27:36 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=1e956d5d-0170-42d1-a1e9-65930a3b02f7
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd HP Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G5 Notebook PC
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic 
root=/dev/mapper/vgUbuntu-lvUbuntuRoot ro rootflags=subvol=@ quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.7 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.48
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EB
  dmi.board.vendor: HP
  dmi.board.version: 61.61
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.48:bd12/17/2019:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.61:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 250
  dmi.product.name: HP 250 G5 Notebook PC
  dmi.product.sku: X0Q78ES#ABU
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1911208] [NEW] package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

[Njorl]

Public bug reported:

Automatic update failed.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.7
ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
Uname: Linux 5.4.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  adam   2435 F pulseaudio
CasperMD5CheckResult: skip
Date: Tue Jan 12 14:27:36 2021
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=1e956d5d-0170-42d1-a1e9-65930a3b02f7
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd HP Webcam
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP 250 G5 Notebook PC
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic 
root=/dev/mapper/vgUbuntu-lvUbuntuRoot ro rootflags=subvol=@ quiet splash 
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.7 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.48
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81EB
dmi.board.vendor: HP
dmi.board.version: 61.61
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.48:bd12/17/2019:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.61:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 250
dmi.product.name: HP 250 G5 Notebook PC
dmi.product.sku: X0Q78ES#ABU
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-firmware 1.187.7 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Automatic update failed.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.7
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   2435 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue Jan 12 14:27:36 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=1e956d5d-0170-42d1-a1e9-65930a3b02f7
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd HP Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G5 Notebook PC
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic 
root=/dev/mapper/vgUbuntu-lvUbuntuRoot ro rootflags=subvol=@ quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.7 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.48
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EB
  dmi.board.vendor: HP
  dmi.board.version: 61.61
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Touch-packages] [Bug 1911206] [NEW] Update info on reloading sysctl with systemd

[Jerry Quinn]

Public bug reported:

/etc/sysctl.d/README says that after making changes, you should run
"service procps start" to activate the changes.

Since systemd is now the default init system, please update the README
files to also say you can activate changes with:

systemctl restart systemd-sysctl

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: procps 2:3.3.16-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
Uname: Linux 5.4.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 12 09:23:57 2021
InstallationDate: Installed on 2020-05-29 (227 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: procps
UpgradeStatus: Upgraded to focal on 2020-11-04 (68 days ago)
modified.conffile..etc.sysctl.d.10-link-restrictions.conf: [deleted]

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


** Tags: amd64 apport-bug focal

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

Title:
  Update info on reloading sysctl with systemd

Status in procps package in Ubuntu:
  New

Bug description:
  /etc/sysctl.d/README says that after making changes, you should run
  "service procps start" to activate the changes.

  Since systemd is now the default init system, please update the README
  files to also say you can activate changes with:

  systemctl restart systemd-sysctl

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: procps 2:3.3.16-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 09:23:57 2021
  InstallationDate: Installed on 2020-05-29 (227 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: procps
  UpgradeStatus: Upgraded to focal on 2020-11-04 (68 days ago)
  modified.conffile..etc.sysctl.d.10-link-restrictions.conf: [deleted]

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

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

[Touch-packages] [Bug 1903300] Re: systemd-networkd silently fails to set vxlan multicast group

[Martin Sofaru]

Hello Chris,


i can confirm, that after installing packages:
libnss-systemd_245.4-4ubuntu3.4_amd64.deb  
libsystemd0_245.4-4ubuntu3.4_amd64.deb  
systemd-sysv_245.4-4ubuntu3.4_amd64.deb   
systemd_245.4-4ubuntu3.4_amd64.deb
libpam-systemd_245.4-4ubuntu3.4_amd64.deb  
libudev1_245.4-4ubuntu3.4_amd64.deb 
systemd-timesyncd_245.4-4ubuntu3.4_amd64.deb  
udev_245.4-4ubuntu3.4_amd64.deb

the mcast group is set properly for the vxlan interface.

Thank you!

Martin

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

Title:
  systemd-networkd silently fails to set vxlan multicast group

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  setting VXLAN.Group does not correctly configure multicast group

  [test case]

  taken from upstream bug, example networkd config:

  [NetDev]
  Kind=vxlan
  Name=myvx

  [VXLAN]
  VNI=1
  Group=ff02::42:1
  DestinationPort=8472

  After restarting systemd-networkd the VXLAN device is created, but the
  group address is not assigned. Use ip -d link show myvx and networkctl
  show myvx to verify.

  [regression potential]

  any regression would likely cause problems only with VXLAN netdevs
  created by networkd.

  [scope]

  this is needed only for f.

  this was introduced by upstream commit 83cb24ac20b which was first in
  v243, so this bug does not exist in b and earlier.

  this was fixed by upstream commit
  7c9b26900cc33daf080627daf5904de74c1ef267 (and two following commits)
  which were first included in v246, so this is already fixed in g and
  later.

  [original description]

  
  Fixed upstream, please include [1].

  Thank you.

  [1] https://github.com/systemd/systemd/pull/15397

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  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.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov  6 14:16:19 2020
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=97786d27-c04a-4592-a087-f19a689468a9 ro console=tty1 console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-08-27 (70 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.1:cvnQEMU:ct1:cvrpc-q35-5.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.1
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1881947] Autopkgtest regression report (systemd/246.6-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.1) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.46.1-1ubuntu1 (arm64, amd64)
prometheus/2.20.0+ds-1 (s390x)
netplan.io/0.100-0ubuntu5 (arm64)
flatpak/1.8.2-1 (arm64)


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/groovy/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1881947

Title:
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Autopkgtest fails due to corrupted journal file

  [Test Case]

   * Observe autopkgtest root-unittests not failing with:

  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

  [Where problems could occur]

   * The change has no impact on the systemd binary packages. The
  relaxed test could hide a journal corruption problem, but it seems the
  corrupted journal files occur only on arm64 probably due to arm64
  reboots being resets: LP: #1748280.

  [Original Bug Text]

  Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz

  [...]
  PASS: test-journal-enum
  == test-journal-flush ===
  Root directory /var/log/journal removed.
  Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed.
  mmap cache statistics: 739 hit, 5 miss
  journal_file_copy_entry failed: Bad message
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function 
main(). Aborting.
  FAIL: test-journal-flush (code: 134)
  Aborted (core dumped)
  == test-journal-importer ===
  [...]
  autopkgtest [07:17:29]:  summary
  timedatedPASS
  hostnamedPASS
  localed-locale   PASS
  localed-x11-keymap   PASS
  logind   PASS
  unit-config  PASS
  storage  PASS
  networkd-test.py PASS
  build-login  PASS
  boot-and-servicesPASS
  udev PASS
  root-unittests   FAIL non-zero exit status 134
  upstream PASS
  boot-smoke   PASS
  systemd-fsckdPASS
  Exit request sent.
  [...]

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

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

[Touch-packages] [Bug 1907306] Autopkgtest regression report (systemd/237-3ubuntu10.44)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.44) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-azure-4.15/4.15.0-1104.116 (amd64)
munin/2.0.37-1ubuntu0.1 (arm64)
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
libvirt/4.0.0-1ubuntu8.17 (i386)
apt/1.6.12ubuntu0.2 (armhf)
netplan.io/0.99-0ubuntu3~18.04.3 (amd64)
linux-hwe-5.0/5.0.0-63.69 (armhf)
openssh/1:7.6p1-4ubuntu0.3 (armhf, s390x, ppc64el, arm64, i386, amd64)
corosync/2.4.3-0ubuntu1.1 (armhf)
nut/2.7.4-5.1ubuntu2 (i386)


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#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1907306

Title:
  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

  [test case]

  configure an interface to use dhcpv4; acquire a dhcpv4 address, then
  stop the dhcpv4 server, and wait for the networkd client to perform
  its renewals and rebinds before expiring the lease

  using a 20 minute lease time as an example (all times are approximate
  due to RFC-mandated random 'fuzz' time of -1 to +1 sec):

  the current behavior would be to sent renew requests at:

  10:00
  13:45

  and then rebind requests at:

  17:30
  18:45

  then the lease would expire at 20:00

  the correct/new behavior should be renew requests at:

  10:00
  13:45
  15:37
  16:37

  and then rebind requests at:

  17:30
  18:45
  19:45

  and then lease expiration at 20:00.

  longer lease times would increase the number of retransmissions.

  [regression potential]

  any regression would likely result in problems receiving and/or
  maintaining a dhcpv4 address

  [scope]

  this is needed in b/f/g/h.

  this was fixed upstream in:
  https://github.com/systemd/systemd/pull/17908

  that was just added, so this is not fixed in any ubuntu release yet.

  technically, this is needed in x as well, however I don't plan to
  backport to x since 1) it reaches ESM soon and 2) the default network
  management tool in x is ifupdown, not systemd-networkd.

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

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

[Touch-packages] [Bug 1713017] Re: Enable MIDI support

[wvengen]

As far as I can see, it is still disabled by default [in kernel
bluez](https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/configure.ac#n243)
nor [in
launchpad](https://git.launchpad.net/bluez/tree/configure.ac#n239),
neither do I find in being enabled explicitely in a package (but could
not so easily find the package code online).

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

Title:
  Enable MIDI support

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Now that bluez has landed with 5.46-0ubuntu2, it would be nice to
  enable Bluetooth MIDI support. This did not seem to be enabled by
  default in the build from
  https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE
  MIDI devices, gatttool could talk to them, but no MIDI device was
  made; also ldd showed no linkage to libasound.so.2).

  After recompiling it with libasound2-dev installed and --enable-midi
  in debian/rules, it worked.

  Suggestion: add libasound2-dev to bluez dependencies, add --enable-
  midi to rules.

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

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

[Touch-packages] [Bug 1878955] Autopkgtest regression report (systemd/237-3ubuntu10.44)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.44) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-azure-4.15/4.15.0-1104.116 (amd64)
munin/2.0.37-1ubuntu0.1 (arm64)
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
libvirt/4.0.0-1ubuntu8.17 (i386)
apt/1.6.12ubuntu0.2 (armhf)
netplan.io/0.99-0ubuntu3~18.04.3 (amd64)
linux-hwe-5.0/5.0.0-63.69 (armhf)
openssh/1:7.6p1-4ubuntu0.3 (armhf, s390x, ppc64el, arm64, i386, amd64)
corosync/2.4.3-0ubuntu1.1 (armhf)
nut/2.7.4-5.1ubuntu2 (i386)


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#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1878955

Title:
  resolved dhclient-enter-hook complains about an empty file

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  [test case]

  run dhclient for the first time (for the current boot) on a
  bionic/focal system, or remove the file(s) in
  /run/systemd/resolved.conf.d/ starting with 'isc-dhcp-*', and then run
  dhclient.

  [regression potential]

  any regression would likely cause the DNS configuration that dhclient
  gets to not be properly reported to systemd-resolved, resulting in
  problematic/broken systemd DNS resolution.

  [scope]

  this is needed in b/f

  this hook was removed from systemd starting in g, and the hook was not
  yet added in x, so this change is needed only in b and f.

  [original description]

  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter-
  hooks.d/resolved"

  Because the $oldstate file can be empty, or different, it should use
  `cmp --quiet`

  This happens when "/run/systemd/resolved.conf.d/isc-
  dhcp-v*-$interface.conf" files do not exist, or when the content
  changes.

  This is very loosely related to
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183

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

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

[Touch-packages] [Bug 1892358] Autopkgtest regression report (systemd/246.6-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.1) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.46.1-1ubuntu1 (arm64, amd64)
prometheus/2.20.0+ds-1 (s390x)
netplan.io/0.100-0ubuntu5 (arm64)
flatpak/1.8.2-1 (arm64)


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/groovy/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1892358

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
    ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
    s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
    arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 

[Touch-packages] [Bug 1905044] Autopkgtest regression report (systemd/246.6-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.1) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.46.1-1ubuntu1 (arm64, amd64)
prometheus/2.20.0+ds-1 (s390x)
netplan.io/0.100-0ubuntu5 (arm64)
flatpak/1.8.2-1 (arm64)


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/groovy/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1905044

Title:
  systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  autopkgtest failure when running with 5.8 kernel, if systemd is built
  with earlier kernel (e.g. 5.4)

  [test case]

  see autopkgtest results, e.g. links in original description below

  [regression potential]

  as this only fixes a test case, any regression would likely result in
  an incorrectly passing, or incorrectly failing, test.

  [scope]

  this is needed for b/f/g/h.

  this bug was introduced by upstream commit 23cc81e7c22 which first
  added testing for 'invalid' cap numbers, but incorrectly using
  capability_list_length() instead of cap_last_cap(). That commit was
  first included in v236, so this bug does not exist before Bionic.

  this is fixed upstream by commit
  ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in
  v247, so this is needed for h and earlier.

  Also note that even though the 5.8 kernel is not planned to be
  released for Bionic, this test also runs at build time, and since the
  LP build farm builds inside chroots, if the build farm ever moved up
  to Focal with a 5.8 kernel, the build of systemd for Bionic would
  start failing (since it would still be building using the older kernel
  headers, inside the chroot), so this does need to be fixed in Bionic
  systemd as well.

  [other info]

  there is a non-test bug related to this in bug 1905245

  [original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz

  The failing testcases are:

  - root-unittests

  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  FAIL: test-cap-list (code: 134)

  - upstream

  TEST-24-UNIT-TESTS:

  --- test-cap-list begin ---
  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  --- test-cap-list end ---

  Both seem to be failing with the same assertion.

  These tests are successful on Focal with linux 5.4, therefore they
  would regress when upgrading the kernel from 5.4 to 5.8.

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

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

[Touch-packages] [Bug 1905245] Autopkgtest regression report (systemd/237-3ubuntu10.44)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.44) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-azure-4.15/4.15.0-1104.116 (amd64)
munin/2.0.37-1ubuntu0.1 (arm64)
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
libvirt/4.0.0-1ubuntu8.17 (i386)
apt/1.6.12ubuntu0.2 (armhf)
netplan.io/0.99-0ubuntu3~18.04.3 (amd64)
linux-hwe-5.0/5.0.0-63.69 (armhf)
openssh/1:7.6p1-4ubuntu0.3 (armhf, s390x, ppc64el, arm64, i386, amd64)
corosync/2.4.3-0ubuntu1.1 (armhf)
nut/2.7.4-5.1ubuntu2 (i386)


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#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1905245

Title:
  "Failed to parse bus message: Invalid argument" with Linux 5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  newer kernels introduced a new capability, and existing systemd
  doesn't have the name mapping for the new cap (since the mapping table
  is generated at systemd compile time), so it fails when trying to map
  the capability to a user-facing name, which causes failure when
  running commands like 'systemctl show'

  [test case]

  install a focal system, and install the 5.8 (or newer) kernel, e.g.
  from linux-generic-hwe-20.04-edge, and reboot into the new kernel.

  Find any service that does not specify its CapabilityBoundingSet; e.g.
  'apparmor', and run systemctl show on it:

  ubuntu@lp1905245-f:~$ systemctl show -p CapabilityBoundingSet apparmor
  Failed to parse bus message: Invalid argument

  the command should correctly show the value, e.g.:
  $ systemctl show -p CapabilityBoundingSet apparmor
  CapabilityBoundingSet=cap_chown cap_dac_override ...etc...

  [regression potential]

  a regression would likely occur while systemd is parsing or printing
  or otherwise handling kernel capabilities. A regression could happen
  when running systemd commands, such as systemctl, or when pid1 is
  managing services.

  [scope]

  this is needed only in focal and bionic.

  This is fixed upstream by PR 16424:
  https://github.com/systemd/systemd/pull/16424
  which was first included in v246, so this is already fixed in groovy and 
later.

  This was introduced upstream in systemd by commit
  52610b020c077ee769c6923249f7e6c4e99d2980 which was first included in
  v235, so this bug does not exist in Xenial.

  This bug will reproduce on any system running under the 5.8 kernel,
  with the new capability, if the systemd binary was compiled with
  kernel headers that do not include the new capability. This means this
  is reproducable on bare-metal/vm instances running 5.8, as well as
  containers on hosts running 5.8. Therefore, while bionic may not ever
  receive a new kernel with added capability, it still needs to be
  patched to avoid the bug on a bionic container running on a host with
  the 5.8 kernel.

  [other info]

  there is a testcase-only related bug 1905044

  [original description]

  When I run `systemctl show myservice.service`, I get the following
  error message:

     Failed to parse bus message: Invalid argument

  systemd version: 245.4-4ubuntu3.3
  linux version: 5.8.0-29-generic #31~20.04.1-Ubuntu  (From 
linux-generic-hwe-20.04-edge)

  This is a bug that has been fixed in Debian. See
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964926

  Please can we port the fix to the ubuntu 20.04 version.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Autopkgtest regression report (systemd/246.6-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.1) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.46.1-1ubuntu1 (arm64, amd64)
prometheus/2.20.0+ds-1 (s390x)
netplan.io/0.100-0ubuntu5 (arm64)
flatpak/1.8.2-1 (arm64)


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/groovy/update_excuses.html#systemd

[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 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 cloud-images:
  New
Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Incomplete
Status in systemd source package in Focal:
  Fix Committed
Status in cloud-init source package in Groovy:
  Incomplete
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  on boot of a specific azure instance, the ID_NET_DRIVER parameter of
  the instance's eth0 interface is not set. That leads to a failure of
  systemd-networkd to take control of the interface after a restart of
  systemd-networkd, which results in DNS failures (at first) and
  eventually complete loss of networking (once the DHCP lease expires).

  [test case]

  this occurs on first boot of an instance using the specific image; it
  is not reproducable using the latest ubuntu image nor any reboot of
  the affected image, and it has not been reproducable (for me) when
  using debug-enabled images based on the affected image.

  So, while the problem is reproducable using the specific image in
  question, it's not possible to verify the fix since any change to the
  image removes reproducability.

  however, while the problem itself can't be reproduced and then
  verified, if the assumption is correct (that the 'add' uevent is being
  missed on boot), that is possible to test and verify:

  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  E: ID_NET_DRIVER=hv_netvsc
  $ sudo rm /run/udev/data/n2 

  (note, change 'n2' to whichever network interface index is correct)

  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  $ sudo udevadm trigger -c change /sys/class/net/eth0
  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER

  (note the 'change' uevent did not populate ID_NET_DRIVER property)

  $ sudo udevadm trigger -c add /sys/class/net/eth0
  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  E: ID_NET_DRIVER=hv_netvsc

  (note the 'add' uevent did populate ID_NET_DRIVER)

  the test verification should result in ID_NET_DRIVER being populated
  for a 'change' uevent.

  [regression potential]

  any regression would likely involve problems with systemd-udevd
  processing 'change' events from network devices, and/or incorrect
  udevd device properties.

  [scope]

  this is needed only for focal and groovy.

  this is fixed by upstream commit e0e789c1e97 which is first included
  in v247, so this is fixed already in hirsute.

  while this commit is not included in bionic, due to the difficult
  nature of reproducing (and verifying) this, and the fact it has only
  been seen once on a focal image, I don't think it's appropriate to SRU
  to bionic at this point; possibly it may be appropriate if this is
  ever reproduced with a bionic image.

  [other info]

  note that this bug's subject and description, as well as the upstream
  systemd bug subject and description, talk about the problem being DNS
  resolution. However that is strictly a side-effect of the real problem
  and is not the actual issue.

  [original 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):

  

[Touch-packages] [Bug 1881947] Autopkgtest regression report (systemd/237-3ubuntu10.44)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.44) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-azure-4.15/4.15.0-1104.116 (amd64)
munin/2.0.37-1ubuntu0.1 (arm64)
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
libvirt/4.0.0-1ubuntu8.17 (i386)
apt/1.6.12ubuntu0.2 (armhf)
netplan.io/0.99-0ubuntu3~18.04.3 (amd64)
linux-hwe-5.0/5.0.0-63.69 (armhf)
openssh/1:7.6p1-4ubuntu0.3 (armhf, s390x, ppc64el, arm64, i386, amd64)
corosync/2.4.3-0ubuntu1.1 (armhf)
nut/2.7.4-5.1ubuntu2 (i386)


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#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1881947

Title:
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Autopkgtest fails due to corrupted journal file

  [Test Case]

   * Observe autopkgtest root-unittests not failing with:

  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

  [Where problems could occur]

   * The change has no impact on the systemd binary packages. The
  relaxed test could hide a journal corruption problem, but it seems the
  corrupted journal files occur only on arm64 probably due to arm64
  reboots being resets: LP: #1748280.

  [Original Bug Text]

  Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz

  [...]
  PASS: test-journal-enum
  == test-journal-flush ===
  Root directory /var/log/journal removed.
  Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed.
  mmap cache statistics: 739 hit, 5 miss
  journal_file_copy_entry failed: Bad message
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function 
main(). Aborting.
  FAIL: test-journal-flush (code: 134)
  Aborted (core dumped)
  == test-journal-importer ===
  [...]
  autopkgtest [07:17:29]:  summary
  timedatedPASS
  hostnamedPASS
  localed-locale   PASS
  localed-x11-keymap   PASS
  logind   PASS
  unit-config  PASS
  storage  PASS
  networkd-test.py PASS
  build-login  PASS
  boot-and-servicesPASS
  udev PASS
  root-unittests   FAIL non-zero exit status 134
  upstream PASS
  boot-smoke   PASS
  systemd-fsckdPASS
  Exit request sent.
  [...]

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

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

[Touch-packages] [Bug 1905044] Autopkgtest regression report (systemd/237-3ubuntu10.44)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.44) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-azure-4.15/4.15.0-1104.116 (amd64)
munin/2.0.37-1ubuntu0.1 (arm64)
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
libvirt/4.0.0-1ubuntu8.17 (i386)
apt/1.6.12ubuntu0.2 (armhf)
netplan.io/0.99-0ubuntu3~18.04.3 (amd64)
linux-hwe-5.0/5.0.0-63.69 (armhf)
openssh/1:7.6p1-4ubuntu0.3 (armhf, s390x, ppc64el, arm64, i386, amd64)
corosync/2.4.3-0ubuntu1.1 (armhf)
nut/2.7.4-5.1ubuntu2 (i386)


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#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1905044

Title:
  systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  autopkgtest failure when running with 5.8 kernel, if systemd is built
  with earlier kernel (e.g. 5.4)

  [test case]

  see autopkgtest results, e.g. links in original description below

  [regression potential]

  as this only fixes a test case, any regression would likely result in
  an incorrectly passing, or incorrectly failing, test.

  [scope]

  this is needed for b/f/g/h.

  this bug was introduced by upstream commit 23cc81e7c22 which first
  added testing for 'invalid' cap numbers, but incorrectly using
  capability_list_length() instead of cap_last_cap(). That commit was
  first included in v236, so this bug does not exist before Bionic.

  this is fixed upstream by commit
  ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in
  v247, so this is needed for h and earlier.

  Also note that even though the 5.8 kernel is not planned to be
  released for Bionic, this test also runs at build time, and since the
  LP build farm builds inside chroots, if the build farm ever moved up
  to Focal with a 5.8 kernel, the build of systemd for Bionic would
  start failing (since it would still be building using the older kernel
  headers, inside the chroot), so this does need to be fixed in Bionic
  systemd as well.

  [other info]

  there is a non-test bug related to this in bug 1905245

  [original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz

  The failing testcases are:

  - root-unittests

  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  FAIL: test-cap-list (code: 134)

  - upstream

  TEST-24-UNIT-TESTS:

  --- test-cap-list begin ---
  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  --- test-cap-list end ---

  Both seem to be failing with the same assertion.

  These tests are successful on Focal with linux 5.4, therefore they
  would regress when upgrading the kernel from 5.4 to 5.8.

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

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

[Touch-packages] [Bug 1907306] Autopkgtest regression report (systemd/246.6-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.1) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.46.1-1ubuntu1 (arm64, amd64)
prometheus/2.20.0+ds-1 (s390x)
netplan.io/0.100-0ubuntu5 (arm64)
flatpak/1.8.2-1 (arm64)


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/groovy/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1907306

Title:
  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

  [test case]

  configure an interface to use dhcpv4; acquire a dhcpv4 address, then
  stop the dhcpv4 server, and wait for the networkd client to perform
  its renewals and rebinds before expiring the lease

  using a 20 minute lease time as an example (all times are approximate
  due to RFC-mandated random 'fuzz' time of -1 to +1 sec):

  the current behavior would be to sent renew requests at:

  10:00
  13:45

  and then rebind requests at:

  17:30
  18:45

  then the lease would expire at 20:00

  the correct/new behavior should be renew requests at:

  10:00
  13:45
  15:37
  16:37

  and then rebind requests at:

  17:30
  18:45
  19:45

  and then lease expiration at 20:00.

  longer lease times would increase the number of retransmissions.

  [regression potential]

  any regression would likely result in problems receiving and/or
  maintaining a dhcpv4 address

  [scope]

  this is needed in b/f/g/h.

  this was fixed upstream in:
  https://github.com/systemd/systemd/pull/17908

  that was just added, so this is not fixed in any ubuntu release yet.

  technically, this is needed in x as well, however I don't plan to
  backport to x since 1) it reaches ESM soon and 2) the default network
  management tool in x is ifupdown, not systemd-networkd.

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

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

[Touch-packages] [Bug 1908067] Autopkgtest regression report (systemd/246.6-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.1) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.46.1-1ubuntu1 (arm64, amd64)
prometheus/2.20.0+ds-1 (s390x)
netplan.io/0.100-0ubuntu5 (arm64)
flatpak/1.8.2-1 (arm64)


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/groovy/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1908067

Title:
  systemd-fsckd test fails on groovy checking plymouth-start isactive

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  systemd-fsckd test fails on groovy because plymouth-start service is
  active

  [test case]

  check autopkgtest logs of systemd-fsckd test case on groovy

  [regression potential]

  incorrectly passed, or failed, systemd-fsckd test

  [scope]

  this is needed only for groovy.

  the plymouth-start.service did not include RemainAfterExit=true before 
groovy, so the service is expected to be inactive when checked by the test 
before groovy. this is already fixed in hirsute:
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c46eda821e97df5595a4cdc5f5c41a9b49a51745

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

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

[Touch-packages] [Bug 1910928] Re: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

[edzzzu]

I'm afraid - i ran the command previously while bug was not present.
Yes - I can run bluetoothctl command.

Here is the output of the command: "ps -aux | grep bluetoothd"

root1686  0.0  0.0   9352  5200 ?Ss   12:26   0:00 
/usr/lib/bluetooth/bluetoothd
ubuntu  7426  0.0  0.0  17660   876 pts/0S+   12:33   0:00 grep 
--color=auto bluetoothd

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] UdevDb.txt

[edzzzu]

apport information

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] acpidump.txt

[edzzzu]

apport information

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] ProcCpuinfo.txt

[edzzzu]

apport information

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] rfkill.txt

[edzzzu]

apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1910928/+attachment/5452258/+files/rfkill.txt

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] syslog.txt

[edzzzu]

apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1910928/+attachment/5452259/+files/syslog.txt

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] getfacl.txt

[edzzzu]

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1910928/+attachment/5452257/+files/getfacl.txt

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] ProcModules.txt

[edzzzu]

apport information

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] ProcInterrupts.txt

[edzzzu]

apport information

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

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

[edzzzu]

apport information

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] Re: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

[edzzzu]

apport information

** Description changed:

  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CasperVersion: 1.455
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.10
+ InterestingModules: rfcomm bnep btusb bluetooth
+ LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ MachineType: LENOVO 20SL
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: bluez 5.55-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
+ ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
+ Tags:  groovy
+ Uname: Linux 5.8.0-25-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/18/2020
+ dmi.bios.release: 1.22
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: DJCN22WW
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: NO DPK
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo ThinkBook 14-IIL
+ dmi.ec.firmware.release: 1.18
+ dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
+ dmi.product.family: Thinkbook 14-IIL
+ dmi.product.name: 20SL
+ dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
+ dmi.product.version: Lenovo ThinkBook 14-IIL
+ dmi.sys.vendor: LENOVO
+ hciconfig:

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp 

[Touch-packages] [Bug 1910928] Lsusb-v.txt

[edzzzu]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1910928/+attachment/5452250/+files/Lsusb-v.txt

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] Lsusb-t.txt

[edzzzu]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1910928/+attachment/5452249/+files/Lsusb-t.txt

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] Lsusb.txt

[edzzzu]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1910928/+attachment/5452248/+files/Lsusb.txt

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] Lspci-vt.txt

[edzzzu]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1910928/+attachment/5452247/+files/Lspci-vt.txt

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] Lspci.txt

[edzzzu]

apport information

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1910928] Dependencies.txt

[edzzzu]

apport information

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1911187] Re: scheduled reboot reboots immediately if dbus or logind is not available

[Ioanna Alifieraki]

** Description changed:

  [IMPACT]
  
  When, for whatever reason, logind or dbus is not available scheduled reboot 
reboots the machine immediately.
  From the sources it seems that this is intended :
  
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
  However, I report this as a bug since this is against the logic of a 
scheduled reboot; if someone schedules a reboot they want the system to reboot 
at the specified time not immediately.
  
- There has been a discussion upstream ( 
https://github.com/systemd/systemd/issues/17575 ) and 
+ There has been a discussion upstream ( 
https://github.com/systemd/systemd/issues/17575 ) and
  a PR ( https://github.com/systemd/systemd/pull/18010 ).
  
  Upstream community is not willing to accept the patch but debian is.
  I open this bug to to pull the patch into Ubuntu once it lands in debian.
  
  [TEST CASE]
  
  The simpler reproducer is to disable dbus to imitate the real world
  case.
  
  # systemctl stop dbus.service
  # systemctl stop dbus.socket
  # shutdown +1140 -r "REBOOT!"
  Failed to set wall message, ignoring: Failed to activate service 
'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Connection timed out
  Connection to groovy closed by remote host.
  Connection to groovy closed.
  
- 
  [REGRESSION POTENTIAL]
  
  The patch has minimal regression potential since it just takes no action
  ( instead of shutting down ) when bus_call_method fails.
  
  [OTHER]
  
+ Debian bug reports : 
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
+ 
  Upstream issue : https://github.com/systemd/systemd/issues/17575
  PR : https://github.com/systemd/systemd/pull/18010

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

Title:
  scheduled reboot reboots immediately if dbus or logind is not
  available

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [IMPACT]

  When, for whatever reason, logind or dbus is not available scheduled reboot 
reboots the machine immediately.
  From the sources it seems that this is intended :
  
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
  However, I report this as a bug since this is against the logic of a 
scheduled reboot; if someone schedules a reboot they want the system to reboot 
at the specified time not immediately.

  There has been a discussion upstream ( 
https://github.com/systemd/systemd/issues/17575 ) and
  a PR ( https://github.com/systemd/systemd/pull/18010 ).

  Upstream community is not willing to accept the patch but debian is.
  I open this bug to to pull the patch into Ubuntu once it lands in debian.

  [TEST CASE]

  The simpler reproducer is to disable dbus to imitate the real world
  case.

  # systemctl stop dbus.service
  # systemctl stop dbus.socket
  # shutdown +1140 -r "REBOOT!"
  Failed to set wall message, ignoring: Failed to activate service 
'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Connection timed out
  Connection to groovy closed by remote host.
  Connection to groovy closed.

  [REGRESSION POTENTIAL]

  The patch has minimal regression potential since it just takes no
  action ( instead of shutting down ) when bus_call_method fails.

  [OTHER]

  Debian bug reports : 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042

  Upstream issue : https://github.com/systemd/systemd/issues/17575
  PR : https://github.com/systemd/systemd/pull/18010

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

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

[Touch-packages] [Bug 1881947] Autopkgtest regression report (systemd/245.4-4ubuntu3.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.4) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-37.42~20.04.1 (arm64)
netplan.io/0.100-0ubuntu4~20.04.3 (amd64)
apt/2.0.2ubuntu0.2 (armhf)
munin/2.0.56-1ubuntu1 (ppc64el)
gvfs/1.44.1-1ubuntu1 (amd64, arm64)
prometheus-alertmanager/0.15.3+ds-3ubuntu1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (ppc64el)
pyudev/0.21.0-3ubuntu1 (s390x)


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/focal/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1881947

Title:
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Autopkgtest fails due to corrupted journal file

  [Test Case]

   * Observe autopkgtest root-unittests not failing with:

  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

  [Where problems could occur]

   * The change has no impact on the systemd binary packages. The
  relaxed test could hide a journal corruption problem, but it seems the
  corrupted journal files occur only on arm64 probably due to arm64
  reboots being resets: LP: #1748280.

  [Original Bug Text]

  Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz

  [...]
  PASS: test-journal-enum
  == test-journal-flush ===
  Root directory /var/log/journal removed.
  Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed.
  mmap cache statistics: 739 hit, 5 miss
  journal_file_copy_entry failed: Bad message
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function 
main(). Aborting.
  FAIL: test-journal-flush (code: 134)
  Aborted (core dumped)
  == test-journal-importer ===
  [...]
  autopkgtest [07:17:29]:  summary
  timedatedPASS
  hostnamedPASS
  localed-locale   PASS
  localed-x11-keymap   PASS
  logind   PASS
  unit-config  PASS
  storage  PASS
  networkd-test.py PASS
  build-login  PASS
  boot-and-servicesPASS
  udev PASS
  root-unittests   FAIL non-zero exit status 134
  upstream PASS
  boot-smoke   PASS
  systemd-fsckdPASS
  Exit request sent.
  [...]

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

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

[Touch-packages] [Bug 1878955] Autopkgtest regression report (systemd/245.4-4ubuntu3.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.4) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-37.42~20.04.1 (arm64)
netplan.io/0.100-0ubuntu4~20.04.3 (amd64)
apt/2.0.2ubuntu0.2 (armhf)
munin/2.0.56-1ubuntu1 (ppc64el)
gvfs/1.44.1-1ubuntu1 (amd64, arm64)
prometheus-alertmanager/0.15.3+ds-3ubuntu1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (ppc64el)
pyudev/0.21.0-3ubuntu1 (s390x)


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/focal/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1878955

Title:
  resolved dhclient-enter-hook complains about an empty file

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  [test case]

  run dhclient for the first time (for the current boot) on a
  bionic/focal system, or remove the file(s) in
  /run/systemd/resolved.conf.d/ starting with 'isc-dhcp-*', and then run
  dhclient.

  [regression potential]

  any regression would likely cause the DNS configuration that dhclient
  gets to not be properly reported to systemd-resolved, resulting in
  problematic/broken systemd DNS resolution.

  [scope]

  this is needed in b/f

  this hook was removed from systemd starting in g, and the hook was not
  yet added in x, so this change is needed only in b and f.

  [original description]

  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter-
  hooks.d/resolved"

  Because the $oldstate file can be empty, or different, it should use
  `cmp --quiet`

  This happens when "/run/systemd/resolved.conf.d/isc-
  dhcp-v*-$interface.conf" files do not exist, or when the content
  changes.

  This is very loosely related to
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183

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

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

[Touch-packages] [Bug 1903300] Autopkgtest regression report (systemd/245.4-4ubuntu3.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.4) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-37.42~20.04.1 (arm64)
netplan.io/0.100-0ubuntu4~20.04.3 (amd64)
apt/2.0.2ubuntu0.2 (armhf)
munin/2.0.56-1ubuntu1 (ppc64el)
gvfs/1.44.1-1ubuntu1 (amd64, arm64)
prometheus-alertmanager/0.15.3+ds-3ubuntu1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (ppc64el)
pyudev/0.21.0-3ubuntu1 (s390x)


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/focal/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1903300

Title:
  systemd-networkd silently fails to set vxlan multicast group

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  setting VXLAN.Group does not correctly configure multicast group

  [test case]

  taken from upstream bug, example networkd config:

  [NetDev]
  Kind=vxlan
  Name=myvx

  [VXLAN]
  VNI=1
  Group=ff02::42:1
  DestinationPort=8472

  After restarting systemd-networkd the VXLAN device is created, but the
  group address is not assigned. Use ip -d link show myvx and networkctl
  show myvx to verify.

  [regression potential]

  any regression would likely cause problems only with VXLAN netdevs
  created by networkd.

  [scope]

  this is needed only for f.

  this was introduced by upstream commit 83cb24ac20b which was first in
  v243, so this bug does not exist in b and earlier.

  this was fixed by upstream commit
  7c9b26900cc33daf080627daf5904de74c1ef267 (and two following commits)
  which were first included in v246, so this is already fixed in g and
  later.

  [original description]

  
  Fixed upstream, please include [1].

  Thank you.

  [1] https://github.com/systemd/systemd/pull/15397

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  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.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov  6 14:16:19 2020
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=97786d27-c04a-4592-a087-f19a689468a9 ro console=tty1 console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-08-27 (70 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.1:cvnQEMU:ct1:cvrpc-q35-5.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.1
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1907306] Autopkgtest regression report (systemd/245.4-4ubuntu3.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.4) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-37.42~20.04.1 (arm64)
netplan.io/0.100-0ubuntu4~20.04.3 (amd64)
apt/2.0.2ubuntu0.2 (armhf)
munin/2.0.56-1ubuntu1 (ppc64el)
gvfs/1.44.1-1ubuntu1 (amd64, arm64)
prometheus-alertmanager/0.15.3+ds-3ubuntu1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (ppc64el)
pyudev/0.21.0-3ubuntu1 (s390x)


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/focal/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1907306

Title:
  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

  [test case]

  configure an interface to use dhcpv4; acquire a dhcpv4 address, then
  stop the dhcpv4 server, and wait for the networkd client to perform
  its renewals and rebinds before expiring the lease

  using a 20 minute lease time as an example (all times are approximate
  due to RFC-mandated random 'fuzz' time of -1 to +1 sec):

  the current behavior would be to sent renew requests at:

  10:00
  13:45

  and then rebind requests at:

  17:30
  18:45

  then the lease would expire at 20:00

  the correct/new behavior should be renew requests at:

  10:00
  13:45
  15:37
  16:37

  and then rebind requests at:

  17:30
  18:45
  19:45

  and then lease expiration at 20:00.

  longer lease times would increase the number of retransmissions.

  [regression potential]

  any regression would likely result in problems receiving and/or
  maintaining a dhcpv4 address

  [scope]

  this is needed in b/f/g/h.

  this was fixed upstream in:
  https://github.com/systemd/systemd/pull/17908

  that was just added, so this is not fixed in any ubuntu release yet.

  technically, this is needed in x as well, however I don't plan to
  backport to x since 1) it reaches ESM soon and 2) the default network
  management tool in x is ifupdown, not systemd-networkd.

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

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

[Touch-packages] [Bug 1890448] Autopkgtest regression report (systemd/245.4-4ubuntu3.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.4) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-37.42~20.04.1 (arm64)
netplan.io/0.100-0ubuntu4~20.04.3 (amd64)
apt/2.0.2ubuntu0.2 (armhf)
munin/2.0.56-1ubuntu1 (ppc64el)
gvfs/1.44.1-1ubuntu1 (amd64, arm64)
prometheus-alertmanager/0.15.3+ds-3ubuntu1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (ppc64el)
pyudev/0.21.0-3ubuntu1 (s390x)


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/focal/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890448

Title:
  hwdb: Add EliteBook to use micmute hotkey

Status in HWE Next:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP EliteBooks don't work.

  [Fix]
  Commit b6eb208b29ae ("hwdb: Add EliteBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the EliteBooks I tested.

  [Regression Potential]
  The hwdb originally only matches a few EliteBook, and fix changes that to 
match all EliteBook models. So if there's an EliteBook that uses the scancode 
for other purpose, there will be a regression.
  However, the risk is rather slim because HP is confident that all EliteBooks 
use the same scancode for mic mute hotkey.

  [scope]

  this is needed for f and earlier.

  this is fixed upstream by commit b6eb208b29ae which is included
  starting in v246, so g and later are already fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890448/+subscriptions

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

[Touch-packages] [Bug 1905044] Autopkgtest regression report (systemd/245.4-4ubuntu3.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.4) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-37.42~20.04.1 (arm64)
netplan.io/0.100-0ubuntu4~20.04.3 (amd64)
apt/2.0.2ubuntu0.2 (armhf)
munin/2.0.56-1ubuntu1 (ppc64el)
gvfs/1.44.1-1ubuntu1 (amd64, arm64)
prometheus-alertmanager/0.15.3+ds-3ubuntu1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (ppc64el)
pyudev/0.21.0-3ubuntu1 (s390x)


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/focal/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1905044

Title:
  systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  autopkgtest failure when running with 5.8 kernel, if systemd is built
  with earlier kernel (e.g. 5.4)

  [test case]

  see autopkgtest results, e.g. links in original description below

  [regression potential]

  as this only fixes a test case, any regression would likely result in
  an incorrectly passing, or incorrectly failing, test.

  [scope]

  this is needed for b/f/g/h.

  this bug was introduced by upstream commit 23cc81e7c22 which first
  added testing for 'invalid' cap numbers, but incorrectly using
  capability_list_length() instead of cap_last_cap(). That commit was
  first included in v236, so this bug does not exist before Bionic.

  this is fixed upstream by commit
  ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in
  v247, so this is needed for h and earlier.

  Also note that even though the 5.8 kernel is not planned to be
  released for Bionic, this test also runs at build time, and since the
  LP build farm builds inside chroots, if the build farm ever moved up
  to Focal with a 5.8 kernel, the build of systemd for Bionic would
  start failing (since it would still be building using the older kernel
  headers, inside the chroot), so this does need to be fixed in Bionic
  systemd as well.

  [other info]

  there is a non-test bug related to this in bug 1905245

  [original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz

  The failing testcases are:

  - root-unittests

  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  FAIL: test-cap-list (code: 134)

  - upstream

  TEST-24-UNIT-TESTS:

  --- test-cap-list begin ---
  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  --- test-cap-list end ---

  Both seem to be failing with the same assertion.

  These tests are successful on Focal with linux 5.4, therefore they
  would regress when upgrading the kernel from 5.4 to 5.8.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Autopkgtest regression report (systemd/245.4-4ubuntu3.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.4) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-37.42~20.04.1 (arm64)
netplan.io/0.100-0ubuntu4~20.04.3 (amd64)
apt/2.0.2ubuntu0.2 (armhf)
munin/2.0.56-1ubuntu1 (ppc64el)
gvfs/1.44.1-1ubuntu1 (amd64, arm64)
prometheus-alertmanager/0.15.3+ds-3ubuntu1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (ppc64el)
pyudev/0.21.0-3ubuntu1 (s390x)


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/focal/update_excuses.html#systemd

[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 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 cloud-images:
  New
Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Incomplete
Status in systemd source package in Focal:
  Fix Committed
Status in cloud-init source package in Groovy:
  Incomplete
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  on boot of a specific azure instance, the ID_NET_DRIVER parameter of
  the instance's eth0 interface is not set. That leads to a failure of
  systemd-networkd to take control of the interface after a restart of
  systemd-networkd, which results in DNS failures (at first) and
  eventually complete loss of networking (once the DHCP lease expires).

  [test case]

  this occurs on first boot of an instance using the specific image; it
  is not reproducable using the latest ubuntu image nor any reboot of
  the affected image, and it has not been reproducable (for me) when
  using debug-enabled images based on the affected image.

  So, while the problem is reproducable using the specific image in
  question, it's not possible to verify the fix since any change to the
  image removes reproducability.

  however, while the problem itself can't be reproduced and then
  verified, if the assumption is correct (that the 'add' uevent is being
  missed on boot), that is possible to test and verify:

  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  E: ID_NET_DRIVER=hv_netvsc
  $ sudo rm /run/udev/data/n2 

  (note, change 'n2' to whichever network interface index is correct)

  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  $ sudo udevadm trigger -c change /sys/class/net/eth0
  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER

  (note the 'change' uevent did not populate ID_NET_DRIVER property)

  $ sudo udevadm trigger -c add /sys/class/net/eth0
  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  E: ID_NET_DRIVER=hv_netvsc

  (note the 'add' uevent did populate ID_NET_DRIVER)

  the test verification should result in ID_NET_DRIVER being populated
  for a 'change' uevent.

  [regression potential]

  any regression would likely involve problems with systemd-udevd
  processing 'change' events from network devices, and/or incorrect
  udevd device properties.

  [scope]

  this is needed only for focal and groovy.

  this is fixed by upstream commit e0e789c1e97 which is first included
  in v247, so this is fixed already in hirsute.

  while this commit is not included in bionic, due to the difficult
  nature of reproducing (and verifying) this, and the fact it has only
  been seen once on a focal image, I don't think it's appropriate to SRU
  to bionic at this point; possibly it may be appropriate if this is
  ever reproduced with a bionic image.

  [other info]

  note that this bug's subject and description, as well as the upstream
  systemd bug subject and description, talk about the problem being DNS
  resolution. However that is strictly a side-effect of the real problem
  and is not the actual issue.

  [original 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
 

[Touch-packages] [Bug 1905245] Autopkgtest regression report (systemd/245.4-4ubuntu3.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.4) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-37.42~20.04.1 (arm64)
netplan.io/0.100-0ubuntu4~20.04.3 (amd64)
apt/2.0.2ubuntu0.2 (armhf)
munin/2.0.56-1ubuntu1 (ppc64el)
gvfs/1.44.1-1ubuntu1 (amd64, arm64)
prometheus-alertmanager/0.15.3+ds-3ubuntu1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (ppc64el)
pyudev/0.21.0-3ubuntu1 (s390x)


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/focal/update_excuses.html#systemd

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1905245

Title:
  "Failed to parse bus message: Invalid argument" with Linux 5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  newer kernels introduced a new capability, and existing systemd
  doesn't have the name mapping for the new cap (since the mapping table
  is generated at systemd compile time), so it fails when trying to map
  the capability to a user-facing name, which causes failure when
  running commands like 'systemctl show'

  [test case]

  install a focal system, and install the 5.8 (or newer) kernel, e.g.
  from linux-generic-hwe-20.04-edge, and reboot into the new kernel.

  Find any service that does not specify its CapabilityBoundingSet; e.g.
  'apparmor', and run systemctl show on it:

  ubuntu@lp1905245-f:~$ systemctl show -p CapabilityBoundingSet apparmor
  Failed to parse bus message: Invalid argument

  the command should correctly show the value, e.g.:
  $ systemctl show -p CapabilityBoundingSet apparmor
  CapabilityBoundingSet=cap_chown cap_dac_override ...etc...

  [regression potential]

  a regression would likely occur while systemd is parsing or printing
  or otherwise handling kernel capabilities. A regression could happen
  when running systemd commands, such as systemctl, or when pid1 is
  managing services.

  [scope]

  this is needed only in focal and bionic.

  This is fixed upstream by PR 16424:
  https://github.com/systemd/systemd/pull/16424
  which was first included in v246, so this is already fixed in groovy and 
later.

  This was introduced upstream in systemd by commit
  52610b020c077ee769c6923249f7e6c4e99d2980 which was first included in
  v235, so this bug does not exist in Xenial.

  This bug will reproduce on any system running under the 5.8 kernel,
  with the new capability, if the systemd binary was compiled with
  kernel headers that do not include the new capability. This means this
  is reproducable on bare-metal/vm instances running 5.8, as well as
  containers on hosts running 5.8. Therefore, while bionic may not ever
  receive a new kernel with added capability, it still needs to be
  patched to avoid the bug on a bionic container running on a host with
  the 5.8 kernel.

  [other info]

  there is a testcase-only related bug 1905044

  [original description]

  When I run `systemctl show myservice.service`, I get the following
  error message:

     Failed to parse bus message: Invalid argument

  systemd version: 245.4-4ubuntu3.3
  linux version: 5.8.0-29-generic #31~20.04.1-Ubuntu  (From 
linux-generic-hwe-20.04-edge)

  This is a bug that has been fixed in Debian. See
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964926

  Please can we port the fix to the ubuntu 20.04 version.

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

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

[Touch-packages] [Bug 1911187] [NEW] scheduled reboot reboots immediately if dbus or logind is not available

[Ioanna Alifieraki]

Public bug reported:

[IMPACT]

When, for whatever reason, logind or dbus is not available scheduled reboot 
reboots the machine immediately.
>From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled 
reboot; if someone schedules a reboot they want the system to reboot at the 
specified time not immediately.

There has been a discussion upstream ( 
https://github.com/systemd/systemd/issues/17575 ) and 
a PR ( https://github.com/systemd/systemd/pull/18010 ).

Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.

[TEST CASE]

The simpler reproducer is to disable dbus to imitate the real world
case.

# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 
'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: 
Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.


[REGRESSION POTENTIAL]

The patch has minimal regression potential since it just takes no action
( instead of shutting down ) when bus_call_method fails.

[OTHER]

Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010

** Affects: systemd (Ubuntu)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Confirmed


** Tags: sts

** Tags added: sts

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

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

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

Title:
  scheduled reboot reboots immediately if dbus or logind is not
  available

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [IMPACT]

  When, for whatever reason, logind or dbus is not available scheduled reboot 
reboots the machine immediately.
  From the sources it seems that this is intended :
  
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
  However, I report this as a bug since this is against the logic of a 
scheduled reboot; if someone schedules a reboot they want the system to reboot 
at the specified time not immediately.

  There has been a discussion upstream ( 
https://github.com/systemd/systemd/issues/17575 ) and 
  a PR ( https://github.com/systemd/systemd/pull/18010 ).

  Upstream community is not willing to accept the patch but debian is.
  I open this bug to to pull the patch into Ubuntu once it lands in debian.

  [TEST CASE]

  The simpler reproducer is to disable dbus to imitate the real world
  case.

  # systemctl stop dbus.service
  # systemctl stop dbus.socket
  # shutdown +1140 -r "REBOOT!"
  Failed to set wall message, ignoring: Failed to activate service 
'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Connection timed out
  Connection to groovy closed by remote host.
  Connection to groovy closed.

  
  [REGRESSION POTENTIAL]

  The patch has minimal regression potential since it just takes no
  action ( instead of shutting down ) when bus_call_method fails.

  [OTHER]

  Upstream issue : https://github.com/systemd/systemd/issues/17575
  PR : https://github.com/systemd/systemd/pull/18010

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

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

[Touch-packages] [Bug 1911137] Re: alt-tab not working after left mouse click

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  alt-tab not working after left mouse click

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  Steps:
  1. Click left mouse
  2. Wait for ~1 second
  3. Press and release Alt + Tab

  Actual: Stay on the same window/task/application
  Expected: Change to another window/task/application

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.snap-store.rules 
70-snap.canonical-livepatch.rules
  Date: Tue Jan 12 17:08:41 2021
  InstallationDate: Installed on 2021-01-09 (3 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude 5410
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=669124d8-c9e0-4fd0-a562-a35d8545db4c ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.2
  dmi.board.name: 06KF2W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 701428
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.2:bd11/09/2020:br1.4:svnDellInc.:pnLatitude5410:pvr:rvnDellInc.:rn06KF2W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5410
  dmi.product.sku: 09A0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1911137] [NEW] alt-tab not working after left mouse click

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu 20.04.1 LTS

Steps:
1. Click left mouse
2. Wait for ~1 second
3. Press and release Alt + Tab

Actual: Stay on the same window/task/application
Expected: Change to another window/task/application

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: udev 245.4-4ubuntu3.3
ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.snap-store.rules 
70-snap.canonical-livepatch.rules
Date: Tue Jan 12 17:08:41 2021
InstallationDate: Installed on 2021-01-09 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Latitude 5410
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=669124d8-c9e0-4fd0-a562-a35d8545db4c ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2020
dmi.bios.release: 1.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.2
dmi.board.name: 06KF2W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 701428
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.2:bd11/09/2020:br1.4:svnDellInc.:pnLatitude5410:pvr:rvnDellInc.:rn06KF2W:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5410
dmi.product.sku: 09A0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal
-- 
alt-tab not working after left mouse click
https://bugs.launchpad.net/bugs/1911137
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1910636] Re: update icu-data which is bundled in tzdata to 2020f

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2020f-0ubuntu0.20.04.1

---
tzdata (2020f-0ubuntu0.20.04.1) focal; urgency=medium

  * Update ICU timezone data files which are utilized by php to version 2020f.
(LP: #1910636)

 -- Brian Murray   Fri, 08 Jan 2021 08:19:33 -0800

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

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

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

Title:
  update icu-data which is bundled in tzdata to 2020f

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Groovy:
  Fix Released
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  The 2020f upload of tzdata did not include an update of the ICU
  timezone data because it was not yet up to date. It has now been
  updated so we should update tzdata with that new information.

  tzdata (2020f-1ubuntu1) hirsute; urgency=medium

    * Merge from Debian unstable (LP: 1909698). Remaining changes:
  - Ship ICU timezone data files which are utilized by php and keep them
    at 2020d as they have not yet been updated.

  [Test Case]
  1) sudo apt-get install python3-icu
  2) python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
  eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"

  Before the SRU it will return 3:00:00, after the SRU it will return
  4:00:00.

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

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

[Touch-packages] [Bug 1910636] Re: update icu-data which is bundled in tzdata to 2020f

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2020f-0ubuntu0.20.04.1

---
tzdata (2020f-0ubuntu0.20.04.1) focal; urgency=medium

  * Update ICU timezone data files which are utilized by php to version 2020f.
(LP: #1910636)

 -- Brian Murray   Fri, 08 Jan 2021 08:19:33 -0800

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

Title:
  update icu-data which is bundled in tzdata to 2020f

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Groovy:
  Fix Released
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  The 2020f upload of tzdata did not include an update of the ICU
  timezone data because it was not yet up to date. It has now been
  updated so we should update tzdata with that new information.

  tzdata (2020f-1ubuntu1) hirsute; urgency=medium

    * Merge from Debian unstable (LP: 1909698). Remaining changes:
  - Ship ICU timezone data files which are utilized by php and keep them
    at 2020d as they have not yet been updated.

  [Test Case]
  1) sudo apt-get install python3-icu
  2) python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
  eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"

  Before the SRU it will return 3:00:00, after the SRU it will return
  4:00:00.

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

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

[Touch-packages] [Bug 1910636] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  update icu-data which is bundled in tzdata to 2020f

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Groovy:
  Fix Released
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  The 2020f upload of tzdata did not include an update of the ICU
  timezone data because it was not yet up to date. It has now been
  updated so we should update tzdata with that new information.

  tzdata (2020f-1ubuntu1) hirsute; urgency=medium

    * Merge from Debian unstable (LP: 1909698). Remaining changes:
  - Ship ICU timezone data files which are utilized by php and keep them
    at 2020d as they have not yet been updated.

  [Test Case]
  1) sudo apt-get install python3-icu
  2) python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
  eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"

  Before the SRU it will return 3:00:00, after the SRU it will return
  4:00:00.

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

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

[Touch-packages] [Bug 1910636] Re: update icu-data which is bundled in tzdata to 2020f

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2020f-0ubuntu0.20.10.1

---
tzdata (2020f-0ubuntu0.20.10.1) groovy; urgency=medium

  * Update ICU timezone data files which are utilized by php to version 2020f.
(LP: #1910636)

 -- Brian Murray   Thu, 07 Jan 2021 19:54:53 -0800

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

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

Title:
  update icu-data which is bundled in tzdata to 2020f

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Groovy:
  Fix Released
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  The 2020f upload of tzdata did not include an update of the ICU
  timezone data because it was not yet up to date. It has now been
  updated so we should update tzdata with that new information.

  tzdata (2020f-1ubuntu1) hirsute; urgency=medium

    * Merge from Debian unstable (LP: 1909698). Remaining changes:
  - Ship ICU timezone data files which are utilized by php and keep them
    at 2020d as they have not yet been updated.

  [Test Case]
  1) sudo apt-get install python3-icu
  2) python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
  eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"

  Before the SRU it will return 3:00:00, after the SRU it will return
  4:00:00.

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

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

[Touch-packages] [Bug 1911133] [NEW] [Regression] RS482M [Mobility Radeon Xpress 200]

[Daniel]

Public bug reported:

RS482M [Mobility Radeon Xpress 200] crash gnome desktop at startup with Oh no! 
Something has gone wrong after latest updates
It works fine before them
System: Hp Nx6325
Video: Advanced Micro Deviceº Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 
200] (prog-if 00 [VGA controller])

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


** Tags: regression-proposed

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

Title:
  [Regression] RS482M [Mobility Radeon Xpress 200]

Status in mesa package in Ubuntu:
  New

Bug description:
  RS482M [Mobility Radeon Xpress 200] crash gnome desktop at startup with Oh 
no! Something has gone wrong after latest updates
  It works fine before them
  System: Hp Nx6325
  Video: Advanced Micro Deviceº Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 
200] (prog-if 00 [VGA controller])

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

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

[Touch-packages] [Bug 1911073] Re: libc6 package version 2.31-0ubuntu9.1 in ubuntu 20.04.1 - no traces of where it came from

[Julian Andres Klode]

Chances are you removed the focal-updates repository. In any case it's
not a bug, if a package is gone from a repo (or superseded) or the repo
gone from your sources.list that's the normal output.

I suggest you use one of the user support options like askubuntu, user
mailing lists, or #ubuntu irc channel if you need further assistance.

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

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

Title:
  libc6 package version 2.31-0ubuntu9.1 in ubuntu 20.04.1 - no traces of
  where it came from

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I installed `Ubuntu 20.04.1 LTS` few weeks ago. So it's almost fresh
  install.

  I can't install libc6-dev:

  The following packages have unmet dependencies:
libc6-dev : Depends: libc6 (= 2.31-0ubuntu9) but 2.31-0ubuntu9.1 is to 
be installed

  Here's what version the `-dev` package is:

  $ apt show libc6-dev
  Version: 2.31-0ubuntu9
  Depends: libc6 (= 2.31-0ubuntu9), libc-dev-bin (= 2.31-0ubuntu9), 
linux-libc-dev, libcrypt-dev

  `Depends: libc6 (= 2.31-0ubuntu9)` looks good to me.

  apt-cache shows libc version is ok:

  $ apt-cache show libc6
  Version: 2.31-0ubuntu9

  
  However, `apt` differs:

  $ apt show libc6
  Version: 2.31-0ubuntu9.1

  apt can not tell where this version comes from `focal/main`:

  $ apt policy libc6
  libc6:
Installed: 2.31-0ubuntu9.1
Candidate: 2.31-0ubuntu9.1
Version table:
   *** 2.31-0ubuntu9.1 100
  100 /var/lib/dpkg/status
   2.31-0ubuntu9 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  9.1 can only be found in `/var/lib/dpkg/status` however, neither in
  packages here: `http://us.archive.ubuntu.com/ubuntu/dists/focal/main
  /binary-amd64/` nor in `/var/lib/apt/lists/us.archive.ubuntu
  .com_ubuntu_dists_focal_main_binary-amd64_Packages` version
  `2.31-0ubuntu9.1` does not exist.

  Upgrade can be seen in the logs:

  2021-01-02 21:02:03 startup archives unpack
  2021-01-02 21:02:03 upgrade libc6:amd64 2.31-0ubuntu9 2.31-0ubuntu9.1
  2021-01-02 21:02:03 status half-configured libc6:amd64 2.31-0ubuntu9
  2021-01-02 21:02:03 status unpacked libc6:amd64 2.31-0ubuntu9
  2021-01-02 21:02:03 status half-installed libc6:amd64 2.31-0ubuntu9
  2021-01-02 21:02:03 status unpacked libc6:amd64 2.31-0ubuntu9.1
  2021-01-02 21:02:04 startup packages configure
  2021-01-02 21:02:04 configure libc6:amd64 2.31-0ubuntu9.1 
  2021-01-02 21:02:04 status unpacked libc6:amd64 2.31-0ubuntu9.1
  2021-01-02 21:02:04 status half-configured libc6:amd64 2.31-0ubuntu9.1
  2021-01-02 21:02:04 status installed libc6:amd64 2.31-0ubuntu9.1

  Is there a legitimate ubuntu repository with this package? How can I
  find the repository name where this package really came from?

  What worries me is md5s hash of this package is
  `1ec728d58f7fc0d302119e9bb53050f8` which can only be found on
  ropshell.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2ubuntu0.2
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 18:44:00 2021
  InstallationDate: Installed on 2021-01-03 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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