[Touch-packages] [Bug 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS

2021-06-12 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Mobile phone hotspot unusable due to systemd-resolved not liking the
  DNS

Status in systemd package in Ubuntu:
  Expired
Status in systemd source package in Focal:
  Expired
Status in systemd source package in Groovy:
  Expired

Bug description:
  Seen in 20.04.

  Trying to connect to the internet using the mobile phone hotspot is
  impossible due to systemd-resolved not resolving and reporting things
  like:

  resolve call failed: DNSSEC validation failed: incompatible-server

  and

  systemd-resolved[81699]: DNSSEC validation failed for question 
d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN 
PTR: no-signature
  DNSSEC validation failed for question 
b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: 
no-signature

  etc etc.

  Name resolution works just fine from the mobile phone.

  Funny thing is that the issue persists if DNSSEC is disabled via
  resolvectl for the interface:

  Link 3 (wlan0)
Current Scopes: DNS  
  DefaultRoute setting: yes  
 LLMNR setting: yes  
  MulticastDNS setting: no   
DNSOverTLS setting: opportunistic
DNSSEC setting: no   
  DNSSEC supported: no   
Current DNS Server: 192.168.43.1 
   DNS Servers: 192.168.43.1

  Systemd-resolved won't accept the issue to be reported upstream saying
  that a too old version of systemd is being used.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.5
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Mar 22 15:39:23 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (400 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/VG_NVMe-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: Upgraded to focal on 2020-05-23 (303 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER
  modified.conffile..etc.systemd.resolved.conf: [modified]
  mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139
  mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733

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

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


[Touch-packages] [Bug 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS

2021-06-12 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu Focal) because there has been no activity
for 60 days.]

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

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

Title:
  Mobile phone hotspot unusable due to systemd-resolved not liking the
  DNS

Status in systemd package in Ubuntu:
  Expired
Status in systemd source package in Focal:
  Expired
Status in systemd source package in Groovy:
  Expired

Bug description:
  Seen in 20.04.

  Trying to connect to the internet using the mobile phone hotspot is
  impossible due to systemd-resolved not resolving and reporting things
  like:

  resolve call failed: DNSSEC validation failed: incompatible-server

  and

  systemd-resolved[81699]: DNSSEC validation failed for question 
d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN 
PTR: no-signature
  DNSSEC validation failed for question 
b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: 
no-signature

  etc etc.

  Name resolution works just fine from the mobile phone.

  Funny thing is that the issue persists if DNSSEC is disabled via
  resolvectl for the interface:

  Link 3 (wlan0)
Current Scopes: DNS  
  DefaultRoute setting: yes  
 LLMNR setting: yes  
  MulticastDNS setting: no   
DNSOverTLS setting: opportunistic
DNSSEC setting: no   
  DNSSEC supported: no   
Current DNS Server: 192.168.43.1 
   DNS Servers: 192.168.43.1

  Systemd-resolved won't accept the issue to be reported upstream saying
  that a too old version of systemd is being used.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.5
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Mar 22 15:39:23 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (400 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/VG_NVMe-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: Upgraded to focal on 2020-05-23 (303 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER
  modified.conffile..etc.systemd.resolved.conf: [modified]
  mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139
  mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733

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

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


[Touch-packages] [Bug 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS

2021-06-12 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu Groovy) because there has been no activity
for 60 days.]

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

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

Title:
  Mobile phone hotspot unusable due to systemd-resolved not liking the
  DNS

Status in systemd package in Ubuntu:
  Expired
Status in systemd source package in Focal:
  Expired
Status in systemd source package in Groovy:
  Expired

Bug description:
  Seen in 20.04.

  Trying to connect to the internet using the mobile phone hotspot is
  impossible due to systemd-resolved not resolving and reporting things
  like:

  resolve call failed: DNSSEC validation failed: incompatible-server

  and

  systemd-resolved[81699]: DNSSEC validation failed for question 
d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN 
PTR: no-signature
  DNSSEC validation failed for question 
b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: 
no-signature

  etc etc.

  Name resolution works just fine from the mobile phone.

  Funny thing is that the issue persists if DNSSEC is disabled via
  resolvectl for the interface:

  Link 3 (wlan0)
Current Scopes: DNS  
  DefaultRoute setting: yes  
 LLMNR setting: yes  
  MulticastDNS setting: no   
DNSOverTLS setting: opportunistic
DNSSEC setting: no   
  DNSSEC supported: no   
Current DNS Server: 192.168.43.1 
   DNS Servers: 192.168.43.1

  Systemd-resolved won't accept the issue to be reported upstream saying
  that a too old version of systemd is being used.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.5
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Mar 22 15:39:23 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (400 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/VG_NVMe-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: Upgraded to focal on 2020-05-23 (303 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER
  modified.conffile..etc.systemd.resolved.conf: [modified]
  mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139
  mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733

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

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


[Touch-packages] [Bug 1923686] Re: Ubuntu 20.10 Network Issue

2021-06-12 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu 20.10 Network Issue

Status in systemd package in Ubuntu:
  Expired

Bug description:
  I have a server running Ubuntu 20.10 running VMware Workstation 16
  which loses its default route. I keep setting it manually but every 30
  minutes or so, it reverts to the incorrect route.

  This server has 5 (4 used) GigE ports on different VLANs. Each of the
  4 ports is connected to a Cisco switch which applies the proper tag
  for that VLAN so that traffic can be routed correctly.

  I have tried disabling netplan and setting up interfaces in
  /etc/network/interfaces with the proper default route. But vmnetbrdige
  resets them every 30 minutes or so, adding routes for each interface
  which results in the incorrect default route.

  I have read of similar problems in Ubuntu 16.04 and 20.04 with a fix
  which claims to have corrected related problems, but not my issue.

  I had this server on CentOS 6 before and everything was work as
  expected.

  Below are the details.
  Contents of /etc/network/interfaces:
  iface eth1 inet static
  address 10.0.1.6
  netmask 255.255.255.0
  gateway 10.0.1.1
  dns-nameservers 8.8.8.8, 75.75.76.76
  dns-search mydomain.local
  up route add -net 0.0.0.0 netmask 0.0.0.0 gw 10.0.1.1 dev eth0

  iface eth2 inet static
  address 10.0.20.60
  netmask 255.255.255.0
  gateway 10.0.20.1

  iface eth3 inet static
  address 10.0.4.60
  netmask 255.255.255.0
  gateway 10.0.4.1

  iface eth4 inet static
  address 192.168.3.60
  netmask 255.255.255.0
  gateway 192.168.3.1

  Output of ifconfig -a:
  eth1: flags=4163  mtu 1500
  inet 10.0.1.60  netmask 255.255.255.0  broadcast 10.0.1.255
  inet6 fe80::264b:feff:fe5a:3622  prefixlen 64  scopeid 0x20
  ether 24:4b:fe:5a:36:22  txqueuelen 1000  (Ethernet)
  RX packets 17216  bytes 14604772 (14.6 MB)
  RX errors 0  dropped 1283  overruns 0  frame 0
  TX packets 14670  bytes 1719546 (1.7 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device memory 0xfc60-fc61

  eth2: flags=4163  mtu 1500
  inet 10.0.20.60  netmask 255.255.255.0  broadcast 10.0.20.255
  inet6 fe80::226:55ff:fed7:d054  prefixlen 64  scopeid 0x20
  ether 00:26:55:d7:d0:54  txqueuelen 1000  (Ethernet)
  RX packets 3159  bytes 212180 (212.1 KB)
  RX errors 0  dropped 1426  overruns 0  frame 0
  TX packets 1691  bytes 122628 (122.6 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 106  memory 0xfca0-fca2

  eth3: flags=4163  mtu 1500
  inet 10.0.4.60  netmask 255.255.255.0  broadcast 10.0.4.255
  inet6 fe80::226:55ff:fed7:d057  prefixlen 64  scopeid 0x20
  ether 00:26:55:d7:d0:57  txqueuelen 1000  (Ethernet)
  RX packets 3835  bytes 249203 (249.2 KB)
  RX errors 0  dropped 1408  overruns 0  frame 0
  TX packets 370  bytes 31235 (31.2 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 115  memory 0xfc82-fc84

  eth4: flags=4163  mtu 1500
  inet 192.168.3.60  netmask 255.255.255.0  broadcast 192.168.3.255
  inet6 fe80::226:55ff:fed7:d056  prefixlen 64  scopeid 0x20
  ether 00:26:55:d7:d0:56  txqueuelen 1000  (Ethernet)
  RX packets 2973  bytes 211765 (211.7 KB)
  RX errors 0  dropped 1433  overruns 0  frame 0
  TX packets 238  bytes 29345 (29.3 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 117  memory 0xfc80-fc82

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 119  bytes 17075 (17.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 119  bytes 17075 (17.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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

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


[Touch-packages] [Bug 1895490] Re: no destination host name is cups-browsed running

2021-06-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  no destination host name is cups-browsed running

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  cups-browsed:
Installed: 1.27.4-1
  cups:
Installed: 2.3.1-9ubuntu1.1

  I expect to be able to print on my Brother HL-L2350DW printer. I have
  no problem printing to that printer via Windows 10. I also got this
  error on Kubuntu 20.04.

  
  What happened instead? I cannot get my pdf to print. Instead I get an error 
that says 'No destination host name supplied by cups-browsed for printer 
"Brother_HL_L2350DW_series", is cups-browsed running?'.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Sep 13 20:30:40 2020
  InstallationDate: Installed on 2020-08-16 (28 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for Brother_HL_L2350DW_series: 
implicitclass://Brother_HL_L2350DW_series/
  MachineType: LENOVO 20AN00DEUS
  Papersize: letter
  PpdFiles: Brother_HL_L2350DW_series: Brother HL-L2350DW series, driverless, 
cups-filters 1.27.4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=d3493ccb-75ba-4bb9-851d-b3fc4c5adb8f ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET96WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00DEUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET96WW(2.50):bd06/20/2018:svnLENOVO:pn20AN00DEUS:pvrThinkPadT440p:rvnLENOVO:rn20AN00DEUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00DEUS
  dmi.product.sku: LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1931732] Re: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: o subprocesso instalado, do pacote initramfs-tools, o script post-installation retornou erro do sta

2021-06-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: o
  subprocesso instalado, do pacote initramfs-tools, o script post-
  installation retornou erro do status de saída 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  não instalou

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.5
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun  9 03:03:16 2021
  ErrorMessage: o subprocesso instalado, do pacote initramfs-tools, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2021-06-09 (2 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: o 
subprocesso instalado, do pacote initramfs-tools, o script post-installation 
retornou erro do status de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1931725] Re: initramfs-tools: use zstd as the default compression method

2021-06-12 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.140ubuntu5

---
initramfs-tools (0.140ubuntu5) impish; urgency=medium

  * Switch default initramfs compression to zstd, as it produces the lower
overall boot time. LP: #1931725

 -- Dimitri John Ledkov   Fri, 11 Jun 2021 16:55:30
+0100

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

Title:
  initramfs-tools: use zstd as the default compression method

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  New

Bug description:
  Turns out that loading is always the slow part in loading initramfs
  into memory and decompressing it since decompression is always the
  final 10-20% or so of the task.  It therefore makes sense to use a
  good compressor that shrinks the initramfs as much as possible with
  little decompression overhead.

  Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in
  decompression, the image size is much smaller with zstd than lz4, and
  since ~80-90% of the boot time is loading the image it makes sense to
  use zstd.

  Attached is a libreoffice spread sheet showing typical load and
  decompression times for a fairly standard 3.4 GHZ intel box with data
  for load times for a 5400 RPM, 7200 RPM and SATA SSD drives.

  The conclusions from the test results (attached) show:

  1. Loading time is always significantly slower than decompression time.
  2. ZSTD is 5x slower than LZ4 in decompression speed but produces far
  better compressed images
  3. Given that loading time is the major factor in loading +
  decompression, ZSTD is best for kernel and initramfs boot timings.

  (Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3
  /kernel-compression-method.txt for some raw data on drive load speeds
  for the same UEFI box I did a couple of years ago).

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

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


[Touch-packages] [Bug 1931756] [NEW] [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem

2021-06-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but
all were no sound.

The modprobe,d modifications did result in the "dummy" message being
replaced by a device. This was done 2 installs ago,sorry.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.10.0-051000-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pbea   1894 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Fri Jun 11 23:34:27 2021
InstallationDate: Installed on 2021-06-11 (0 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2021
dmi.bios.release: 1.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.2
dmi.board.name: 0P25F6
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal
-- 
[XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
https://bugs.launchpad.net/bugs/1931756
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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 1920836] Re: Show Extended Security Maintenence status

2021-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.99.13

---
software-properties (0.99.13) impish; urgency=medium

  * Catch exception if UA status file is not written

 -- Robert Ancell   Fri, 11 Jun 2021
17:16:09 +1200

** Changed in: software-properties (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Show Extended Security Maintenence status

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  New

Bug description:
  [Impact]
  There is not currently a graphical method of determining if a system is 
subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) 
updates. This is resolved by adding some [new 
UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to 
the software properties application.

  [Test Case]
  1. Install latest version of Ubuntu advantage:
  $ sudo add-apt-repository ppa:ua-client/stable
  $ sudo apt update
  $ sudo apt upgrade
  2. Open Software Properties
  3. Go to Updates tab.

  Expected result:
  Information is shown that indicates if this system is using Extended Security 
Maintenance updates, when updates will supported until, and a link to upgrade 
to ESM.

  Observed result:
  No ESM information currently shown.

  [Where problems could occur]
  - Software properties could hit a bug getting a response from the ua app. The 
current code carefully checks if and what is returned, falling back to a safe 
default behavior.
  - Launching software properties could trigger a bug in the ua app.
  - Software properties could show incorrect information, causing confusion for 
the user. The solution uses information from distro-info and the ua app which 
means software-properties contains no data about ESM, and instead relies on 
these apps that can be updated if things change.

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

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


[Touch-packages] [Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51

2021-06-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51

Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Groovy:
  Confirmed

Bug description:
  We seem to get failed dep8 testing on lxc in Groovy for a while. What
  we are interested in is knowing whether this is known problems in the
  testing or something that waits on kernel fixes (who would be driving
  those if this is the case).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20210224_161232_5c8ac@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/lxc/20210224_202135_e7aed@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/l/lxc/20210224_172418_73aab@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/lxc/20210224_164056_06e00@/log.gz

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

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


[Touch-packages] [Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51

2021-06-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51

Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Groovy:
  Confirmed

Bug description:
  We seem to get failed dep8 testing on lxc in Groovy for a while. What
  we are interested in is knowing whether this is known problems in the
  testing or something that waits on kernel fixes (who would be driving
  those if this is the case).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20210224_161232_5c8ac@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/lxc/20210224_202135_e7aed@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/l/lxc/20210224_172418_73aab@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/lxc/20210224_164056_06e00@/log.gz

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

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


[Touch-packages] [Bug 1931612] [NEW] Print dialog box shows same printer twice

2021-06-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have set up a single HP printer which is attached to my network.  The
setup process went smoothly, and when I open the Printers system setup
panel, I see only my printer there.

However, when I print from an application, and that application uses the
system print dialog box, my printer appears twice.  One entry, matching
the name correctly, works fine.  The other, which a slightly changed
name, does not work at all.  See attached screenshot.

Applications that have their own print dialog box do not have this
problem.  For example, Firefox shows only my printer once.  Same thing
with Libre Office.

Description:Ubuntu 20.04.2 LTS
Release:20.04

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


** Tags: bot-comment
-- 
Print dialog box shows same printer twice
https://bugs.launchpad.net/bugs/1931612
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups 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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

2021-06-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in gdm3 package in Ubuntu:
  Incomplete
Status in glibc package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
  before now slipping into a bad mode.

  Now it seems all tests failed in boot-and-services by hanging until killed by
  VirtSubproc.Timeout of autokgtest.

  The last [1] test log has a bit more, it shows a python stack overflow
  ```
 VirtSubproc.Timeout
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f108e840740 (most recent call first):
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
  ```

  I have seen a bunch of packages including even gdm3 and glibc being blocked by
  that so I wanted to at least track down the issue until we can put it on
  someones task list to resolve.
  No one replied to my pings yet, but maybe that means someone is already
  debugging this and had enabled some debugging?

  By running the same in armhf container on arm64 VM on canonistack I've seen
  no issues. The test worked fine and had no hang/issues.

  root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
  lxc
  1
  test_profile (__main__.AppArmorTest)
  AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
  test_help (__main__.CLITest)
  --help works and succeeds ... ok
  test_invalid_option (__main__.CLITest)
  Calling with invalid option fails ... ok
  test_version (__main__.CLITest)
  --version works and succeeds ... ok
  test_cpushares (__main__.CgroupsTest)
  service with CPUShares ... ok
  test_simple (__main__.CgroupsTest)
  simple service ... ok
  test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does 
not work in containers'
  test_log_for_service (__main__.JournalTest) ... ok
  test_no_options (__main__.JournalTest) ... ok
  test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_failing (__main__.SeccompTest) ... ok
  test_0_init (__main__.ServicesTest)
  Verify that init is systemd ... ok
  test_cron (__main__.ServicesTest) ... ok
  test_dbus (__main__.ServicesTest) ... ok
  test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found'
  test_logind (__main__.ServicesTest) ... ok
  test_network_manager (__main__.ServicesTest) ... ok
  test_no_failed (__main__.ServicesTest)
  No failed units ... ok
  test_rsyslog (__main__.ServicesTest) ... ok
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'
  --
  Ran 23 tests in 5.589s
  OK (skipped=6)

  So I can not reproduce this on canonistack, but it blocks autopkgtests of
  various packages pretty reproducibly :-/

  [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz

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

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


[Touch-packages] [Bug 1931488] [NEW] Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade

2021-06-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I just upgraded from Kubuntu 20.10 to 21.04 and now I no longer get any
file search results ("Desktop search") in Krunner or Kickoff
("Application Launcher"). For example type "testfile" in Krunner gives
zero results although there this file in the home directory.

However baloosearch in the terminal works fine. Desktop search / file
search is also enabled in the settings for Krunner and in system
settings.

If I create a new user account the file search does work. I assume that
some setting in the home directory must have been changed during the
upgrade.

Please let me know which logs or files I could upload that could be of
use to debug this problem.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Jun  9 20:10:40 2021
DistUpgraded: 2021-06-06 22:12:52,319 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed
 virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Fujitsu Technology Solutions HD Graphics 630 [1734:121c]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
 Bus 001 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU ESPRIMO Q556/2
ProcEnviron:
 LANGUAGE=de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=8f3a8bfd-584a-4e11-a2f8-984c6e293255 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to hirsute on 2021-06-06 (2 days ago)
dmi.bios.date: 02/12/2020
dmi.bios.release: 1.26
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V5.0.0.12 R1.26.0 for D3403-U1x
dmi.board.name: D3403-U1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3403-U1
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.26.0forD3403-U1x:bd02/12/2020:br1.26:svnFUJITSU:pnESPRIMOQ556/2:pvr:rvnFUJITSU:rnD3403-U1:rvrS26361-D3403-U1:cvnFUJITSU:ct3:cvr:
dmi.product.family: ESPRIMO-FTS
dmi.product.name: ESPRIMO Q556/2
dmi.sys.vendor: FUJITSU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute kubuntu third-party-packages ubuntu
-- 
Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade
https://bugs.launchpad.net/bugs/1931488
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1931318] [NEW] Screen brightness of HP laptop is not saved after restart

2021-06-08 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When the computer is turned on, screen brightness is always 100% instead
of the last set brightness. The computer is HP Envy 15 laptop. The
Ubuntu version is 20.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.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  460.80  Fri May  7 06:55:54 
UTC 2021
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun  9 08:13:44 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company Device [103c:878e]
 NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f12] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:878e]
InstallationDate: Installed on 2021-06-05 (3 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: HP HP ENVY Laptop 15-ep0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/29/2020
dmi.bios.release: 15.5
dmi.bios.vendor: AMI
dmi.bios.version: F.05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 878E
dmi.board.vendor: HP
dmi.board.version: 18.32
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 18.32
dmi.modalias: 
dmi:bvnAMI:bvrF.05:bd12/29/2020:br15.5:efr18.32:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.32:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP ENVY
dmi.product.name: HP ENVY Laptop 15-ep0xxx
dmi.product.sku: 16P91PA#AR6
dmi.sys.vendor: HP
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
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 ubuntu
-- 
Screen brightness of HP laptop is not saved after restart
https://bugs.launchpad.net/bugs/1931318
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1930917] Re: Latest isc-dhcp-server rejects proper dhcpd.conf

2021-06-07 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-dhcp - 4.4.1-2.2ubuntu6.2

---
isc-dhcp (4.4.1-2.2ubuntu6.2) hirsute-security; urgency=medium

  * Fix regression caused by rebuild with newer toolchain (LP: #1930917)
- debian/rules: build with -fno-strict-aliasing.

 -- Marc Deslauriers   Mon, 07 Jun 2021
08:08:56 -0400

** Changed in: isc-dhcp (Ubuntu Hirsute)
   Status: Confirmed => Fix Released

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

Title:
  Latest isc-dhcp-server rejects proper dhcpd.conf

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in isc-dhcp source package in Hirsute:
  Fix Released
Status in isc-dhcp source package in Impish:
  Confirmed

Bug description:
  Ubuntu 21.04 on Raspberry Pi. isc-dhcp-server was working just fine
  with version V4.4.1-2.2-ubuntu6.

  I got updated to V4.4.1-2.2ubuntu6.1 and now isc-dhcp-server refuses
  to start with the error "Can't clone pool group".

  I backed off to the prior version and it's working as before, so
  something in the V4.4.1-2.2ubuntu6.1 update has broken config file
  parsing.

  Here's the subnet section of the failing config. Removing the "pool"
  declaration from the subnet declaration eliminates the error, but of
  course, that's not a working configuration.

  subnet 192.168.92.0 netmask 255.255.255.0 {
  option domain-search "foo.com", "dyn.foo.com";
  option broadcast-address 192.168.92.255;
  allow duplicates;
  ddns-updates off;
  pool {
  ddns-updates on;
  allow unknown-clients;
  option domain-name "dyn.foo.com";
  ddns-rev-domainname "dhcp";
  default-lease-time 86400;
  max-lease-time 86400;
  range 192.168.92.101 192.168.92.127;
  }
  }

  This was also noted at least twice in the Ubuntu forums:
  https://ubuntuforums.org/showthread.php?t=2462984 and
  https://ubuntuforums.org/showthread.php?t=2462930

  Thanks

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

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


[Touch-packages] [Bug 1914278] Re: discover is not removing unused kernels

2021-06-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  discover is not removing unused kernels

Status in apt package in Ubuntu:
  Invalid
Status in discover package in Ubuntu:
  Confirmed
Status in packagekit package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  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/1914278/+subscriptions

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


[Touch-packages] [Bug 1914278] Re: discover is not removing unused kernels

2021-06-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  discover is not removing unused kernels

Status in apt package in Ubuntu:
  Invalid
Status in discover package in Ubuntu:
  Confirmed
Status in packagekit package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  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/1914278/+subscriptions

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


[Touch-packages] [Bug 1931024] Re: BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550]

2021-06-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550]

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I've been working with a user for the last 2 days on a failure to even
  start the kernel when installing 20.04 or 21.04 (possibly other
  releases) with a UEFI boot.

  System is Dell XPS 9550 amd64 with Ubuntu Budgie.

  The symptom is that after GRUB successfully loads the kernel into RAM,
  it fails to return from loading the initrd into RAM. This was proved
  by adding guard 'echo' and 'sleep' around each stage n grub.cfg.

  After much investigation since this seemed initially related to a LUKS
  install I noticed the initrd.img files generated with MODULES=most are
  105MB. Most of that is unneeded firmware and other files so I changed
  to MODULES=dep. Resulting initrd.img's are around 55MB.

  System then boots correctly.

  This looks like a possible issue with the UEFI on these XPS models but
  as initrd.img sizes get ridiculously large this is likely to hit more
  systems and users.

  For several years I carry optimisation patches to initramfs-tools that
  don't add most firmwares except those specifically required (certainly
  not adding AMD GPU firmware when system has only Intel or Nvidia GPUs
  - and visa versa)

  My initrd.img's are a hybrid of MODULES=dep and result in less than
  20MB.

  My recommendation is to add optimisations to initramfs-tools or adopt
  MODULES=dep.

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

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


[Touch-packages] [Bug 1931018] [NEW] Keyboard layout switch freezes

2021-06-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi! I have problem with slow keyboard layout switching between Russian
and English layouts. In ubuntu 16.04-20.04 :)

gsettings get org.gnome.desktop.wm.keybindings switch-input-source
['XF86Keyboard']
But in gnome-tweak-tool I set as key for layout switching caps-lock. It is 
work, but when I switch from en to ru, fast, and when ru to en, I have delay 
~1s.

And in gnome-tweak-tool I see caps-lock as keyboard key for switching,
and in gsettings is XF86Keyboard or some time ago super+space. When I
try to set in gsettings some other keys (as super+space), they worked
fast, but in gnome-tweak-tool caps-lock work slooow. And all this keys
work in one time, this is strange.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.12.0-8.5-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.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  460.80  Fri May  7 06:55:54 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Sun Jun  6 15:58:43 2021
DistUpgraded: 2020-12-05 22:39:51,673 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить 
процесс-потомок «./xorg_fix_proprietary.py» (Нет такого файла или каталога) (8))
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.80, 5.11.0-18.1-liquorix-amd64, x86_64: installed
 nvidia, 460.80, 5.12.0-8.5-liquorix-amd64, x86_64: installed
 nvidia, 460.80, 5.12.0-9.2-liquorix-amd64, x86_64: installed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer 3rd Gen Core processor Graphics Controller 
[1558:2701]
 NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 
[VGA controller])
InstallationDate: Installed on 2018-06-28 (1073 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: CLEVO CO. W250ENQ / W270ENQ
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: audit=0 intel_pstate=disable  
BOOT_IMAGE=/boot/vmlinuz-5.12.0-8.5-liquorix-amd64 
root=UUID=3f1a1990-8bad-49d1-970e-87308d8cd521 ro quiet splash nouveau.runpm=0 
zswap.enabled=0 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-12-05 (182 days ago)
dmi.bios.date: 04/03/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W250ENQ / W270ENQ
dmi.board.vendor: CLEVO CO.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/03/2012:br4.6:svnCLEVOCO.:pnW250ENQ/W270ENQ:pvrNotApplicable:rvnCLEVOCO.:rnW250ENQ/W270ENQ:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W250ENQ / W270ENQ
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.
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-06-08T10:33:29.519300
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
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 false-gpu-hang focal freeze third-party-packages 
ubuntu
-- 
Keyboard layout switch 

[Touch-packages] [Bug 1922621] Re: PulseAudio Assertion 'section' in pa_alsa_element_get() when laptop in docking station

2021-06-05 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  PulseAudio Assertion 'section' in pa_alsa_element_get() when laptop in
  docking station

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  https://errors.ubuntu.com/problem/5bc83665288ea40e5ad4564ebe20d1ab81d04fd3

  ---

  PulseAudio 1:13.99.1-1ubuntu3.10, Ubuntu 20.04.2
  Laptop: Lenovo ThinkPad X1 Carbon 7th

  Soundcards:
   0 [sofhdadsp  ]: sof-hda-dsp - sof-hda-dsp
    LENOVO-20QES01L00-ThinkPadX1Carbon7th
   1 [Audio  ]: USB-Audio - ThinkPad Dock USB Audio
    Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-5.4.4, high speed

  When the laptop is not docked, everything works fine. Sound is played
  using the laptop internal speakers. When the laptop is in the docking
  station, the sound in KDE is not working (no sound devices are shown).
  Pulseaudio is crashing with an Assertion.

  D: [pulseaudio] alsa-mixer.c: Profile output:analog-stereo supported.
  D: [pulseaudio] conf-parser.c: Parsing configuration file 
'/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf'
  D: [pulseaudio] conf-parser.c: Parsing configuration file 
'/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common'
  E: [pulseaudio] alsa-mixer.c: Assertion 'section' failed at 
modules/alsa/alsa-mixer.c:1954, function pa_alsa_element_get(). Aborting.

  Prime suspect for the change is an "Embedded Controller Update" by
  fwupdmgr, which was installed a while ago, and applied during last
  reboot. This cannot be downgraded (Lenovo does not support that).

  More details from "pulseaudio -", docked:

  I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; 
argument: "").
  D: [pulseaudio] database-tdb.c: Opened TDB database 
'/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database.tdb'
  I: [pulseaudio] module-card-restore.c: Successfully opened database file 
'/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database'.
  I: [pulseaudio] module.c: Loaded "module-card-restore" (index: #2; argument: 
"").
  I: [pulseaudio] module.c: Loaded "module-augment-properties" (index: #3; 
argument: "").
  I: [pulseaudio] module.c: Loaded "module-switch-on-port-available" (index: 
#4; argument: "").
  D: [pulseaudio] module.c: Checking for existence of 
'/usr/lib/pulse-13.99.1/modules/module-switch-on-connect.so': success
  I: [pulseaudio] module.c: Loaded "module-switch-on-connect" (index: #5; 
argument: "").
  D: [pulseaudio] module.c: Checking for existence of 
'/usr/lib/pulse-13.99.1/modules/module-udev-detect.so': success
  D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC1 is accessible: yes
  D: [pulseaudio] module-udev-detect.c: 
/devices/pci:00/:00:14.0/usb1/1-5/1-5.4/1-5.4.4/1-5.4.4:1.0/sound/card1 
is busy: no
  D: [pulseaudio] module-udev-detect.c: Loading module-alsa-card with arguments 
'device_id="1" name="usb-Generic_ThinkPad_Dock_USB_Audio-00" 
card_name="alsa_card.usb-Generic_ThinkPad_Dock_USB_Audio-00" namereg_fail=false 
tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
avoid_resampling=no card_properties="module-udev-detect.discovered=1"'
  D: [pulseaudio] dbus-util.c: Successfully connected to D-Bus session bus 
0dd0d23e5ac302eec692d2b2606b9c78 as :1.81
  D: [pulseaudio] reserve-wrap.c: Successfully acquired reservation lock on 
device 'Audio1'
  I: [pulseaudio] (alsa-lib)main.c: error: failed to import hw:1 use case 
configuration -2
  I: [pulseaudio] (alsa-lib)main.c: error: failed to import ThinkPad Dock USB 
Audio use case configuration -2
  I: [pulseaudio] alsa-ucm.c: UCM not available for card ThinkPad Dock USB Audio
  D: [pulseaudio] conf-parser.c: Parsing configuration file 
'/usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf'
  D: [pulseaudio] alsa-mixer.c: Looking at profile input:analog-stereo
  D: [pulseaudio] alsa-mixer.c: Checking for recording on Analog Stereo 
(analog-stereo)
  D: [pulseaudio] alsa-util.c: Trying front:1 with SND_PCM_NO_AUTO_FORMAT ...

  Not docked:

  I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; 
argument: "").
  D: [pulseaudio] database-tdb.c: Opened TDB database 
'/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database.tdb'
  I: [pulseaudio] module-card-restore.c: Successfully opened database file 
'/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database'.
  I: [pulseaudio] module.c: Loaded "module-card-restore" (index: #2; argument: 
"").
  I: [pulseaudio] module.c: Loaded "module-augment-properties" (index: #3; 
argument: "").
  I: [pulseaudio] module.c: Loaded "module-switch-on-port-available" (index: 
#4; argument: "").
  D: 

[Touch-packages] [Bug 1930917] Re: Latest isc-dhcp-server rejects proper dhcpd.conf

2021-06-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  Latest isc-dhcp-server rejects proper dhcpd.conf

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.04 on Raspberry Pi. isc-dhcp-server was working just fine
  with version V4.4.1-2.2-ubuntu6.

  I got updated to V4.4.1-2.2ubuntu6.1 and now isc-dhcp-server refuses
  to start with the error "Can't clone pool group".

  I backed off to the prior version and it's working as before, so
  something in the V4.4.1-2.2ubuntu6.1 update has broken config file
  parsing.

  Here's the subnet section of the failing config. Removing the "pool"
  declaration from the subnet declaration eliminates the error, but of
  course, that's not a working configuration.

  subnet 192.168.92.0 netmask 255.255.255.0 {
  option domain-search "foo.com", "dyn.foo.com";
  option broadcast-address 192.168.92.255;
  allow duplicates;
  ddns-updates off;
  pool {
  ddns-updates on;
  allow unknown-clients;
  option domain-name "dyn.foo.com";
  ddns-rev-domainname "dhcp";
  default-lease-time 86400;
  max-lease-time 86400;
  range 192.168.92.101 192.168.92.127;
  }
  }

  This was also noted at least twice in the Ubuntu forums:
  https://ubuntuforums.org/showthread.php?t=2462984 and
  https://ubuntuforums.org/showthread.php?t=2462930

  Thanks

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

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


[Touch-packages] [Bug 1915945] Re: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed sudo package post-installation script subprocess returned error exit status 1

2021-06-04 Thread Launchpad Bug Tracker
[Expired for sudo (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed
  sudo package post-installation script subprocess returned error exit
  status 1

Status in sudo package in Ubuntu:
  Expired

Bug description:
  I've put the system to upgrade and this error occured!!

  I tried many ways to correct it but all attempts were unsuccesfull.

  Best regards,

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sudo 1.8.31-1ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   software-properties-common:amd64: Install
   software-properties-gtk:amd64: Install
   python3-software-properties:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 17 13:43:57 2021
  DuplicateSignature:
   package:sudo:1.8.31-1ubuntu1.2
   Setting up sudo (1.8.31-1ubuntu1.2) ...
   chown: alterando o dono de '/etc/sudoers': Operação não permitida
   dpkg: error processing package sudo (--configure):
installed sudo package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed sudo package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-12-12 (797 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: sudo
  Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed 
sudo package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-09-30 (139 days ago)
  VisudoCheck:
   /etc/sudoers: análise OK
   /etc/sudoers.d/README: análise OK
  mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421

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

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


[Touch-packages] [Bug 1921423] Re: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1

2021-06-04 Thread Launchpad Bug Tracker
[Expired for sudo (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o
  subprocesso instalado, do pacote sudo, o script post-installation
  retornou erro do status de saída 1

Status in sudo package in Ubuntu:
  Expired

Bug description:
  The privileges of my /etc/sudoers file is 220. I don't have any idea
  on how it was changed, and I tried many different ways to chmod it and
  I didn't get to do it, even booting from another media and trying to
  chmod the file didn't work.

  It's the main reason of the many errors that started happening when
  updating this machine.

  I can't stop this machine now, and I don't want to run the risk of
  trying to use the installation software to try to repair it.

  If you have any idea on how to chmod the file, I'll be grateful.

  Best regards,

  Alex Leandro Rosa

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sudo 1.8.31-1ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Mar 25 15:00:47 2021
  ErrorMessage: o subprocesso instalado, do pacote sudo, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2018-12-12 (833 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: sudo
  Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o 
subprocesso instalado, do pacote sudo, o script post-installation retornou erro 
do status de saída 1
  UpgradeStatus: Upgraded to focal on 2020-09-30 (175 days ago)
  VisudoCheck:
   /etc/sudoers: análise OK
   /etc/sudoers.d/README: análise OK
  mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421

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

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


[Touch-packages] [Bug 1930925] [NEW] Ubuntu 20.04 doesn't work with moidern KVMs

2021-06-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have recently acquired a acquired a desktop running ubuntu 20.04. I
have several computers and switch between them using this KVM
https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1
The other machines are either running windows or ubuntu 18.04 or
earlier. They are all fine, but the with 20.04 machine neither the
keyboard nor the mouse works. On the 18.04 machine I can see

lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and it is the Logitech, Inc. Unifying Receiver which appears when the
USB from the KVM is connected. On the 20.04 machine only this appears

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have tested installation discs from 19.04 onwards. The failure first
appears in 19.10 and is still present in 21.04

I can observe a similar problem with a dual boot laptop running windows
10 and 20.04. With windows 10 I can use it with the KVM for screen and
keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not
work. This issue has also been observed here
https://unix.stackexchange.com/questions/646515/using-logitech-mouse-
keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it
using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model).

I had to report this originally against xorg as this bug reporting
system seems not to allow reporting of bugs against unknown packages. I
also had to report it through the ubuntu-bug executable as I've been
unable to find a way in launchpad of reporting a bug (as opposed to
getting a guided tour about reporting bugs).

I am happy to supply more info and test fixes if I am asked but as with
this type of bug where something fails to happen rather than something
wrong happens I don't know what to look at.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Fri Jun  4 20:21:15 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
InstallationDate: Installed on 2021-05-14 (21 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
 Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
 |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: ASUS System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/27/2021
dmi.bios.release: 8.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0820
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H570M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0820:bd04/27/2021:br8.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH570M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1

[Touch-packages] [Bug 1930903] [NEW] Frequent kernel oops related to nvidia / nv_drm_master_set

2021-06-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After upgrading yesterday from ubuntu 20 to 21.04 my machine now
exhibits frequent involuntary restarts, related to a kernel oops of the
form

Jun  3 10:48:32 zotac kernel: [   20.464926] RIP: 
0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
[...]
Jun  3 10:48:32 zotac kernel: [   20.464958] Call Trace:
Jun  3 10:48:32 zotac kernel: [   20.464964]  drm_new_set_master+0x7e/0x100 
[drm]
Jun  3 10:48:32 zotac kernel: [   20.464994]  drm_master_open+0x6e/0xa0 [drm]
Jun  3 10:48:32 zotac kernel: [   20.465017]  drm_open+0xf8/0x250 [drm]
Jun  3 10:48:32 zotac kernel: [   20.465044]  drm_stub_open+0xba/0x140 [drm]
Jun  3 10:48:32 zotac kernel: [   20.465070]  chrdev_open+0xf7/0x220
Jun  3 10:48:32 zotac kernel: [   20.465075]  ? cdev_device_add+0x90/0x90
Jun  3 10:48:32 zotac kernel: [   20.465078]  do_dentry_open+0x156/0x370
Jun  3 10:48:32 zotac kernel: [   20.465081]  vfs_open+0x2d/0x30
Jun  3 10:48:32 zotac kernel: [   20.465084]  do_open+0x1c3/0x340
Jun  3 10:48:32 zotac kernel: [   20.465087]  path_openat+0x10a/0x1d0
Jun  3 10:48:32 zotac kernel: [   20.465090]  do_filp_open+0x8c/0x130
Jun  3 10:48:32 zotac kernel: [   20.465093]  ? __check_object_size+0x1c/0x20
Jun  3 10:48:32 zotac kernel: [   20.465096]  do_sys_openat2+0x9b/0x150
Jun  3 10:48:32 zotac kernel: [   20.465099]  __x64_sys_openat+0x56/0x90
Jun  3 10:48:32 zotac kernel: [   20.465102]  do_syscall_64+0x38/0x90
Jun  3 10:48:32 zotac kernel: [   20.465105]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun  3 10:48:32 zotac kernel: [   20.465108] RIP: 0033:0x7fe6ea270954

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
.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  460.80  Fri May  7 06:55:54 
UTC 2021
 GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Jun  4 17:00:45 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.80, 5.11.0-18-generic, x86_64: installed
 nvidia, 460.80, 5.8.0-53-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
InstallationDate: Installed on 2020-05-09 (391 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: NA ZBOX-ER51070
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Default string
dmi.board.name: ZBOX-ER51070
dmi.board.vendor: NA
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: ZBOX-ER51070
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: NA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute ubuntu
-- 
Frequent kernel oops related to nvidia / nv_drm_master_set
https://bugs.launchpad.net/bugs/1930903
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 

[Touch-packages] [Bug 1918021] Re: Got Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write privilege to the state data while building simple Docker container

2021-06-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: docker.io (Ubuntu)
   Status: New => Confirmed

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

Title:
  Got Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write
  privilege to the state data while building simple Docker container

Status in docker.io package in Ubuntu:
  Confirmed
Status in libpaper package in Ubuntu:
  Invalid
Status in ucf package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Have simple Dockerfile as shown below:

  ```
  mkdir ~/ubuntu-mate-hirsute
  cat < ~/ubuntu-mate-hirsute/Dockerfile
  FROM ubuntu:hirsute
  ENV SHELL=/bin/bash

  RUN apt-get update && \
  env DEBIAN_FRONTEND=noninteractive apt-get install -y ubuntu-mate-desktop

  CMD ["mate-session"]

  EOF
  ```

  2. Build this Dockerfile by the command shown below

   docker build ~/ubuntu-mate-hirsute/ -t ubuntu-mate:hirsute

  Expected result:
  * Docker container is built and tagged as it was requested - 
ubuntu-mate:hirsute .

  Actual results:
  * Docker container is not built, have the following errors instead:

  ...
  Setting up libpaper1:amd64 (1.1.28) ...
  ucf: do not have write privilege to the state data
  dpkg: error processing package libpaper1:amd64 (--configure):
   installed libpaper1:amd64 package post-installation script subprocess 
returned error exit status 1
  ...
  dpkg: dependency problems prevent configuration of libgs9:amd64:
   libgs9:amd64 depends on libpaper1; however:
Package libpaper1:amd64 is not configured yet.

  dpkg: error processing package libgs9:amd64 (--configure):
   dependency problems - leaving unconfigured
  ...
  Setting up fonts-tlwg-umpush (1:0.7.2-1build1) ...
  dpkg: dependency problems prevent configuration of libpaper-utils:
   libpaper-utils depends on libpaper1; however:
Package libpaper1:amd64 is not configured yet.

  dpkg: error processing package libpaper-utils (--configure):
   dependency problems - leaving unconfigured
  Setting up samba-common (2:4.13.3+dfsg-1ubuntu2) ...
  ucf: do not have write privilege to the state data
  dpkg: error processing package samba-common (--configure):
   installed samba-common package post-installation script subprocess returned 
error exit status 1
  ...
  dpkg: dependency problems prevent configuration of ghostscript:
   ghostscript depends on libgs9 (= 9.53.3~dfsg-7); however:
Package libgs9:amd64 is not configured yet.

  dpkg: error processing package ghostscript (--configure):
   dependency problems - leaving unconfigured
  ...
  Setting up fonts-tlwg-mono (1:0.7.2-1build1) ...
  dpkg: dependency problems prevent configuration of libatrildocument3:
   libatrildocument3 depends on libspectre1 (>= 0.2.3); however:
Package libspectre1:amd64 is not configured yet.

  dpkg: error processing package libatrildocument3 (--configure):
   dependency problems - leaving unconfigured
  ...
  dpkg: dependency problems prevent configuration of cups-daemon:
   cups-daemon depends on libpaper1; however:
Package libpaper1:amd64 is not configured yet.

  dpkg: error processing package cups-daemon (--configure):
   dependency problems - leaving unconfigured
  ...
  dpkg: dependency problems prevent configuration of atril:
   atril depends on libatrildocument3 (= 1.24.0-1); however:
Package libatrildocument3 is not configured yet.

  dpkg: error processing package atril (--configure):
   dependency problems - leaving unconfigured
  ...
  dpkg: dependency problems prevent configuration of libatrilview3:
   libatrilview3 depends on libatrildocument3 (= 1.24.0-1); however:
Package libatrildocument3 is not configured yet.

  dpkg: error processing package libatrilview3 (--configure):
   dependency problems - leaving unconfigured
  ...
  dpkg: dependency problems prevent configuration of smbclient:
   smbclient depends on samba-common (= 2:4.13.3+dfsg-1ubuntu2); however:
Package samba-common is not configured yet.

  dpkg: error processing package smbclient (--configure):
   dependency problems - leaving unconfigured
  ...
  dpkg: dependency problems prevent configuration of samba-common-bin:
   samba-common-bin depends on samba-common (= 2:4.13.3+dfsg-1ubuntu2); however:
Package samba-common is not configured yet.

  dpkg: error processing package samba-common-bin (--configure):
   dependency problems - leaving unconfigured
  ...
  dpkg: dependency problems prevent configuration of printer-driver-ptouch:
   printer-driver-ptouch depends on ghostscript; however:
Package ghostscript is not configured yet.

  dpkg: error processing package printer-driver-ptouch (--configure):
   dependency problems - leaving unconfigured
  ...
  dpkg: dependency problems prevent configuration of cups-filters:
   cups-filters depends on ghostscript; however:
Package ghostscript 

[Touch-packages] [Bug 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt

2021-06-03 Thread Launchpad Bug Tracker
This bug was fixed in the package python-apt - 2.1.3ubuntu1.4

---
python-apt (2.1.3ubuntu1.4) groovy; urgency=medium

  * debfile: Pass `Name` instead of `Binary` to ExtractTar.
Passing the binary causes it to fail trying to find the `false`
compressor when a binary for a given compressor is not installed.
(LP: #1926437)
  * Update mirror lists

 -- Julian Andres Klode   Thu, 29 Apr 2021 15:31:59
+0200

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

Title:
  [SRU] Backport zstd support, fix bug in python-apt

Status in apt package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in python-apt source package in Focal:
  Fix Released
Status in python-apt source package in Groovy:
  Fix Released
Status in python-apt source package in Hirsute:
  Fix Released
Status in python-apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  APT in xenial needs to learn about zstd support to enable Launchpad to work 
with zstd packages.

  python-apt in all releases needs to be adjusted to pass the compressor
  names instead of programs to ExtractTar, as otherwise, if
  /usr/bin/zstd does not exist, it will pass "false" as the compressor,
  and then ExtractTar fails (same for other compressors).

  On hirsute, the python-apt upload also includes some new  
annotations for build-dependencies, as it's a straight upload of the 2.2
  stable series.

  [Test plan]
  The apt regression tests cover the compression methods extensively, including 
even stored compressed lists in /var/lib/apt and fetching Packages files 
compressed with such methods, for all compression methods.

  The final test is to make apt_inst.DebFile("glibc-doc-
  reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
  1923845 work in python3-apt.

  For hirsute, the build dependency changes will verify themselves
  during the build ;)

  [Where problems could occur]

  APT:

  The changes to APT are adding the zstd compression backend to FileFd
  and then linking it into the configuration. The former is adding new
  code, triggered only on zstd files, and should not be able to cause
  regressions.

  The latter is a bunch of small lines here and there, and it caused
  issues during backporting in the test suite because it expected
  compressors in a specific order. However, chances are that nothing
  else has as stringent requirements as the test suite, so I don't
  believe that is a problem for existing users.

  Bugs can of course be in the code dealing with zstd, and that might
  open you up to security vulnerabilities in the zstd code if you pass
  APT zstd compressed files.

  A regression can be if clients used apt-helper cat-file to cat a zstd-
  compressed file ending in .zst - they'll now get uncompressed content,
  rather than compressed.

  python-apt:

  The change just replaces Binary with Name, aligning the code with APT
  itself, so it's so trivial, we don't expect regressions.

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

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


[Touch-packages] [Bug 1922380] Re: remove shim-signed very difficult

2021-06-02 Thread Launchpad Bug Tracker
[Expired for apt (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  remove shim-signed very difficult

Status in apt package in Ubuntu:
  Expired

Bug description:
  Hello
  I don't want the shim-signed anymore, but I need an additional password to 
remove it.

  
  This error is for all version of ubuntu.

  I am sure I am entering the correct one because I entered it using a
  copy paste technique.

  Have pity on those who do not know English well !!

  
  apt purge shim-signed
  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances   
  Lecture des informations d'état... Fait
  Les paquets suivants ont été installés automatiquement et ne sont plus 
nécessaires :
mokutil shim
  Veuillez utiliser « apt autoremove » pour les supprimer.
  Les paquets suivants seront ENLEVÉS :
shim-signed*
  ATTENTION : Les paquets essentiels suivants vont être enlevés.
  Vous NE devez PAS faire ceci, à moins de savoir exactement ce
  que vous êtes en train de faire.
shim-signed
  0 mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à jour.
  Après cette opération, 2 734 ko d'espace disque seront libérés.
  Vous êtes sur le point de faire quelque chose de potentiellement dangereux
  Pour continuer, tapez la phrase « Oui, faites ce que je vous dis ! »
   ?]Oui, faites ce que je vous dis ! 
  Annulation.

  
  root@a:~# export LANG=us

  root@a:~# apt purge shim-signed
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
mokutil shim
  Use 'apt autoremove' to remove them.
  The following packages will be REMOVED:
shim-signed*
  WARNING: The following essential packages will be removed.
  This should NOT be done unless you know exactly what you are doing!
shim-signed
  0 upgraded, 0 newly installed, 1 to remove and 171 not upgraded.
  After this operation, 2734 kB disk space will be freed.
  You are about to do something potentially harmful.
  To continue type in the phrase 'Yes, do as I say!'
   ?] Yes, do as I say! 
  perl: warning: Setting locale failed.
  perl: warning: Please check that your locale settings:
LANGUAGE = "fr_FR:fr_CA",
LC_ALL = (unset),
LC_TIME = "fr_FR.UTF-8",
LC_MONETARY = "fr_FR.UTF-8",
LC_ADDRESS = "fr_FR.UTF-8",
LC_TELEPHONE = "fr_FR.UTF-8",
LC_NAME = "fr_FR.UTF-8",
LC_MEASUREMENT = "fr_FR.UTF-8",
LC_IDENTIFICATION = "fr_FR.UTF-8",
LC_NUMERIC = "fr_FR.UTF-8",
LC_PAPER = "fr_FR.UTF-8",
LANG = "us"
  are supported and installed on your system.
  perl: warning: Falling back to the standard locale ("C").
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  dpkg: warning: overriding problem because --force enabled:
  dpkg: warning: this is a protected package; it should not be removed
  (Reading database ... 211327 files and directories currently installed.)
  Removing shim-signed (1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
  (Reading database ... 211314 files and directories currently installed.)
  Purging configuration files for shim-signed 
(1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  root@a:~#

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: evince 3.38.0-1
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 15:07:48 2021
  InstallationDate: Installed on 2020-10-25 (159 days ago)
  InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  KernLog:
   
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1930567] Re: Popup menu handling broken with multiple monitors in Wayland sessions

2021-06-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Popup menus don't appear at all if opened close to inter-monitor
  boundaries in Wayland sessions

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I have two (hopefully related) problems with popup-menus for
  applications on an external monitor.  For background I have two
  displays, the first a builtin LCD panel, the second and HDMI connected
  LCD monitor.  The external monitor is stacked "above" the internal LCD
  panel, the internal LCD panel is the "primary" display from a where
  the dash et al are placed.

  The first issue occurs with gnome-terminal.  When using right-click on
  an element in the window such as a link, a menu is shown to allow
  OpenURL et al.  This menu will not appear when the link it too close
  to the bottom of the upper display (the external one); the cursor
  changes to the arrow menu item selector cursor but not menu is
  rendered.  This occurs regardless of whether the window is maximised
  and it related to proximity to the boundary of the display.  It
  behaves correctly at the bottom boundary of the lower display.  Two
  screenshots attached showing it working/not-working.

  The second issue occurs in firefox.  When it is rendered on the upper
  displays its internal menus are displayed at the top of the lower
  display rather than on the upper display rooted at the menu item
  itself.  This also does not occur on the lower display.  Screenshot
  attached.

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

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


[Touch-packages] [Bug 1930567] Re: Popup menu handling broken with multiple monitors in Wayland sessions

2021-06-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Popup menus don't appear at all if opened close to inter-monitor
  boundaries in Wayland sessions

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I have two (hopefully related) problems with popup-menus for
  applications on an external monitor.  For background I have two
  displays, the first a builtin LCD panel, the second and HDMI connected
  LCD monitor.  The external monitor is stacked "above" the internal LCD
  panel, the internal LCD panel is the "primary" display from a where
  the dash et al are placed.

  The first issue occurs with gnome-terminal.  When using right-click on
  an element in the window such as a link, a menu is shown to allow
  OpenURL et al.  This menu will not appear when the link it too close
  to the bottom of the upper display (the external one); the cursor
  changes to the arrow menu item selector cursor but not menu is
  rendered.  This occurs regardless of whether the window is maximised
  and it related to proximity to the boundary of the display.  It
  behaves correctly at the bottom boundary of the lower display.  Two
  screenshots attached showing it working/not-working.

  The second issue occurs in firefox.  When it is rendered on the upper
  displays its internal menus are displayed at the top of the lower
  display rather than on the upper display rooted at the menu item
  itself.  This also does not occur on the lower display.  Screenshot
  attached.

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

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


[Touch-packages] [Bug 1930567] Re: Popup menu handling broken with multiple monitors in Wayland sessions

2021-06-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  Popup menus don't appear at all if opened close to inter-monitor
  boundaries in Wayland sessions

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I have two (hopefully related) problems with popup-menus for
  applications on an external monitor.  For background I have two
  displays, the first a builtin LCD panel, the second and HDMI connected
  LCD monitor.  The external monitor is stacked "above" the internal LCD
  panel, the internal LCD panel is the "primary" display from a where
  the dash et al are placed.

  The first issue occurs with gnome-terminal.  When using right-click on
  an element in the window such as a link, a menu is shown to allow
  OpenURL et al.  This menu will not appear when the link it too close
  to the bottom of the upper display (the external one); the cursor
  changes to the arrow menu item selector cursor but not menu is
  rendered.  This occurs regardless of whether the window is maximised
  and it related to proximity to the boundary of the display.  It
  behaves correctly at the bottom boundary of the lower display.  Two
  screenshots attached showing it working/not-working.

  The second issue occurs in firefox.  When it is rendered on the upper
  displays its internal menus are displayed at the top of the lower
  display rather than on the upper display rooted at the menu item
  itself.  This also does not occur on the lower display.  Screenshot
  attached.

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

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


[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

2021-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-release-upgrader - 1:20.10.16

---
ubuntu-release-upgrader (1:20.10.16) groovy; urgency=medium

  * DistUpgrade/DistUpgradeController.py: restore sources.list where possible
if a KeyboardInterrupt event is received and redirect the output of
gnome-session-inhibit to devnull so a message regarding Ctrl-C is not
displayed. (LP: #1898026)
  * Update mirrors, demotions, and translations.

 -- Brian Murray   Fri, 14 May 2021 10:27:44 -0700

** Changed in: ubuntu-release-upgrader (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1898026

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in ubuntu-release-upgrader source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Calling update() or installing packages from apt clients resets their SIGINT 
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have 
set for them.

  In case of ubuntu-release-upgrader, this results in the release
  upgrader being unable to handle interrupts after it did the initial
  update - the default libc handler will run and the program exits.

  [Test plan]

  [[apt]]
  As a standalone test for apt, we can test the following script:

  import apt
  import time

  apt.Cache().update()
  print("WAITING")
  try:
  time.sleep(1)
  except BaseException as e:
  print("Seen", repr(e))
  print("END")

  Pressing Ctrl+C while WAITING is printed should print Seen
  KeyboardInterrupt, and importantly, also the END line.

  [[ubuntu-release-upgrader]]
  1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
  2) At the "Do you want to start the upgrade?" question say Y.
  3) When you see the "Lock screen disabled" message you will also see 
"Inhibiting until Ctrl+C is pressed".
  4) Press "Ctrl+C"

  Your /etc/apt/sources.list file will now have focal in it instead of
  bionic although the upgrade has quit. With the version of ubuntu-
  release-upgrader in -proposed you will not see the "Ctrl+C" message.
  For your sources.list file to be restored you'll need the version of
  apt from bionic-proposed installed before starting the upgrade.

  [Where problems could occur]
  apt: This specific change removes the two lines that SIG_DFL the signal 
handlers after running scripts. AFAWCT those lines are unnecessary - the code 
that calls it temporarily sets the handlers to SIG_IGN but restores previous 
handlers at the end; it was wrongly refactored decades ago. A regression could 
occur in that those signals will now continue to be ignored if we missed a spot.

  ubuntu-release-upgrader: The change is wrapping a bunch of code in a
  try: except: block so if the indentation was off the pyflakes /
  pycodestyle tests would fail but autopkgtest will catch that.

  [Original bug report]
  As a long-time-user of ?ubuntu, with apt-get as tool of choice for 
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
  In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu 
version; just all packages including new ones. Version updates had to be 
initiated manually, and I was always asked if I really wanted the new ?ubuntu 
version. Sounds appropriate.

  Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. 
I for one consider this kind of intrusive, though.
  It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a 
number of times earlier; just to *check* if the upgrade was on offer; but this 
is only a guess.

  In *any* case, a pop-up asking "Are you sure? Are you connected
  through an adequate pipe? Are you sitting with full batteries; better
  a power supply?" would be convenient; since I am using my PC for
  urgent duties, and didn't want to fiddle with unexpected upgrade bugs.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:48:39 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 

[Touch-packages] [Bug 1796712] Re: libcurl3-gnutls in trusty fails to verify certificates when certificate chain is out-of-order

2021-06-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  libcurl3-gnutls in trusty fails to verify certificates when
  certificate chain is out-of-order

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  libcurl3-gnutls 7.35.0-1ubuntu2.17 fails to verify remote certificate
  if the certificate chain provided is out-of-order. This is caused by
  libgnutls-dev package dependency, since libgnutls26 package is
  apparently long known to have this issue:
  https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1373422

  This bug can be observed with git, which depends on libcurl3-gnutls:

  git clone https://gnunet.org/git/libmicrohttpd.git/
  Cloning into 'libmicrohttpd'...
  fatal: unable to access 'https://gnunet.org/git/libmicrohttpd.git/': server 
certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt 
CRLfile: none

  libgnutls28 package fixes this issue, since out-of-order certificate
  chains are allowed in that package. I am not very familiar with debian
  packaging process, so I was wondering if it is possible at all to bump
  dependency of libcurl3-gnutls from libgnutls-dev -> libgnutls28-dev
  for trusty.

  libgnutls28-dev conflicts with libgnutls-dev. At first sight, one of
  dependencies of libcurl3-gnutls-dev, lbrtmp-dev, also depends on
  libgnutls-dev. So, again I am not sure if this change is applicable or
  it causes nontrivial reverse-dependency issues.

  Given above bug filed against gnutls26 is still open after 4 years, I
  thought it might be easier to solve it on libcurl dependencies. (Is
  it?)

  Thanks.

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

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


[Touch-packages] [Bug 1926843] Re: online accounts integration with fb isn't working

2021-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-online-accounts -
3.36.1-0ubuntu1

---
gnome-online-accounts (3.36.1-0ubuntu1) focal; urgency=medium

  * New stable version (lp: #1925775)
  * debian/rules: disable the facebook provider since it's current not
working (lp: #1926843)

 -- Sebastien Bacher   Mon, 10 May 2021 17:03:46
+0200

** Changed in: gnome-online-accounts (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 gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1926843

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Released
Status in gnome-online-accounts source package in Hirsute:
  Fix Released

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions

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


[Touch-packages] [Bug 1925775] Re: SRU the current 3.36.1 stable update

2021-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-online-accounts -
3.36.1-0ubuntu1

---
gnome-online-accounts (3.36.1-0ubuntu1) focal; urgency=medium

  * New stable version (lp: #1925775)
  * debian/rules: disable the facebook provider since it's current not
working (lp: #1926843)

 -- Sebastien Bacher   Mon, 10 May 2021 17:03:46
+0200

** Changed in: gnome-online-accounts (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 gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1925775

Title:
  SRU the current 3.36.1 stable update

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some API documentation 
fixes and translation updates
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Try adding online account in a GNOME session, ensure the service is
  correctly enabled in application, for example that a google accounts
  are picked up in gnome-calendar and evolution.

  * Regression potential

  The changes are in API documentation so nothing specific to check, if
  there is an issue it would be from a toolchain regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1925775/+subscriptions

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


[Touch-packages] [Bug 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt

2021-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package python-apt - 2.0.0ubuntu0.20.04.5

---
python-apt (2.0.0ubuntu0.20.04.5) focal; urgency=medium

  * debfile: Pass `Name` instead of `Binary` to ExtractTar.
Passing the binary causes it to fail trying to find the `false`
compressor when a binary for a given compressor is not installed.
(LP: #1926437)
  * Update mirror lists

 -- Julian Andres Klode   Thu, 29 Apr 2021 16:12:21
+0200

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

Title:
  [SRU] Backport zstd support, fix bug in python-apt

Status in apt package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in python-apt source package in Focal:
  Fix Released
Status in python-apt source package in Groovy:
  Fix Committed
Status in python-apt source package in Hirsute:
  Fix Released
Status in python-apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  APT in xenial needs to learn about zstd support to enable Launchpad to work 
with zstd packages.

  python-apt in all releases needs to be adjusted to pass the compressor
  names instead of programs to ExtractTar, as otherwise, if
  /usr/bin/zstd does not exist, it will pass "false" as the compressor,
  and then ExtractTar fails (same for other compressors).

  On hirsute, the python-apt upload also includes some new  
annotations for build-dependencies, as it's a straight upload of the 2.2
  stable series.

  [Test plan]
  The apt regression tests cover the compression methods extensively, including 
even stored compressed lists in /var/lib/apt and fetching Packages files 
compressed with such methods, for all compression methods.

  The final test is to make apt_inst.DebFile("glibc-doc-
  reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
  1923845 work in python3-apt.

  For hirsute, the build dependency changes will verify themselves
  during the build ;)

  [Where problems could occur]

  APT:

  The changes to APT are adding the zstd compression backend to FileFd
  and then linking it into the configuration. The former is adding new
  code, triggered only on zstd files, and should not be able to cause
  regressions.

  The latter is a bunch of small lines here and there, and it caused
  issues during backporting in the test suite because it expected
  compressors in a specific order. However, chances are that nothing
  else has as stringent requirements as the test suite, so I don't
  believe that is a problem for existing users.

  Bugs can of course be in the code dealing with zstd, and that might
  open you up to security vulnerabilities in the zstd code if you pass
  APT zstd compressed files.

  A regression can be if clients used apt-helper cat-file to cat a zstd-
  compressed file ending in .zst - they'll now get uncompressed content,
  rather than compressed.

  python-apt:

  The change just replaces Binary with Name, aligning the code with APT
  itself, so it's so trivial, we don't expect regressions.

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

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


[Touch-packages] [Bug 1922951] Re: SRU the current 3.36.5 stable update

2021-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package evolution-data-server -
3.36.5-0ubuntu1

---
evolution-data-server (3.36.5-0ubuntu1) focal; urgency=medium

  * New stable version (lp: #1922951)
  * debian/patches/git_imapx_compat.patch: cherry pick a fix needed for
compatibility with the new iCloud behaviour (lp: #1925742)

 -- Sebastien Bacher   Wed, 07 Apr 2021 20:27:39
+0200

** Changed in: evolution-data-server (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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1922951

Title:
  SRU the current 3.36.5 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

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

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


[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

2021-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package evolution-data-server -
3.36.5-0ubuntu1

---
evolution-data-server (3.36.5-0ubuntu1) focal; urgency=medium

  * New stable version (lp: #1922951)
  * debian/patches/git_imapx_compat.patch: cherry pick a fix needed for
compatibility with the new iCloud behaviour (lp: #1925742)

 -- Sebastien Bacher   Wed, 07 Apr 2021 20:27:39
+0200

** Changed in: evolution-data-server (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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1925742

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

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

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


[Touch-packages] [Bug 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt

2021-06-01 Thread Launchpad Bug Tracker
This bug was fixed in the package python-apt -
1.1.0~beta1ubuntu0.16.04.12

---
python-apt (1.1.0~beta1ubuntu0.16.04.12) xenial; urgency=medium

  * debfile: Pass `Name` instead of `Binary` to ExtractTar.
Passing the binary causes it to fail trying to find the `false`
compressor when a binary for a given compressor is not installed.
(LP: #1926437)
  * Update mirror lists

 -- Julian Andres Klode   Thu, 29 Apr 2021 21:37:32
+0200

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

Title:
  [SRU] Backport zstd support, fix bug in python-apt

Status in apt package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in python-apt source package in Focal:
  Fix Committed
Status in python-apt source package in Groovy:
  Fix Committed
Status in python-apt source package in Hirsute:
  Fix Released
Status in python-apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  APT in xenial needs to learn about zstd support to enable Launchpad to work 
with zstd packages.

  python-apt in all releases needs to be adjusted to pass the compressor
  names instead of programs to ExtractTar, as otherwise, if
  /usr/bin/zstd does not exist, it will pass "false" as the compressor,
  and then ExtractTar fails (same for other compressors).

  On hirsute, the python-apt upload also includes some new  
annotations for build-dependencies, as it's a straight upload of the 2.2
  stable series.

  [Test plan]
  The apt regression tests cover the compression methods extensively, including 
even stored compressed lists in /var/lib/apt and fetching Packages files 
compressed with such methods, for all compression methods.

  The final test is to make apt_inst.DebFile("glibc-doc-
  reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
  1923845 work in python3-apt.

  For hirsute, the build dependency changes will verify themselves
  during the build ;)

  [Where problems could occur]

  APT:

  The changes to APT are adding the zstd compression backend to FileFd
  and then linking it into the configuration. The former is adding new
  code, triggered only on zstd files, and should not be able to cause
  regressions.

  The latter is a bunch of small lines here and there, and it caused
  issues during backporting in the test suite because it expected
  compressors in a specific order. However, chances are that nothing
  else has as stringent requirements as the test suite, so I don't
  believe that is a problem for existing users.

  Bugs can of course be in the code dealing with zstd, and that might
  open you up to security vulnerabilities in the zstd code if you pass
  APT zstd compressed files.

  A regression can be if clients used apt-helper cat-file to cat a zstd-
  compressed file ending in .zst - they'll now get uncompressed content,
  rather than compressed.

  python-apt:

  The change just replaces Binary with Name, aligning the code with APT
  itself, so it's so trivial, we don't expect regressions.

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

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


[Touch-packages] [Bug 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt

2021-06-01 Thread Launchpad Bug Tracker
This bug was fixed in the package python-apt - 1.6.5ubuntu0.6

---
python-apt (1.6.5ubuntu0.6) bionic; urgency=medium

  * debfile: Pass `Name` instead of `Binary` to ExtractTar.
Passing the binary causes it to fail trying to find the `false`
compressor when a binary for a given compressor is not installed.
(LP: #1926437)
  * Update mirror lists

 -- Julian Andres Klode   Thu, 29 Apr 2021 21:33:02
+0200

** Changed in: python-apt (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: python-apt (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Backport zstd support, fix bug in python-apt

Status in apt package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in python-apt source package in Focal:
  Fix Committed
Status in python-apt source package in Groovy:
  Fix Committed
Status in python-apt source package in Hirsute:
  Fix Released
Status in python-apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  APT in xenial needs to learn about zstd support to enable Launchpad to work 
with zstd packages.

  python-apt in all releases needs to be adjusted to pass the compressor
  names instead of programs to ExtractTar, as otherwise, if
  /usr/bin/zstd does not exist, it will pass "false" as the compressor,
  and then ExtractTar fails (same for other compressors).

  On hirsute, the python-apt upload also includes some new  
annotations for build-dependencies, as it's a straight upload of the 2.2
  stable series.

  [Test plan]
  The apt regression tests cover the compression methods extensively, including 
even stored compressed lists in /var/lib/apt and fetching Packages files 
compressed with such methods, for all compression methods.

  The final test is to make apt_inst.DebFile("glibc-doc-
  reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
  1923845 work in python3-apt.

  For hirsute, the build dependency changes will verify themselves
  during the build ;)

  [Where problems could occur]

  APT:

  The changes to APT are adding the zstd compression backend to FileFd
  and then linking it into the configuration. The former is adding new
  code, triggered only on zstd files, and should not be able to cause
  regressions.

  The latter is a bunch of small lines here and there, and it caused
  issues during backporting in the test suite because it expected
  compressors in a specific order. However, chances are that nothing
  else has as stringent requirements as the test suite, so I don't
  believe that is a problem for existing users.

  Bugs can of course be in the code dealing with zstd, and that might
  open you up to security vulnerabilities in the zstd code if you pass
  APT zstd compressed files.

  A regression can be if clients used apt-helper cat-file to cat a zstd-
  compressed file ending in .zst - they'll now get uncompressed content,
  rather than compressed.

  python-apt:

  The change just replaces Binary with Name, aligning the code with APT
  itself, so it's so trivial, we don't expect regressions.

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

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


[Touch-packages] [Bug 1926843] Re: online accounts integration with fb isn't working

2021-06-01 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-online-accounts -
3.38.1-1ubuntu1.1

---
gnome-online-accounts (3.38.1-1ubuntu1.1) hirsute; urgency=medium

  * debian/rules:
- disable the facebook provider since it's current not working
  (lp: #1926843)

 -- Sebastien Bacher   Fri, 07 May 2021 17:16:05
+0200

** Changed in: gnome-online-accounts (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Committed
Status in gnome-online-accounts source package in Hirsute:
  Fix Released

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions

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


[Touch-packages] [Bug 269441] Re: Trash always full

2021-06-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Trash always full

Status in Ubuntu MATE:
  Confirmed
Status in caja package in Ubuntu:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  I've seen other users having problems with that the trash appears
  empty even though it isn't. I have the opposite problem: my trash icon
  on the desktop always appears full, even if empty.

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

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


[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x

2021-06-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.11.0-18.19

---
linux (5.11.0-18.19) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460

  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files

  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper
- bpf: Tighten speculative pointer arithmetic mask
- perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3
- perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[]
- perf auxtrace: Fix potential NULL pointer dereference
- perf map: Fix error return code in maps__clone()
- HID: google: add don USB id
- HID: asus: Add support for 2021 ASUS N-Key keyboard
- HID: alps: fix error return code in alps_input_configured()
- HID cp2112: fix support for multiple gpiochips
- HID: wacom: Assign boolean values to a bool variable
- soc: qcom: geni: shield geni_icc_get() for ACPI boot
- dmaengine: xilinx: dpdma: Fix descriptor issuing on video group
- dmaengine: xilinx: dpdma: Fix race condition in done IRQ
- ARM: dts: Fix swapped mmc order for omap3
- m68k: fix flatmem memory model setup
- net: geneve: check skb is large enough for IPv4/IPv6 header
- dmaengine: tegra20: Fix runtime PM imbalance on error
- s390/entry: save the caller of psw_idle
- arm64: kprobes: Restore local irqflag if kprobes is cancelled
- xen-netback: Check for hotplug-status existence before watching
- cavium/liquidio: Fix duplicate argument
- csky: change a Kconfig symbol name to fix e1000 build error
- ia64: fix discontig.c section mismatches
- ia64: tools: remove duplicate definition of ia64_mf() on ia64
- x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access
- net: hso: fix NULL-deref on disconnect regression
- USB: CDC-ACM: fix poison/unpoison imbalance
- Linux 5.11.17

  * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184)
- locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

  * Fix kernel panic at boot on dual GFX systems (LP: #1926792)
- drm/amdgpu: Register VGA clients after init can no longer fail

  * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode
(LP: #1925075)
- ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure

  * CirrusLogic: Cracking noises appears in built-in speaker when output volume
is set >80% (LP: #1924997)
- ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye

  * CirrusLogic: The default input volume is "0%" (LP: #1923557)
- ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB

  * Fix no picture from HDMI when it's plugged after boot (LP: #1924238)
- drm/i915/display: Handle lane polarity for DDI port

  * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k
60Hz output (LP: #1922754)
- drm/amd/display: Try YCbCr420 color when YCbCr444 fails

  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev
  struct
- AMD_SFH: Add sensor_mask module parameter
- AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus
  bits
- mtd: rawnand: mtk: Fix WAITRDY break condition and timeout
- Input: nspire-keypad - enable interrupts only when opened
- gpio: sysfs: Obey valid_mask
- dmaengine: idxd: Fix clobbering of SWERR overflow bit on writeback
- dmaengine: idxd: fix delta_rec and crc size field for completion record
- dmaengine: idxd: fix opcap sysfs attribute 

[Touch-packages] [Bug 1930305] [NEW] [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all

2021-05-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hello,

So I use Ubuntu 20.04 LTS for a month. Firstly thank you for such a good
and progressive operating system. Here is the problem:

Normally, sound works perfectly when the output device is speakers. It
is also works when I plugged in the headphone on PC when the system is
on. However whenever I try to plug in the headphone when the system is
locked (on locked screen) the headphone does not work anymore even I
restart. But it works when I try to plug in it when the lock screen is
not active on next day. It is not working right now. The list of Output
Devices in the Settings:

- Speakers - Built-in Audio
- Headphones - Built-in Audio

When I select headphones, the sound is gone at all.

Also yes, I tried to use headphone on another devices and they work
perfectly.

I will put all informations that you might want. Please let me know if
you need more information. I am also not sure if I chose the right
output device.

Thank you.

Release: Ubuntu 20.04.2 LTS

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  oldner 3424 F pulseaudio
 /dev/snd/controlC1:  oldner 3424 F pulseaudio
 /dev/snd/pcmC1D0c:   oldner 3424 F...m pulseaudio
 /dev/snd/pcmC1D0p:   oldner 3424 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 31 20:29:49 2021
InstallationDate: Installed on 2021-05-26 (4 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  oldner 3424 F pulseaudio
 /dev/snd/controlC1:  oldner 3424 F pulseaudio
 /dev/snd/pcmC1D0c:   oldner 3424 F...m pulseaudio
 /dev/snd/pcmC1D0p:   oldner 3424 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: No sound at all
Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out, Left] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 05VVC5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron5537:pvrA12:rvnDellInc.:rn05VVC5:rvrA00:cvnDellInc.:ct8:cvrA12:
dmi.product.family: 00
dmi.product.name: Inspiron 5537
dmi.product.sku: Inspiron 5537
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal
-- 
[Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all
https://bugs.launchpad.net/bugs/1930305
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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 1930279] [NEW] winking triangles on screen

2021-05-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking
triangles on my screen, they sometimes will appear when i watching a
youtube video they will appear on the video's seek bar or when i typing
they will appear on selected texts,but the main and most annoying state
of it happens when I am playing minecraft,my entire game screen has
these little triangles

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 31 18:05:33 2021
DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: groovy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
 virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
InstallationDate: Installed on 2020-01-10 (507 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago)
dmi.bios.date: 03/19/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1204
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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 groovy third-party-packages ubuntu
-- 
winking triangles on screen
https://bugs.launchpad.net/bugs/1930279
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1929921] [NEW] Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in eddsa_test

2021-05-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

---Problem Description---
===
IBM z15 with D41C Bundle S39a and z/VM 7.2.0 guest with crypto cards attached 
OS: Ubuntu 20.04.2 (focal fossa) with 5.4.0-73-generic and libica 3.6.1 
installed
Core dump when running the eddsa_test from libica

Details
===
The available openSSL version is: OpenSSL 1.1.1f  31 Mar 2020
The ibmca engine was installed, but not defined into the openssl.cnf file,
openssl engine displayed the default line:
   (dynamic) Dynamic engine loading support

The segmentation fault was generated by `./eddsa_test'.
Program terminated with signal SIGSEGV, Segmentation fault in openSSL 
(gdb) bt
#0  0x03ff896e50be in OPENSSL_cleanse () from 
/lib/s390x-linux-gnu/libcrypto.so.1.1
#1  0x03ff898a26fa in ica_ed25519_ctx_del (ctx=0x3fff9b7e010) at 
ica_api.c:1897
#2  0x02aa28986f14 in ed25519_stress () at eddsa_test.c:441
#3  0x02aa289831bc in main (argc=0x1, argv=0x3fff9b7eaf8) at eddsa_test.c:66

See https://wiki.ubuntu.com/Debug%20Symbol%20Packages about how to
define debug repositories

apt install libica3-dbgsym

#0  0x03ff896e50be in OPENSSL_cleanse () from 
/lib/s390x-linux-gnu/libcrypto.so.1.1
(gdb) bt
# coredumpctl dump 158582 > eddsa.core
   PID: 158582 (eddsa_test)
   UID: 0 (root)
   GID: 0 (root)
Signal: 11 (SEGV)
 Timestamp: Wed 2021-05-26 19:52:28 CEST (15h ago)
  Command Line: ./eddsa_test
Executable: /root/crypto/libica-3.6.1/test/eddsa_test
 Control Group: /user.slice/user-0.slice/session-9.scope
  Unit: session-9.scope
 Slice: user-0.slice
   Session: 9
 Owner UID: 0 (root)
   Boot ID: 6a7a23240f464a0d9f2d3fa3e82be73e
Machine ID: c933ae494f9a4c6e8d82625c952945d5
  Hostname: t3514002.lnxne.boe
   Storage: 
/var/lib/systemd/coredump/core.eddsa_test.0.6a7a23240f464a0d9f2d3fa3e82be73e.158582.1622051548.lz4
   Message: Process 158582 (eddsa_test) of user 0 dumped core.

Stack trace of thread 158582:
#0  0x03ff896e50be OPENSSL_cleanse (libcrypto.so.1.1 + 
0x1650be)
  
---uname output---
Linux system 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x 
s390x s390x GNU/Linux
 
Machine Type = Manufacturer:  IBM Type:   8561 Model:703 T01 
 ---Debugger---
A debugger was configured, however the system did not enter into the debugger
 
---Steps to Reproduce---
1.) install the github libica 3.6.1 package
and build the test cases
2.) cd .../libica-3.6.1
3.) ./bootstrap.sh; configure --enable-coverage
4.) make coverage
Watch the segmentation fault to happen
 
Userspace tool common name: eddsa_test 
 
The userspace tool has the following bit modes: 64bit 

Userspace rpm: libica3

Userspace tool obtained from project website:  na


The problem could be reproduced with libica 3.6.1, however, it does not show up 
with libica 3.8.0. Looks like the problem was fixed by commit 

https://github.com/opencryptoki/libica/commit/b40d0d2ad4a2aac088cf47befbddd8b3b9fca1c5

After applying this fix on top of 3.6.1, the segfault does not occur
anymore. It's sufficient to apply the 4 changes in eddsa_test.c.

** Affects: ubuntu-z-systems
 Importance: High
 Status: Invalid

** Affects: openssl (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: Invalid


** Tags: architecture-s39064 bugnameltc-192953 severity-high 
targetmilestone-inin20042
-- 
Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in eddsa_test
https://bugs.launchpad.net/bugs/1929921
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to openssl 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 1929825] [NEW] [Ubuntu 21.04] OSA Device doesn't get enabled if a vlan is specified on the kernel cmdline for the installer

2021-05-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The OSA Device doesn't get enabled if a vlan is specified on the kernel
cmdline for the installer.

with the cmdline
`ip=10.1.8.74::10.1.10.1:255.255.252.0::enc800.300:none nameserver=10.1.9.101 
vlan=enc800.300:enc800 
url=http://10.1.9.101:1002/iso/ubuntu-21.04-live-server-s390x.iso quiet ---`

the boot fails with this message and drops to a shell:
```
BusyBox v1.30.1 (Ubuntu 1:1.30.1-6ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.
 
(initramfs) [6n
ip: SIOCGIFFLAGS: No such device
ip: can't find device 'enc800'
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
no search or nameservers found in /run/net-enc800.300.conf /run/net-*.conf /run/
net6-*.conf
Connecting to 10.1.9.101:1002 (10.1.9.101:1002)
wget: can't connect to remote host (10.1.9.101): Network is unreachable
Unable to find a live file system on the network
```

It the zdev 800 doesn't get enabled.
``` 
ip addr
1: lo:  mtu 65536 qdisc noop qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
(initramfs) [6n
lszdev | grep 0.0.0800
qeth 0.0.0800:0.0.0801:0.0.0802  no  no
```

But I can enable it manually:
```
chzdev -e 800
QETH device 0.0.0800:0.0.0801:0.0.0802 configured
Note: The initial RAM-disk must be updated for these changes to take effect:
   - QETH device 0.0.0800:0.0.0801:0.0.0802
A manual update of the initial RAM-disk is required.
(initramfs) [6n
ip addr
1: lo:  mtu 65536 qdisc noop qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enc800:  mtu 1500 qdisc noop qlen 1000
link/ether f2:ae:7d:de:88:a0 brd ff:ff:ff:ff:ff:ff
```

The same cmdline (adjusted for the iso url) works on 20.04.
Between 20.04 and 21.04 the line 318 `echo "${VLAN}" | grep -q "${dev}" && 
continue` was added to /scripts/functions in the initrd.ubuntu. If I remove 
this line and repack the ramdisk the network boot works as expected like on 
ubuntu 20.04

** Affects: ubuntu-z-systems
 Importance: High
 Status: Fix Released

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


** Tags: architecture-s39064 bugnameltc-192957 severity-high 
targetmilestone-inin2104
-- 
[Ubuntu 21.04] OSA Device doesn't get enabled if a vlan is specified on the 
kernel cmdline for the installer
https://bugs.launchpad.net/bugs/1929825
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools 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 1152187] Re: [MIR] systemd

2021-05-31 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~utkarsh/ubuntu-seeds/+git/ubuntu-seeds/+merge/403505

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

Title:
  [MIR] systemd

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

Bug description:
  * The package is in universe and built on all archs:
  https://launchpad.net/ubuntu/+source/systemd/44-10ubuntu1

  * Rationale:

  - in a first step we want systemd-services promoted to replace ubuntu-
  system-services

  -  We will also want to move from consolekit to logind soon
  (https://blueprints.launchpad.net/ubuntu/+spec/foundations-1303
  -consolekit-logind-migration)

  - udev has been merged in the systemd source upstream so we will want
  to build it from there at some point as well

  we don't plan to use the systemd init system at this point

  * Security:

  there has been some security issues in the past
  http://secunia.com/advisories/search/?search=systemd
  http://secunia.com/advisories/48220/
  http://secunia.com/advisories/48208/
  http://secunia.com/advisories/48331/

  Those are mostly logind issue and have been fixed upstream.

  Our current package is outdated but we do plan to update it before
  starting using logind. There should be no issue with the services

  * Quality:
  - there is no RC bug in debian: 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=systemd
  - there is no bug open in launchpad: 
https://launchpad.net/ubuntu/+source/systemd/+bugs
  - upstream is active and responsive to issues

  The desktop bugs team is subscribed to the package in launchpad,
  foundations/desktop will maintain the package and look to the bug
  reports regularly.

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

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


[Touch-packages] [Bug 1912911] Re: When printing with my Brother hl-2170w printer I keep getting an invalid page range error on a blank page, after the desired pages are printed

2021-05-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  When printing with my Brother hl-2170w printer I keep getting an
  invalid page range error on a blank page, after the desired pages are
  printed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I run uname -a, this is basically what I get:
  "5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux"

  apt-cache policy cups gives me the following:

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
===

  4 and 5 are being answered together...

  Before the upgrade, I was able to print one or more pages, and not see the 
extra error page.
  This is the desired behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 23 13:15:24 2021
  InstallationDate: Installed on 2020-12-21 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for SCRIBE: 
dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/
  MachineType: Dell Inc. Inspiron 7773
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/SCRIBE.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/SCRIBE.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=9899e123-f378-4328-a399-78cd6361f58e ro quiet splash 
resume=UUID=46e80ad1-16de-4fdf-b1f7-96f4f58b1c57
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0R58C3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd09/14/2017:br1.2:svnDellInc.:pnInspiron7773:pvr:rvnDellInc.:rn0R58C3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7773
  dmi.product.sku: 0809
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

2021-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package qtbase-opensource-src - 5.15.2+dfsg-6

---
qtbase-opensource-src (5.15.2+dfsg-6) unstable; urgency=medium

  * Backport upstream patch to adjust QMimeDatabase behavior (LP: #1857824).
  * Make qtbase5-dev break qt5-default (see #976389, LP: #1920130).

 -- Dmitry Shachnev   Sat, 29 May 2021 12:04:21
+0300

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04

2021-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package qtbase-opensource-src - 5.15.2+dfsg-6

---
qtbase-opensource-src (5.15.2+dfsg-6) unstable; urgency=medium

  * Backport upstream patch to adjust QMimeDatabase behavior (LP: #1857824).
  * Make qtbase5-dev break qt5-default (see #976389, LP: #1920130).

 -- Dmitry Shachnev   Sat, 29 May 2021 12:04:21
+0300

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

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

Title:
  System icons missing in kubuntu 21.04

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src-gles package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Hirsute:
  New
Status in qtbase-opensource-src-gles source package in Hirsute:
  New
Status in qtbase-opensource-src-gles package in Debian:
  Fix Released

Bug description:
  [Impact]

  This affects Groovy → Hirsute upgrades for users who had qt5-default
  package installed.

  For these users, apt could replace libqt5gui5 with libqt5gui5-gles,
  which is not suitable for most desktop systems and can result in all
  kinds of broken UI (such as missing icons).

  [Test Plan]

  1. Get a groovy amd64 system (e.g. a chroot).
  2. Install qt5-default package.
  3. Replace groovy with hirsute in /etc/apt/sources.list.
  4. Run "apt update".
  5. Run "apt dist-upgade".

  Incorrect behavior:

  The following packages will be REMOVED:
libqt5gui5 qt5-default qtbase5-dev
  The following NEW packages will be installed:
... libqt5gui5-gles ...

  Correct behavior: only qt5-default is removed, libqt5gui5 is not
  removed and libqt5gui5-gles is not installed.

  [Where problems could occur]

  The fix is adding "Breaks: qt5-default" in three packages:
  - qtbase5-dev (built from qtbase-opensource-src source).
  - qtbase5-gles-dev (built from qtbase-opensource-src-gles source).
  - libqt5gui5-gles (built from qtbase-opensource-src-gles source).

  It can affect apt's dependency resolver. Example of a problem may be
  the resolver keeping the old behavior in some cases.

  [Other Info]

  See this post for details on what the -gles packages are:
  https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html

  See my discussion with one of the developers of apt on this issue:
  https://lists.debian.org/debian-devel/2021/05/msg00076.html
  https://lists.debian.org/debian-devel/2021/05/msg00150.html
  https://lists.debian.org/debian-devel/2021/05/msg00162.html

  Also see this comment where I collected some links to stories of users who 
were affected by this bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389#10

  [Original Description]

  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  

[Touch-packages] [Bug 1928305] Re: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter

2021-05-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Lightdm ignores power saving settings; suspends system in 20 minutes
  regardless of sleep-inactive-ac-timeout parameter

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Dear colleagues,

  We have discovered an abnormal operation of the lightdm
  (1.30.0-0ubuntu4~20.04.1) program.

  1. When no user is logged in (the initial user selection screen is
  displayed) the idle system goes into suspend (sleep) mode. The timeout
  for this event is 20 minutes.

  2. I tried to cancel the entering into sleep mode. To do this, I
  altered the sleep-inactive-ac-timeout and sleep-inactive-battery-
  timeout parameters to 0.

  The command sudo -H -u lightdm dbus-launch --exit-with-session
  gsettings list-recursively org.gnome.settings-daemon.plugins.power
  gives the output:

  root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch 
--exit-with-session gsettings list-recursively 
org.gnome.settings-daemon.plugins.power
  No protocol specified
  org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend'
  org.gnome.settings-daemon.plugins.power time-critical 300
  org.gnome.settings-daemon.plugins.power power-button-action 'suspend'
  org.gnome.settings-daemon.plugins.power 
lid-close-suspend-with-external-monitor false
  org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate'
  org.gnome.settings-daemon.plugins.power idle-dim true
  org.gnome.settings-daemon.plugins.power button-power 'suspend'
  org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend'
  org.gnome.settings-daemon.plugins.power priority 0
  org.gnome.settings-daemon.plugins.power idle-brightness 30
  org.gnome.settings-daemon.plugins.power active true
  org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate'
  org.gnome.settings-daemon.plugins.power button-suspend 'suspend'
  org.gnome.settings-daemon.plugins.power button-sleep 'hibernate'
  org.gnome.settings-daemon.plugins.power percentage-critical 3
  org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
  org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend'
  org.gnome.settings-daemon.plugins.power ambient-enabled true
  org.gnome.settings-daemon.plugins.power notify-perhaps-recall true
  org.gnome.settings-daemon.plugins.power percentage-low 10
  org.gnome.settings-daemon.plugins.power percentage-action 2
  org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'
  org.gnome.settings-daemon.plugins.power time-low 1200
  org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
  org.gnome.settings-daemon.plugins.power time-action 120
  org.gnome.settings-daemon.plugins.power use-time-for-policy true

  
  3. I checked the result, the system still suspends (goes into sleep mode) in 
20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, 
because it may affect the suspend mode. It is set to ignore.

  #  This file is part of systemd.
  #
  #  systemd is free software; you can redistribute it and/or modify it
  #  under the terms of the GNU Lesser General Public License as published by
  #  the Free Software Foundation; either version 2.1 of the License, or
  #  (at your option) any later version.
  #
  # Entries in this file show the compile time defaults.
  # You can change settings by editing this file.
  # Defaults can be restored by simply deleting this file.
  #
  # See logind.conf(5) for details.

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  #HandleLidSwitch=suspend
  #HandleLidSwitchExternalPower=suspend
  #HandleLidSwitchDocked=ignore
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  IdleAction=ignore
  IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192

  I came to conclusion that lightdm ignores correctly given setting for
  not suspending the system (org.gnome.settings-daemon.plugins.power
  sleep-inactive-ac-timeout 0).

  Commentaries on this finding are welcome.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  PackageArchitecture: amd64
  Tags: focal third-party-packages
  Uname: Linux 5.4.96-050496-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago)
  UserGroups: 

[Touch-packages] [Bug 1928316] Re: package linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2021-05-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Unknown

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 13 11:26:52 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: initramfs-tools
  Title: package linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-05-28 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~os369510/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/403448

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

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in Provider for Plainbox - Checkbox:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

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

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


[Touch-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged

2021-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package pulseaudio - 1:14.2-2ubuntu2

---
pulseaudio (1:14.2-2ubuntu2) impish; urgency=medium

  * d/p/0016-check_off_profile_when_switching_profile.patch
  * d/p/0017-add_dynamic_priority_bonus_base_for_alsa_profiles.patch
Fix a "Rear Mic" always showing on input list when using dual codec.
(LP: #1929371)

 -- Jeremy Szu   Tue, 25 May 2021 12:41:39
+

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

Title:
  [SRU] there is always a "Rear Microphone - Built-in Audio" option on
  the input device list even if the microphone is unplugged

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  In Lenovo P520, which using a codec for front panel, the other codec for rear 
panel and both are on a same card.

  In this case, the rear Mic will present on input devices of "Sound
  Settings" even if attaching nothing to rear mic jack.

  [Fix]
  For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl 
because of
  ```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
  ```
  After applying "Rear Mic Jack", the rear Mic will not always there anymore 
but it's not there as well if hot-plugging audio device on rear mic. Thus, it 
needs to change pulseaudio to handle if all devices are off cases.

  For pulseaudio, if there is no any audio devices attached, then
  attaching an input device on rear mic jack. The port will not be
  selected automatically because the profiles is off. It needs patch
  pulseaudio to check off profiles (for dual codec case).

  [Test]
  After applying these patches, the rear mic jack works good in all cases (boot 
without mic and then attach mic, boot with mic and then hotplug it) and other 
functions (line-in / line-out) work pretty well.

  [Where problems could occur]
  This change only apply the bonus on below cases:
  ```
  if ((has_input_port && found_available_input_port && !has_output_port) ||
  (has_output_port && found_available_output_port && !has_input_port) ||
  (has_input_port && found_available_input_port && has_output_port && 
found_available_output_port)) 
  ```
  and these cases have been tested.
  If there are some complex codec design then it might cause problem but so far 
we didn't see that.

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

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


[Touch-packages] [Bug 1929854] [NEW] Vital and critical configuration files get overridden by system updates without warning

2021-05-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

• In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of 
special compose keys defined.
• In my /boot/grub/grub.cfg I have a very complicated special setup for my 
various boot configurations, and a 5-sec timout for my EFI-config.
• My /etc/ssh/sshd_config contains a well-balanced configuration 

All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING
or ASKING BACK by ubuntu system setups (discover).

I set all of them to read-only by root and no-access for group and other
users, but they still get overridden by every other system update.  I
even have a shutdown process in place which should actually make sure
that changes to these files are reverted by writing a backup copy over
any newly installed override — unfortunately, everything I did to run
either a custom shutdown process or a startup process with systemd
turned out to not work and be a nightmare to make work.

How somebody could be as bold as to override vital configuration files
like this without even asking  for consent is one of the strange
miracles in this world which I'll probably never understand.  However,
if "ubuntu" is really what it translates to, it should take a little bit
more care about pre-existing configurations on systems on which it is
set up and running well — until one system update suddenly jeopardizes
the functioning of the entire system.  I'm pretty sure these are not the
only configuration files which are carelessly just overridden.  They're
just the ones every other update breaks my system and inflinges on my
the costs of hours of research until I find out that — of course — it
was an overridden critical system configuration again.  The really mean
thing is that you don't notice anything when you run the update … only
next time you start your system and of course are not aware anymore that
you did a system update, the new (absolutely wrong and/or insufficent)
settings are in place and shoot you in the leg.

Take an example from gentoo's etc-update feature which lets you merge
new configuration files with pre-existing ones using a diff3-update.  I
went away from gentoo for other reasons, but I always praised that
feature.

Please make sure immediately that critical configuration files do not
get overridden if they are non-writable by root, and then gradually
introduce a system that merges changes to configuration files with the
current situation on the target system.  Or at least present the configs
that would be changed in a particular directory, so that anybody who is
interested in preserving local settings could merge them in a suitable
way.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu May 27 18:48:15 2021
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297]
InstallationDate: Installed on 2021-01-15 (132 days ago)
InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: LENOVO 20QQS0KL13
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic 
root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2020
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: N2NET38W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QQS0KL13
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: ZF211710
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P53
dmi.product.name: 20QQS0KL13
dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53
dmi.product.version: ThinkPad P53
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: 

[Touch-packages] [Bug 1929292] Re: ubiquity crashes whilst trying to use ubuntu-bug

2021-05-27 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/impish/apport/ubuntu

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

Title:
  ubiquity crashes whilst trying to use ubuntu-bug

Status in apport package in Ubuntu:
  In Progress

Bug description:
  Multiple identities can be used for authentication:
   1.  user,,, (user)
   2.  Jon Thackray,,, (jon)
  Choose identity to authenticate as (1-2): 2
  Password: 
  polkit-agent-helper-1: pam_authenticate failed: Authentication failure
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 158, in 
add_info
  add_installation_log(report, 'Casper', 'casper.log')
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 29, in 
add_installation_log
  if isinstance(report[ident], bytes):
File "/usr/lib/python3.8/collections/__init__.py", line 1010, in __getitem__
  raise KeyError(key)
  KeyError: 'Casper'

  My installation doesn't have /var/log/partman

  jon@frobenius:/var/lib$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  jon@frobenius:/var/lib$ apt-cache policy ubiquity
  ubiquity:
Installed: (none)
Candidate: 20.04.15.11
Version table:
   20.04.15.11 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   20.04.15 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  I expected to be able to report a bug I've found in qmail-run, but
  this seems to be a barrier to entry

  Instead I got to report ubiquity preventing me from reporting a bug

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat May 22 13:36:26 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-05-14 (8 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1929292] [NEW] ubiquity crashes whilst trying to use ubuntu-bug

2021-05-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Multiple identities can be used for authentication:
 1.  user,,, (user)
 2.  Jon Thackray,,, (jon)
Choose identity to authenticate as (1-2): 2
Password: 
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
 AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.
ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/package-hooks/source_ubiquity.py", line 158, in 
add_info
add_installation_log(report, 'Casper', 'casper.log')
  File "/usr/share/apport/package-hooks/source_ubiquity.py", line 29, in 
add_installation_log
if isinstance(report[ident], bytes):
  File "/usr/lib/python3.8/collections/__init__.py", line 1010, in __getitem__
raise KeyError(key)
KeyError: 'Casper'

My installation doesn't have /var/log/partman

jon@frobenius:/var/lib$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

jon@frobenius:/var/lib$ apt-cache policy ubiquity
ubiquity:
  Installed: (none)
  Candidate: 20.04.15.11
  Version table:
 20.04.15.11 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
 20.04.15 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

I expected to be able to report a bug I've found in qmail-run, but this
seems to be a barrier to entry

Instead I got to report ubiquity preventing me from reporting a bug

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat May 22 13:36:26 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2021-05-14 (8 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal rls-ff-incoming ubiquity-20.04.15.10
-- 
ubiquity crashes whilst trying to use ubuntu-bug
https://bugs.launchpad.net/bugs/1929292
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport 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 1785383] Re: missing EDNS0 record confuses systemd-resolved

2021-05-27 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/403382

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

Title:
  missing EDNS0 record confuses systemd-resolved

Status in systemd:
  Fix Released
Status in dnsmasq package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in dnsmasq source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  In Progress
Status in dnsmasq source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in dnsmasq source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  In Progress
Status in dnsmasq source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  In Progress
Status in dnsmasq source package in Impish:
  Fix Released
Status in systemd source package in Impish:
  Triaged

Bug description:
  [Impact]
  dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer 
for a domain it is authoritative for. systemd-resolved seems to get confused by 
this in certain circumstances; when using the stub resolver and requesting an 
address for which there are no  records, there can sometimes be a five 
second hang in resolution.

  [Fix]
  This is fixed by upstream commit 
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78

  Not sure if it is worth cherry picking? I imagine the most likely
  trigger will be dnsmasq on routers which are not likely to be running
  Ubuntu, but maybe just in case.

  I also think there are some logic issues in systemd-resolved, upstream
  bug filed:

  https://github.com/systemd/systemd/issues/9785

  [Test Case]
  Simple-ish test case for bionic:

  ---
  IFACE=dummy0
  SUBNET=10.0.0

  ip link add $IFACE type dummy
  ifconfig $IFACE ${SUBNET}.1/24
  dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,${SUBNET}.1 --server=/test/ &

  dig -t a test.test @10.0.0.1 | grep EDNS
  # should return "; EDNS ..."
  dig -t  test.test @10.0.0.1 | grep EDNS
  # again, should return "; EDNS ..." but doesn't
  ---

  To reproduce the systemd-resolved side of the problem

  ---
  # as above, but
  # now configure systemd-resolved to look at only 10.0.0.1, then

  systemd-resolve --reset-server-features
  # should exhibit five second delay then connect, assuming sshd is running :)
  ssh test.test
  ---

  
  More detailed test case for focal and later:

  install dnsmasq on a bionic system and start it, listening to an
  interface that is externally reachable, e.g. for a normal libvirt vm
  with interface name 'ens3':

  IFACE=ens3
  dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,1.2.3.4 --server=/test/

  note that the '1.2.3.4' address doesn't matter, any addr is ok.

  then setup a test system that can reach the dnsmasq system, and
  configure networkd to use the dnsmasq server, e.g. using config like:

  [Match]
  Name=ens3

  [Network]
  DHCP=yes
  DNS=DNSMASQ_IP_ADDRESS
  Domains=test

  [DHCPv4]
  UseDNS=no
  UseDomains=no

  replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
  dnsmasq is running, and replace 'ens3' with whatever the test system
  interface name is. Then restart systemd-networkd, and test:

  systemd-resolve --reset-server-features
  systemd-resolve --flush-caches
  host test.test

  The lookup using 'host' should complete immediately;.

  [Discussion]
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq-base 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Aug  4 11:33:56 2018
  InstallationDate: Installed on 2018-05-31 (64 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix

2021-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package pam - 1.1.8-3.6ubuntu2.18.04.3

---
pam (1.1.8-3.6ubuntu2.18.04.3) bionic; urgency=medium

  * Backport pam_faillock module from pam 1.4.0 (LP: #1927796)
- debian/patches-applied/add_pam_faillock.patch: add module.
- debian/patches-applied/pam_faillock_create_directory: create dir
  before creating file in modules/pam_faillock/faillock.c.
- debian/rules: set execute permissions on pam_faillock test.
- debian/libpam-modules-bin.install: install faillock binary and man
  page.

 -- Marc Deslauriers   Thu, 08 Apr 2021
07:27:58 -0400

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

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

Title:
  [SRU]pam_tally2 can cause accounts to be locked by correct password.
  pam_faillock use is the recommended fix

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Bionic:
  Fix Released
Status in pam source package in Focal:
  Fix Released
Status in pam source package in Groovy:
  Fix Released
Status in pam source package in Hirsute:
  Fix Released
Status in pam source package in Impish:
  Fix Released

Bug description:
  [IMPACT]
  There is a known issue in pam_tally2 which may cause an account to be lock 
down even with correct password, in a busy node environment where simultaneous 
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).

  There are already two customer cases from Canonical clients
  complaining about this behavior (00297697 and 00303806).

  Also, potentially, this will cause further problems in the future,
  since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to
  lock accounts when wrong passwords are used. And both benchmarks - but
  specially STIG - requires use of a lot of audit rules, which can lead
  to the busy node environment.

  The issue impacts all pam_tally2 versions distributed in all currently
  supported Ubuntu versions and also the next unreleased one. Note that,
  according to https://github.com/linux-pam/linux-pam/issues/71, there
  is no plan to fix this issue!

  [FIX]
  This fix proposes to add pam_faillock module to the PAM package, so users of 
pam_tally2 having issues can migrate to pam_faillock. We also plan to modify 
the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but 
in order to do so, we need the pam_faillock module to be available.

  Note that we don't propose to remove pam_tally2, since not every user
  of this module is affected.

  [TEST]
  Tested on a VM installed with Focal server iso and on another with Bionic 
server iso. Enabled pam_faillock module as recommeded by its man page. Then 
tried to log over ssh with an incorrect password, until the account got locked. 
Waited for the configured grace time to unlock and logged in using the correct 
password.

  Note that, since the pam_tally2 issue is caused by a racing condition,
  with a hard to recreate environment (we could not even reproduce it
  with pam_tally2), we could not reproduce the conditions to test
  pam_faillock with.

  [REGRESSION POTENTIAL]
  The regression potential for this is small, since we're not removing the old 
pam_tally2 module, just adding another one. So anyone still using pam_tally2 
will be able to do so.

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

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


[Touch-packages] [Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit

2021-05-26 Thread Launchpad Bug Tracker
This bug was fixed in the package sudo - 1.9.5p2-3ubuntu1

---
sudo (1.9.5p2-3ubuntu1) impish; urgency=low

  * Merge from Debian unstable (LP: #1929110). Remaining changes:
- debian/rules:
   + use dh-autoreconf
- debian/rules: stop shipping init scripts, as they are no longer
  necessary.
- debian/rules:
  + compile with --without-lecture --with-tty-tickets --enable-admin-flag
  + install man/man8/sudo_root.8 in both flavours
- debian/sudo.pam:
  + Use pam_env to read /etc/environment and /etc/default/locale
environment files. Reading ~/.pam_environment is not permitted due
to security reasons.
- debian/sudoers:
  + also grant admin group sudo access
  + include /snap/bin in the secure_path
  * Dropped changes, now included in Debian:
- debian/rules:
  + install apport hooks
- debian/sudo-ldap.dirs, debian/sudo.dirs:
  + add usr/share/apport/package-hooks

 -- William 'jawn-smith' Wilson   Thu, 20
May 2021 15:43:31 +

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

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

Title:
  Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit

Status in sudo package in Ubuntu:
  Fix Released

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

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

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


[Touch-packages] [Bug 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly

2021-05-26 Thread Launchpad Bug Tracker
This bug was fixed in the package procps - 2:3.3.17-5ubuntu1

---
procps (2:3.3.17-5ubuntu1) impish; urgency=low

  * Merge from Debian unstable.
Remaining changes:
  - autopkgtest for LP: #1874824. Submitted to debian as bug 988792
  - debian/sysctl.d (Ubuntu-specific):
+ 10-console-messages.conf: stop low-level kernel messages on console.
+ 10-kernel-hardening.conf: add the kptr_restrict setting
+ 10-ipv6-privacy.conf: add a file to sysctl.d to apply the defaults
  for IPv6 privacy extensions for interfaces. (LP: #176125, #841353)
+ 10-magic-sysrq.conf: Disable most magic sysrq by default, allowing
  critical sync, remount, reboot functions. (LP: #194676, LP: #1025467)
+ 10-network-security.conf: enable rp_filter.
+ 10-ptrace.conf: describe new PTRACE setting.
+ 10-zeropage.conf: safe mmap_min_addr value for graceful fall-back.
  for armhf, and arm64.
+ 10-qemu.conf.s390x for qemu.
+ README: describe how this directory is supposed to work.
  - debian/rules: Fix cross build
  - ignore_eaccess.patch: If we get eaccess when opening a sysctl file for
writing, don't error out.  Otherwise package upgrades can fail,
especially in containers.
- Adjust logic due to rc no longer being propagated (LP: #1903351)
  - ignore_erofs.patch: Same as ignore_eaccess but for the case where
part of /proc is read/only.
- Adjust logic due to rc no longer being propagated (LP: #1903351)
  - debian/procps.maintscript: handle migration of link-protect.conf from
/etc to /usr.
Justification of dropped patches
  - missing_potfiles_in: Debian has now added this code in POTFILES.in
so the patch is no longer needed
  - pmap_test: This patch disables some tests that are not causing
any problems. These tests are run in Debian so should be run
in Ubuntu as well
  - top_config_file_bwcompat: Debian has applied this code upstream so
the patch is no longer needed
  - tar-version: Debian has applied this code upstream so the patch is
no longer needed
  - stack_limit: Debian has applied this code upstream so the patch is
no longer needed

procps (2:3.3.17-5) unstable; urgency=medium

  * Add break/replace for conflicting manpages-fr-extra Closes: #986276

procps (2:3.3.17-4) unstable; urgency=medium

  * Remove w alternative in postinst Closes: #982803

procps (2:3.3.17-3) unstable; urgency=medium

  * Install language files Closes: #982437
  * Add epoch to manpages-pl Replaces/Breaks Closes: #982566
  * Remove conflict with w-bassman as removed in 2010
  * Remove w alternative as there is no alternative Closes: #982440
  * Update to debhelper 13
  * d/control: Remove conflict from non-existent pgrep package

procps (2:3.3.17-2) unstable; urgency=medium

  * Rename pwait to pidwait Closes: #982391
  * Mark autopkgtest as superficial Closes: #974459
  * Actually install the translated manpages Closes: #953743

procps (2:3.3.17-1) unstable; urgency=medium

  * New upstream source
- sysctl: Match systemd directory order Closes: #950788
- sysctl: Document directory order Closes: #951550
- top: ensure config file backward compatibility Closes: #951335

 -- William 'jawn-smith' Wilson   Wed, 19
May 2021 09:24:31 +

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

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

Title:
  ignore_eacces and ignore_erofs patches don't work properly

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Focal:
  New
Status in procps source package in Groovy:
  New

Bug description:
  The patches used to ignore errors in containers no longer work as of
  3.3.16 due to upstream commit https://gitlab.com/procps-
  ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932

  The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not 
WriteSetting
  Both patches ignore the change that rc is no longer propagated up and instead 
everything is trapped by:

  if (!ignore_failure && errno != ENOENT)
  rc = -1;

  
  Versions affected: focal+

  
  root@bfee89058713:/tmp# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.10 (Groovy Gorilla)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.10"
  VERSION_ID="20.10"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=groovy
  UBUNTU_CODENAME=groovy

  
  root@bfee89058713:/# dpkg -l procps
  Desired=Unknown/Install/Remove/Purge/Hold
  | 

[Touch-packages] [Bug 1929647] [NEW] debian helper tools for python never updates

2021-05-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

software updater prompts new updates
debian helper tools for python is always one of them but I cannot select the 
checkbox
so

debian helper tools for python never updates


Here's the screen shot
https://i.imgur.com/AjDd5yo.png

** Affects: python-debian (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
debian helper tools for python never updates
https://bugs.launchpad.net/bugs/1929647
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to python-debian 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 1921350] Re: UFW hangs indefinitely on any action

2021-05-25 Thread Launchpad Bug Tracker
[Expired for ufw (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  UFW hangs indefinitely on any action

Status in ufw package in Ubuntu:
  Expired

Bug description:
  When installing a new cloudserver (on Amazon EC2, if it makes a
  difference), UFW completely hangs on any command, for example ufw
  status. Interrupting it with Ctrl+C yields this backtrace:

  Traceback (most recent call last):
File "/usr/sbin/ufw", line 130, in 
  lock = create_lock(lockfile=lockfile, dryrun=pr.dryrun)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 1112, in create_lock
  fcntl.lockf(lock, fcntl.LOCK_EX)
  KeyboardInterrupt

  The line numbers are always the same.

  The platform is Ubuntu Server 20.04 (Ubuntu 20.04.2 LTS), from the
  Amazon image. I have not seen this bug on other servers. UFW is
  version 0.36.

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

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


[Touch-packages] [Bug 1929011] [NEW] Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

2021-05-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Left-Alt is always operational & Right-Alt is not at any time & not specific to 
this report's subject category.
True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso.
It is natural to use Right-Alt due to a closer distance to the SysRq key.
This might help explain why some say REISUB does not work.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screensaver (not installed)
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 20 00:27:12 2021
InstallationDate: Installed on 2020-07-14 (309 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal
-- 
Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot
https://bugs.launchpad.net/bugs/1929011
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-settings 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 1739510] Re: ill install you signature

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

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

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

Title:
  ill install you signature

Status in xorg package in Ubuntu:
  Expired

Bug description:
  hope you can help me. i cant affort another computer
  and spain is acting violence

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Dec 21 01:27:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:81ed]
  InstallationDate: Installed on 2017-12-19 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:651b Microdia 
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 276d:1160  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G5 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed 
root=UUID=d6ad60b5-3719-45b3-8b42-1bb91b324af7 ro nopat vesafb.invalid=1 
plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81ED
  dmi.board.vendor: HP
  dmi.board.version: 62.39
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd01/20/2017:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81ED:rvr62.39:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP 250 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec 21 00:06:27 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1929456] Re: XrandR does not propose 21:9 resolution

2021-05-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
   XrandR does not propose 21:9 resolution

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 
resolution".
  In bug 1895301 sombody wrote "We just need one person experiencing the bug to 
open a bug with the relevant system details automatically attached." - so I did.

  I have a similar problem with a 21:9 monitor with a resolution of
  2560x1080. It's a LG 25UB55-B on a HP docking station A7E32A, DVI
  output with adapter to HDMI, HDMI cable and input to the monitor via
  HDMI. Laptop is an HP Elitebook 8440p (Intel i5-520 with Intel HD
  Graphics (ILK)), internal display with 1366*768 is in use as well.

  I had Ubuntu 18.04 LTS before until January this year, with automatic
  updates on, so presumably up to date. There it worked fine out of the
  box, i.e. since first install I had the full resolution of 21:9 in
  2560x1080 on my external monitor.

  I didn't change any hardware, just installed Ubuntu 20.04 from DVD, an it 
stopped working.
  I got only 16:9 with 1920x1080.
  I've updated to Ubuntu 20.10, tried Ubuntu 21.04 (from DVD as well), changed 
cable and adapter, nothing helped.
  Did some reseach with google and found the mentioned bug 1895301. The 
workaround worked, I got full resolution of 2560x1080 on the external display.
  It is not permanent, so at the moment of filing this bug, I'm still back on 
the 16:9 with 1920x1080.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
  Date: Mon May 24 20:23:52 2021
  DistUpgraded: 2021-05-23 15:18:23,444 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder 
Verzeichnis nicht gefunden) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:172a]
  InstallationDate: Installed on 2021-02-10 (103 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP EliteBook 8440p
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to groovy on 2021-05-23 (1 days ago)
  dmi.bios.date: 09/13/2013
  dmi.bios.release: 15.36
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.24
  dmi.board.name: 172A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.34
  dmi.chassis.asset.tag: CZC040C94D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 48.52
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.24:bd09/13/2013:br15.36:efr48.52:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.34:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8440p
  dmi.product.sku: J2544631
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

2021-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.33

---
ubuntu-release-upgrader (1:20.04.33) focal; urgency=medium

  * DistUpgrade/DistUpgradeController.py: restore sources.list where possible
if a KeyboardInterrupt event is received and redirect the output of
gnome-session-inhibit to devnull so a message regarding Ctrl-C is not
displayed. (LP: #1898026)
  * DistUpgrade/DistUpgradeQuirks.py: Restore code which ensured the python
package was maked for removal. (LP: #1928397)
  * Update mirrors and translations.

 -- Brian Murray   Thu, 13 May 2021 16:38:41 -0700

** Changed in: ubuntu-release-upgrader (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1898026

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in ubuntu-release-upgrader source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Calling update() or installing packages from apt clients resets their SIGINT 
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have 
set for them.

  In case of ubuntu-release-upgrader, this results in the release
  upgrader being unable to handle interrupts after it did the initial
  update - the default libc handler will run and the program exits.

  [Test plan]

  [[apt]]
  As a standalone test for apt, we can test the following script:

  import apt
  import time

  apt.Cache().update()
  print("WAITING")
  try:
  time.sleep(1)
  except BaseException as e:
  print("Seen", repr(e))
  print("END")

  Pressing Ctrl+C while WAITING is printed should print Seen
  KeyboardInterrupt, and importantly, also the END line.

  [[ubuntu-release-upgrader]]
  1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
  2) At the "Do you want to start the upgrade?" question say Y.
  3) When you see the "Lock screen disabled" message you will also see 
"Inhibiting until Ctrl+C is pressed".
  4) Press "Ctrl+C"

  Your /etc/apt/sources.list file will now have focal in it instead of
  bionic although the upgrade has quit. With the version of ubuntu-
  release-upgrader in -proposed you will not see the "Ctrl+C" message.
  For your sources.list file to be restored you'll need the version of
  apt from bionic-proposed installed before starting the upgrade.

  [Where problems could occur]
  apt: This specific change removes the two lines that SIG_DFL the signal 
handlers after running scripts. AFAWCT those lines are unnecessary - the code 
that calls it temporarily sets the handlers to SIG_IGN but restores previous 
handlers at the end; it was wrongly refactored decades ago. A regression could 
occur in that those signals will now continue to be ignored if we missed a spot.

  ubuntu-release-upgrader: The change is wrapping a bunch of code in a
  try: except: block so if the indentation was off the pyflakes /
  pycodestyle tests would fail but autopkgtest will catch that.

  [Original bug report]
  As a long-time-user of ?ubuntu, with apt-get as tool of choice for 
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
  In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu 
version; just all packages including new ones. Version updates had to be 
initiated manually, and I was always asked if I really wanted the new ?ubuntu 
version. Sounds appropriate.

  Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. 
I for one consider this kind of intrusive, though.
  It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a 
number of times earlier; just to *check* if the upgrade was on offer; but this 
is only a guess.

  In *any* case, a pop-up asking "Are you sure? Are you connected
  through an adequate pipe? Are you sitting with full batteries; better
  a power supply?" would be convenient; since I am using my PC for
  urgent duties, and didn't want to fiddle with unexpected upgrade bugs.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: 

[Touch-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter

2021-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-settings - 20.04.6

---
ubuntu-settings (20.04.6) focal; urgency=medium

  * debian/ubuntu-settings.gsettings-override:
- use the same power options between session and greeter. (LP: #1902898)

 -- Didier Roche   Fri, 30 Apr 2021 09:01:06 +0200

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

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

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Focal:
  Fix Released
Status in ubuntu-settings source package in Hirsute:
  Fix Released

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

  [Test Plan] 
  1. Install new package and reboot
  2. On the greeter screen (gdm), press the physical power button of your 
machine.
  3. You should be now prompted about what to do, like shutdown. You can 
dismiss it.
  4. Clicking on the physical suspend button should suspend the machine 
immediatly.

  [Where problems could occur]
  We change the scope of when we applied those settings: we were only applying 
them to the GNOME session ran by the user, and it will now be applied as 
default to the GNOME session ran by gdm.
  Impacts is thus limited to the greeter screen.

  
  Diff is available on this commit: 
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89

  --
  Original report content:

  For a logged-in desktop user, they
  see:

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

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

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

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

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


[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix

2021-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package pam - 1.3.1-5ubuntu4.2

---
pam (1.3.1-5ubuntu4.2) focal; urgency=medium

  * Backport pam_faillock module from pam 1.4.0 (LP: #1927796)
- debian/patches-applied/add_pam_faillock.patch: add module.
- debian/patches-applied/pam_faillock_create_directory: create dir
  before creating file in modules/pam_faillock/faillock.c.
- debian/rules: set execute permissions on pam_faillock test.
- debian/libpam-modules-bin.install: install faillock binary and man
  page.

 -- Marc Deslauriers   Thu, 08 Apr 2021
07:06:27 -0400

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

Title:
  [SRU]pam_tally2 can cause accounts to be locked by correct password.
  pam_faillock use is the recommended fix

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

Bug description:
  [IMPACT]
  There is a known issue in pam_tally2 which may cause an account to be lock 
down even with correct password, in a busy node environment where simultaneous 
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).

  There are already two customer cases from Canonical clients
  complaining about this behavior (00297697 and 00303806).

  Also, potentially, this will cause further problems in the future,
  since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to
  lock accounts when wrong passwords are used. And both benchmarks - but
  specially STIG - requires use of a lot of audit rules, which can lead
  to the busy node environment.

  The issue impacts all pam_tally2 versions distributed in all currently
  supported Ubuntu versions and also the next unreleased one. Note that,
  according to https://github.com/linux-pam/linux-pam/issues/71, there
  is no plan to fix this issue!

  [FIX]
  This fix proposes to add pam_faillock module to the PAM package, so users of 
pam_tally2 having issues can migrate to pam_faillock. We also plan to modify 
the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but 
in order to do so, we need the pam_faillock module to be available.

  Note that we don't propose to remove pam_tally2, since not every user
  of this module is affected.

  [TEST]
  Tested on a VM installed with Focal server iso and on another with Bionic 
server iso. Enabled pam_faillock module as recommeded by its man page. Then 
tried to log over ssh with an incorrect password, until the account got locked. 
Waited for the configured grace time to unlock and logged in using the correct 
password.

  Note that, since the pam_tally2 issue is caused by a racing condition,
  with a hard to recreate environment (we could not even reproduce it
  with pam_tally2), we could not reproduce the conditions to test
  pam_faillock with.

  [REGRESSION POTENTIAL]
  The regression potential for this is small, since we're not removing the old 
pam_tally2 module, just adding another one. So anyone still using pam_tally2 
will be able to do so.

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

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


[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix

2021-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package pam - 1.3.1-5ubuntu6.20.10.1

---
pam (1.3.1-5ubuntu6.20.10.1) groovy; urgency=medium

  * Backport pam_faillock module from pam 1.4.0 (LP: #1927796)
- debian/patches-applied/add_pam_faillock.patch: add module.
- debian/patches-applied/pam_faillock_create_directory: create dir
  before creating file in modules/pam_faillock/faillock.c.
- debian/rules: set execute permissions on pam_faillock test.
- debian/libpam-modules-bin.install: install faillock binary and man
  page.

 -- Richard Maciel Costa   Thu, 08
Apr 2021 07:06:27 -0400

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

Title:
  [SRU]pam_tally2 can cause accounts to be locked by correct password.
  pam_faillock use is the recommended fix

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

Bug description:
  [IMPACT]
  There is a known issue in pam_tally2 which may cause an account to be lock 
down even with correct password, in a busy node environment where simultaneous 
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).

  There are already two customer cases from Canonical clients
  complaining about this behavior (00297697 and 00303806).

  Also, potentially, this will cause further problems in the future,
  since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to
  lock accounts when wrong passwords are used. And both benchmarks - but
  specially STIG - requires use of a lot of audit rules, which can lead
  to the busy node environment.

  The issue impacts all pam_tally2 versions distributed in all currently
  supported Ubuntu versions and also the next unreleased one. Note that,
  according to https://github.com/linux-pam/linux-pam/issues/71, there
  is no plan to fix this issue!

  [FIX]
  This fix proposes to add pam_faillock module to the PAM package, so users of 
pam_tally2 having issues can migrate to pam_faillock. We also plan to modify 
the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but 
in order to do so, we need the pam_faillock module to be available.

  Note that we don't propose to remove pam_tally2, since not every user
  of this module is affected.

  [TEST]
  Tested on a VM installed with Focal server iso and on another with Bionic 
server iso. Enabled pam_faillock module as recommeded by its man page. Then 
tried to log over ssh with an incorrect password, until the account got locked. 
Waited for the configured grace time to unlock and logged in using the correct 
password.

  Note that, since the pam_tally2 issue is caused by a racing condition,
  with a hard to recreate environment (we could not even reproduce it
  with pam_tally2), we could not reproduce the conditions to test
  pam_faillock with.

  [REGRESSION POTENTIAL]
  The regression potential for this is small, since we're not removing the old 
pam_tally2 module, just adding another one. So anyone still using pam_tally2 
will be able to do so.

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

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


[Touch-packages] [Bug 1928001] Re: [SRU] New stable release 2.68.1

2021-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package glib2.0 - 2.68.1-1~ubuntu21.04.1

---
glib2.0 (2.68.1-1~ubuntu21.04.1) hirsute; urgency=medium

  * debian/{control,gbp.conf}: Update branch refs for hirsute
  * Backport from Debian to hirsute for SRU (LP: #1928001)

glib2.0 (2.68.1-1) experimental; urgency=medium

  * New upstream stable release
  * d/tests/run-with-locales: Avoid FTBFS with locales-all installed

 -- Iain Lane   Mon, 10 May 2021 18:14:07 +0100

** Changed in: glib2.0 (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 2.68.1

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

Bug description:
  [ Description ]

  Take this new upstream stable release.

  * Fix a crash in `GKeyFile` when parsing a file which contains translations
using a `GKeyFile` instance which has loaded another file previously (#2361)

  * Pin GIO DLL in memory on Windows (!2016)

  * Bugs fixed:
   - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
   - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
   - !2016 GIO W32: Pin gio DLL
   - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
   - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
   - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
   - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

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

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

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

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


[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix

2021-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package pam - 1.3.1-5ubuntu6.21.04.1

---
pam (1.3.1-5ubuntu6.21.04.1) hirsute; urgency=medium

  * Backport pam_faillock module from pam 1.4.0 (LP: #1927796)
- debian/patches-applied/add_pam_faillock.patch: add module.
- debian/patches-applied/pam_faillock_create_directory: create dir
  before creating file in modules/pam_faillock/faillock.c.
- debian/rules: set execute permissions on pam_faillock test.
- debian/libpam-modules-bin.install: install faillock binary and man
  page.

 -- Richard Maciel Costa   Thu, 08
Apr 2021 07:06:27 -0400

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

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

Title:
  [SRU]pam_tally2 can cause accounts to be locked by correct password.
  pam_faillock use is the recommended fix

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

Bug description:
  [IMPACT]
  There is a known issue in pam_tally2 which may cause an account to be lock 
down even with correct password, in a busy node environment where simultaneous 
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).

  There are already two customer cases from Canonical clients
  complaining about this behavior (00297697 and 00303806).

  Also, potentially, this will cause further problems in the future,
  since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to
  lock accounts when wrong passwords are used. And both benchmarks - but
  specially STIG - requires use of a lot of audit rules, which can lead
  to the busy node environment.

  The issue impacts all pam_tally2 versions distributed in all currently
  supported Ubuntu versions and also the next unreleased one. Note that,
  according to https://github.com/linux-pam/linux-pam/issues/71, there
  is no plan to fix this issue!

  [FIX]
  This fix proposes to add pam_faillock module to the PAM package, so users of 
pam_tally2 having issues can migrate to pam_faillock. We also plan to modify 
the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but 
in order to do so, we need the pam_faillock module to be available.

  Note that we don't propose to remove pam_tally2, since not every user
  of this module is affected.

  [TEST]
  Tested on a VM installed with Focal server iso and on another with Bionic 
server iso. Enabled pam_faillock module as recommeded by its man page. Then 
tried to log over ssh with an incorrect password, until the account got locked. 
Waited for the configured grace time to unlock and logged in using the correct 
password.

  Note that, since the pam_tally2 issue is caused by a racing condition,
  with a hard to recreate environment (we could not even reproduce it
  with pam_tally2), we could not reproduce the conditions to test
  pam_faillock with.

  [REGRESSION POTENTIAL]
  The regression potential for this is small, since we're not removing the old 
pam_tally2 module, just adding another one. So anyone still using pam_tally2 
will be able to do so.

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

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


[Touch-packages] [Bug 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

2021-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu4.1

---
gtk+3.0 (3.24.25-1ubuntu4.1) hirsute; urgency=medium

  * debian/patches/git_imcontext.patch:
- cherry pick imcontext fixes until 3.24.29 (LP: #1925379)

 -- Rico Tzschichholz   Sat, 01 May 2021 10:01:31
+0200

** Changed in: gtk+3.0 (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Hirsute:
  Fix Released

Bug description:
  * Impact

  The auto-correction in libreoffice is not action as it should

  * Test case

  see comment 9

  * Regression potential

  The changes are in the input handling so check that standard input,
  keyboard layouts, compose and keybinding as worked as expected on
  different layout and language type, include ibus and chinese.

   
  I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then 
discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I 
was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, 
same LibreOffice profile, same LibreOffice document, and no changes on my part 
to my LibreOffice settings since I installed Ubuntu 21.04.

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

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


[Touch-packages] [Bug 559548] Re: fontconfig-config breaks monospace and diacritics

2021-05-23 Thread Launchpad Bug Tracker
[Expired for fontconfig (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  fontconfig-config breaks monospace and diacritics

Status in fontconfig package in Ubuntu:
  Expired

Bug description:
  Besides being redundant (see 
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/387848)
  45-latin.conf and 60-latin.conf have contradictory aliases settings. The 
superseding one, 45-latin.conf is breaking the 'monospace' alias font when 
combining diacritics are being used by prioritizing Bitstream Vera Sans Mono 
over DejaVu Sans Mono.
  DejaVu Sans Mono has characters and OpenType features Bitsteam Vera Sans Mono 
doesn't have. It doesn't make sense to prioritize Vera. This breaks things like 
"e" + U+0301, where 'e' comes from Vera and U+0301 comes from DejaVu.

  see https://bugzilla.mozilla.org/show_bug.cgi?id=556715 or
  https://bug556715.bugzilla.mozilla.org/attachment.cgi?id=436657 for
  example.

  45-latin.conf has
  
  Bitstream Vera Sans Mono
  DejaVu Sans Mono
  Liberation Mono
  Inconsolata
  Courier New
  Courier
  Andale Mono
  Luxi Mono
  Cumberland AMT
  Cumberland
  Nimbus Mono L
  monospace
  

  60-latin.conf has
  
  monospace
  
  DejaVu Sans Mono
  Bitstream Vera Sans Mono
  Inconsolata
  Andale Mono
  Courier New
  Cumberland AMT
  Luxi Mono
  Nimbus Mono L
  Courier
  
  

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

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


[Touch-packages] [Bug 1929329] [NEW] low graphic mode

2021-05-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

MY COMPUTER LAPTOP TELLS MY THAT MY "DEVICE IS RUNNING IN A LOW GRAPHIC
MODE". I don't know what to do.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun May 23 14:38:54 2021
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built
 tuxedo-wmi, 1.5.1, 4.15.0-140-generic, x86_64: installed
 tuxedo-wmi, 1.5.1, 4.15.0-142-generic, x86_64: installed
 tuxedo-wmi, 1.5.1, 4.8.0-54-generic, x86_64: installed
 tuxedo-wmi, 1.5.1, 4.8.0-56-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:2425]
InstallationDate: Installed on 2017-02-23 (1549 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook N24_25JU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=UUID=5a0e0583-d0c9-43e4-9770-c35662d7d7c5 ro quiet splash 
acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: Tag 12345
dmi.board.name: N24_25JU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd06/03/2016:svnNotebook:pnN24_25JU:pvrNotApplicable:rvnNotebook:rnN24_25JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N24_25JU
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun May 23 14:37:53 2021
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial
-- 
low graphic mode
https://bugs.launchpad.net/bugs/1929329
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1929326] [NEW] Bluetooth WH-1000XM3 headphones disconnects and reconnects

2021-05-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

>From time to time, my Sony WH-1000XM3 Bluetooth connected headphones
automatically disconnect, and then a couple of seconds later reconnects.
This started happening after updating Ubuntu from 20.10 to 21.04. This
never happened even once when using Ubuntu 20.10, and the headphones are
not used or paired to any other device. The only device that has had any
changes to it is the computer which is now running Ubuntu 21.04.

It is currently using a custom kernel from https://kernel.ubuntu.com
/~kernel-ppa/mainline/ in an attempt to see if that would mitigate the
problem. It did not. The issue started to happen when the Ubuntu 21.04
system was running its default kernel.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
Uname: Linux 5.12.4-051204-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  per2734 F pulseaudio
 /dev/snd/controlC2:  per2734 F pulseaudio
 /dev/snd/controlC0:  per2734 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun May 23 12:58:22 2021
InstallationDate: Installed on 2018-11-26 (908 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: WH-1000XM3
Symptom_PulseAudioLog:
 maj 23 11:33:04 perdator systemd[1473]: pulseaudio.service: Succeeded.
 maj 23 11:33:14 perdator systemd[1473]: pulseaudio.socket: Succeeded.
 maj 23 12:35:05 perdator dbus-daemon[1151]: [system] Rejected send message, 0 
matched rules; type="method_return", sender=":1.79" (uid=1000 pid=2734 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" 
(uid=0 pid=1147 comm="/usr/lib/bluetooth/bluetoothd ")
 maj 23 12:54:15 perdator dbus-daemon[1151]: [system] Rejected send message, 0 
matched rules; type="method_return", sender=":1.79" (uid=1000 pid=2734 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" 
(uid=0 pid=1147 comm="/usr/lib/bluetooth/bluetoothd ")
Symptom_Type: Sound works for a while, then breaks
Title: [WH-1000XM3, playback] fails after a while
UpgradeStatus: Upgraded to hirsute on 2021-05-10 (13 days ago)
dmi.bios.date: 03/11/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5843
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X470-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5843:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX470-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute
-- 
Bluetooth WH-1000XM3 headphones disconnects and reconnects
https://bugs.launchpad.net/bugs/1929326
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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 1922926] Re: Battery applet not updated after sleep

2021-05-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Battery applet not updated after sleep

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Budgie 21.04.
  On battery, for example, battery says 40%.  Close lid of laptop and then plug 
the laptop into AC.
  Open laptop on AC and applet still says 40% and gives no indication of being 
on AC.  Disconnect AC and reconnect AC no change.  The applet uses Upower to 
respond to battery events. So whatever is feeding Upower isnt being updated 
after a resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: upower 0.99.11-2
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Wed Apr  7 07:17:27 2021
  InstallationDate: Installed on 2020-04-18 (353 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 
(20200417)
  SourcePackage: upower
  UpgradeStatus: Upgraded to hirsute on 2021-03-28 (9 days ago)

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

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


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-21 Thread Launchpad Bug Tracker
This bug was fixed in the package language-selector - 0.212

---
language-selector (0.212) impish; urgency=medium

  * data/pkg_depends:
- Don't pull Fcitx for non-Chinese languages. This is consistent
  with the IM_CONFIG_PREFERRED_RULE variable in
  /etc/default/im-config.
- Pull IBus IMs for Chinese also on Ubuntu Budgie
- Switch to Fcitx 5 for Chinese (LP: #1928360)

 -- Gunnar Hjalmarsson   Fri, 21 May 2021 06:41:05
+0200

** Changed in: language-selector (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  In Progress
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

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


[Touch-packages] [Bug 1929125] Re: lib32z1 cannot be installed on ubuntu 20.04 LTS

2021-05-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  lib32z1 cannot be installed on ubuntu 20.04 LTS

Status in zlib package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 20.04 LTS. When trying to install lib32z1, I get the
  following error:

  The following packages have unmet dependencies:
   lib32z1 : Depends: libc6-i386 (>= 2.4) but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  lib32z1 (https://packages.ubuntu.com/focal/lib32z1) depends on
  libc6-i386 (>= 2.4) but the latest version of libc6-i386 I can find
  for Ubuntu is 2.33 (https://packages.ubuntu.com/impish/libc6-i386)

  Is it possible Ubuntu is asking for a version of a dependency so high
  that it doesn't even exist?

  The reason I'm installing a 32-bit package is it's required for
  Android Studio installation process:
  https://developer.android.com/studio/install#linux

  ---

  apt-cache policy libc6-i386

  libc6-i386:
Installed: (none)
Candidate: 2.31-0ubuntu9.2
Version table:
   2.31-0ubuntu9.2 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   2.31-0ubuntu9 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  apt-cache policy lib32z1

  lib32z1:
Installed: (none)
Candidate: 1:1.2.11.dfsg-2ubuntu1.2
Version table:
   1:1.2.11.dfsg-2ubuntu1.2 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   1:1.2.11.dfsg-2ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  lsb_release -rd

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

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

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


[Touch-packages] [Bug 1910273] Re: Upgrade to groovy breaks DNS resolution

2021-05-21 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1907878 ***
https://bugs.launchpad.net/bugs/1907878

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

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

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

Title:
  Upgrade to groovy breaks DNS resolution

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  ~# lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10
  ~# apt-cache policy ifupdown
  ifupdown:
Instalēts: 0.8.35ubuntu2
Kandidāts: 0.8.35ubuntu2
Versiju tabula:
   *** 0.8.35ubuntu2 500
  500 http://mirrors.digitalocean.com/ubuntu groovy/universe amd64 
Packages
  100 /var/lib/dpkg/status
  ~#

  Problem: Upon upgrade from Ubuntu 20.04 to Ubuntu 20.10, I expected
  name resolution upon reboot to work as usual.

  What happened:
  a) /var/log/syslog sprinkled with error messages:
  - /etc/network/if-up.d/resolved: 12: mystatedir: not found
  - /etc/network/if-up.d/resolved: 70: DNS: not found
  - /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-eth0: 
DNS=8.8.8.8 8.8.4.4: not found
  b) resolvectl dns returning no name servers

  Investigation:
  Recently changed /etc/network/if-up.d/resolved and 
/etc/network/if-down.d/resolved files contain programming errors. See 
https://git.launchpad.net/ubuntu/+source/ifupdown/commit/?id=54fec5eedfd59adaffe9021c271914578dd05d1b
 .

  Fix:
  $ diff 
/Users/pklavins/Downloads/ifupdown-0.8.35ubuntu2/debian/if-down.d/resolved 
if-down.d_resolved 
  12c12
  < mystatedir statedir ifindex interface
  ---
  > # local mystatedir statedir ifindex interface
  $ diff 
/Users/pklavins/Downloads/ifupdown-0.8.35ubuntu2/debian/if-up.d/resolved 
if-up.d_resolved 
  12c12
  < mystatedir statedir ifindex interface
  ---
  > # local mystatedir statedir ifindex interface
  39,40c39,40
  < DNS=DNS
  < DOMAINS=DOMAINS
  ---
  > DNS=$DNS
  > DOMAINS=$DOMAINS
  42,43c42,43
  < DNS=DNS6
  < DOMAINS=DOMAINS6
  ---
  > DNS=$DNS6
  > DOMAINS=$DOMAINS6
  47c47
  < "$DNS"="$NEW_DNS"
  ---
  > DNS="$NEW_DNS"
  51c51
  < "$DOMAINS"="$NEW_DOMAINS"
  ---
  > DOMAINS="$NEW_DOMAINS"
  70c70
  < DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
  ---
  > # local DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
  $

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

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


[Touch-packages] [Bug 1929115] [NEW] Video playback on all browsers lags in HD (720p and above)

2021-05-20 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I recently installed ubuntu 20.04 GNOME and noticed that video playback
lags with resolution above and equal to 720p. The video lags the audio
and frame rate drops (seemingly from 30/60 fps to around 10 fps). In
standard definition , there are no such frame drops.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 20 23:33:47 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Picasso [103c:86fd]
InstallationDate: Installed on 2021-05-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: HP HP Laptop 15s-eq0xxx
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=a41f5b2f-9502-402d-b248-2803c0503b41 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/03/2020
dmi.bios.release: 15.22
dmi.bios.vendor: AMI
dmi.bios.version: F.22
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86FD
dmi.board.vendor: HP
dmi.board.version: 99.39
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 99.39
dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd07/03/2020:br15.22:efr99.39:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.39:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15s-eq0xxx
dmi.product.sku: 9VV61PA#ACJ
dmi.sys.vendor: HP
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.2~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 performance ubuntu
-- 
Video playback on all browsers lags in HD (720p and above)
https://bugs.launchpad.net/bugs/1929115
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies

2021-05-20 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 2.3.5

---
apt (2.3.5) experimental; urgency=medium

  * policy: Apply phasing to uninstalled packages too (LP: #1925745)

 -- Julian Andres Klode   Mon, 17 May 2021 11:43:23
+0200

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

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

Title:
  Hirsute: Cannot install ubuntu-desktop due to unmet dependencies

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Confirmed
Status in apt source package in Impish:
  Fix Released

Bug description:
  I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute
  desktop machines so I can automate the installation.

  After installation, I'm trying to install the desktop via "apt install
  ubuntu-desktop".

  This fails with:
  "Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 
1:21.04.11) but 1:21.04.10 is to be installed
 Depends: python3-distupgrade (= 1:21.04.11) 
but 1:21.04.10 is to be installed
  E: Unable to correct problems, you have held broken packages."

  "apt policy ubuntu-release-upgrader-core" shows:
  "ubuntu-release-upgrader-core:
Installed: 1:21.04.10
Candidate: 1:21.04.10
Version table:
   1:21.04.11 1 (phased 20%)
  500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:21.04.10 500
  500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status"

  
  I could not find any information what "phased 20%" means. It's obviously a 
major problem not being able to install the desktop on a fresh installation.

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

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


[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix

2021-05-20 Thread Launchpad Bug Tracker
This bug was fixed in the package pam - 1.3.1-5ubuntu7

---
pam (1.3.1-5ubuntu7) impish; urgency=medium

  * Backport pam_faillock module from pam 1.4.0 (LP: #1927796)
- debian/patches-applied/add_pam_faillock.patch: add module.
- debian/patches-applied/pam_faillock_create_directory: create dir
  before creating file in modules/pam_faillock/faillock.c.
- debian/rules: set execute permissions on pam_faillock test.
- debian/libpam-modules-bin.install: install faillock binary and man
  page.

 -- Richard Maciel Costa   Thu, 08
Apr 2021 07:06:27 -0400

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

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

Title:
  [SRU]pam_tally2 can cause accounts to be locked by correct password.
  pam_faillock use is the recommended fix

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

Bug description:
  [IMPACT]
  There is a known issue in pam_tally2 which may cause an account to be lock 
down even with correct password, in a busy node environment where simultaneous 
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).

  There are already two customer cases from Canonical clients
  complaining about this behavior (00297697 and 00303806).

  Also, potentially, this will cause further problems in the future,
  since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to
  lock accounts when wrong passwords are used. And both benchmarks - but
  specially STIG - requires use of a lot of audit rules, which can lead
  to the busy node environment.

  The issue impacts all pam_tally2 versions distributed in all currently
  supported Ubuntu versions and also the next unreleased one. Note that,
  according to https://github.com/linux-pam/linux-pam/issues/71, there
  is no plan to fix this issue!

  [FIX]
  This fix proposes to add pam_faillock module to the PAM package, so users of 
pam_tally2 having issues can migrate to pam_faillock. We also plan to modify 
the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but 
in order to do so, we need the pam_faillock module to be available.

  Note that we don't propose to remove pam_tally2, since not every user
  of this module is affected.

  [TEST]
  Tested on a VM installed with Focal server iso and on another with Bionic 
server iso. Enabled pam_faillock module as recommeded by its man page. Then 
tried to log over ssh with an incorrect password, until the account got locked. 
Waited for the configured grace time to unlock and logged in using the correct 
password.

  Note that, since the pam_tally2 issue is caused by a racing condition,
  with a hard to recreate environment (we could not even reproduce it
  with pam_tally2), we could not reproduce the conditions to test
  pam_faillock with.

  [REGRESSION POTENTIAL]
  The regression potential for this is small, since we're not removing the old 
pam_tally2 module, just adding another one. So anyone still using pam_tally2 
will be able to do so.

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

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


[Touch-packages] [Bug 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)

2021-05-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Switch to "unified" cgroup hierarchy (cgroupv2)

Status in lxc:
  Fix Released
Status in lxd:
  Fix Released
Status in snapd:
  Confirmed
Status in docker.io package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed
Status in lxc package in Debian:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Systemd upstream switched the default cgroup hierarchy to unified with
  v243. This change is reverted by the Ubuntu systemd packages, but as
  unified is the way to go per upstream support should be added to all
  relevant Ubuntu packges (and snaps):

  https://github.com/systemd/systemd/blob/v243/NEWS#L56

  * systemd now defaults to the "unified" cgroup hierarchy setup during
build-time, i.e. -Ddefault-hierarchy=unified is now the build-time
default. Previously, -Ddefault-hierarchy=hybrid was the default. 
This
change reflects the fact that cgroupsv2 support has matured
substantially in both systemd and in the kernel, and is clearly the
way forward. Downstream production distributions might want to
continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for
their builds as unfortunately the popular container managers have 
not
caught up with the kernel API changes.

  
  Systemd is rebuilt using the new default and is available from the following 
PPA for testing:

  https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh

  The autopkgtest results against other packges are available here:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain

  lxc autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

  snapd autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz

  
  docker.io autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

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

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


[Touch-packages] [Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.1.1f-1ubuntu4.4

---
openssl (1.1.1f-1ubuntu4.4) groovy; urgency=medium

  * Allow x509 certificates which set basicConstraints=CA:FALSE,pathlen:0
to validate, as it is common on self-signed leaf certificates.
(LP: #1926254)
- d/p/lp-1926254-1-Allow-certificates-with-Basic-Constraints-CA-fa.patch
- d/p/lp-1926254-2-Set-X509_V_ERR_INVALID_EXTENSION-error-for-inva.patch
- d/p/lp-1926254-3-Add-test-cases-for-the-non-CA-certificate-with-.patch
  * Split d/p/pr12272.patch into multiple patchfiles to fix dpkg-source
error when attempting to build a source package, due to pr12272.patch
patching files multiple times within the same patch. (LP: #1927161)
- d/p/lp-1927161-1-x86-Add-endbranch-to-indirect-branch-targets-fo.patch
- d/p/lp-1927161-2-Use-swapcontext-for-Intel-CET.patch
- d/p/lp-1927161-3-x86-Always-generate-note-gnu-property-section-f.patch
- d/p/lp-1927161-4-x86_64-Always-generate-note-gnu-property-sectio.patch
- d/p/lp-1927161-5-x86_64-Add-endbranch-at-function-entries-for-In.patch

 -- Matthew Ruffell   Wed, 05 May 2021
12:13:30 +1200

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

Title:
  x509 Certificate verification fails when
  basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Fix Released
Status in openssl source package in Groovy:
  Fix Released
Status in openssl source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In openssl 1.1.1f, the below commit was merged:

  commit ba4356ae4002a04e28642da60c551877eea804f7
  Author: Bernd Edlinger 
  Date:   Sat Jan 4 15:54:53 2020 +0100
  Subject: Fix error handling in x509v3_cache_extensions and related functions
  Link: 
https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7

  This introduced a regression which caused certificate validation to
  fail when certificates violate RFC 5280 [1], namely, when a
  certificate has "basicConstraints=CA:FALSE,pathlen:0". This
  combination is commonly seen by self-signed leaf certificates with an
  intermediate CA before the root CA.

  Because of this, openssl 1.1.1f rejects these certificates and they
  cannot be used in the system certificate store, and ssl connections
  fail when you try to use them to connect to a ssl endpoint.

  The error you see when you try verify is:

  $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem 
user1_cert.pem
  error 20 at 0 depth lookup: unable to get local issuer certificate
  error user1_cert.pem: verification failed

  The exact same certificates work fine on Xenial, Bionic and Hirsute.

  [1] https://tools.ietf.org/html/rfc5280.html

  [Testcase]

  We will create our own root CA, intermediate CA and leaf server
  certificate.

  Create necessary directories:

  $ mkdir reproducer
  $ cd reproducer
  $ mkdir CA

  Write openssl configuration files to disk for each CA and cert:

  $ cat << EOF >> rootCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Root-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> subCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Sub-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE,pathlen:0
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> user.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test User

  [ usr_cert ]
  basicConstraints= critical,CA:FALSE,pathlen:0
  keyUsage= critical,digitalSignature,keyAgreement
  extendedKeyUsage= clientAuth,serverAuth
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  Then generate the necessary RSA keys and form certificates:

  $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes 
-x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1

  $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config 

[Touch-packages] [Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.1.1f-1ubuntu2.4

---
openssl (1.1.1f-1ubuntu2.4) focal; urgency=medium

  * Allow x509 certificates which set basicConstraints=CA:FALSE,pathlen:0
to validate, as it is common on self-signed leaf certificates.
(LP: #1926254)
- d/p/lp-1926254-1-Allow-certificates-with-Basic-Constraints-CA-fa.patch
- d/p/lp-1926254-2-Set-X509_V_ERR_INVALID_EXTENSION-error-for-inva.patch
- d/p/lp-1926254-3-Add-test-cases-for-the-non-CA-certificate-with-.patch

 -- Matthew Ruffell   Wed, 28 Apr 2021
12:37:28 +1200

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

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

Title:
  x509 Certificate verification fails when
  basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Fix Released
Status in openssl source package in Groovy:
  Fix Released
Status in openssl source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In openssl 1.1.1f, the below commit was merged:

  commit ba4356ae4002a04e28642da60c551877eea804f7
  Author: Bernd Edlinger 
  Date:   Sat Jan 4 15:54:53 2020 +0100
  Subject: Fix error handling in x509v3_cache_extensions and related functions
  Link: 
https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7

  This introduced a regression which caused certificate validation to
  fail when certificates violate RFC 5280 [1], namely, when a
  certificate has "basicConstraints=CA:FALSE,pathlen:0". This
  combination is commonly seen by self-signed leaf certificates with an
  intermediate CA before the root CA.

  Because of this, openssl 1.1.1f rejects these certificates and they
  cannot be used in the system certificate store, and ssl connections
  fail when you try to use them to connect to a ssl endpoint.

  The error you see when you try verify is:

  $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem 
user1_cert.pem
  error 20 at 0 depth lookup: unable to get local issuer certificate
  error user1_cert.pem: verification failed

  The exact same certificates work fine on Xenial, Bionic and Hirsute.

  [1] https://tools.ietf.org/html/rfc5280.html

  [Testcase]

  We will create our own root CA, intermediate CA and leaf server
  certificate.

  Create necessary directories:

  $ mkdir reproducer
  $ cd reproducer
  $ mkdir CA

  Write openssl configuration files to disk for each CA and cert:

  $ cat << EOF >> rootCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Root-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> subCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Sub-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE,pathlen:0
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> user.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test User

  [ usr_cert ]
  basicConstraints= critical,CA:FALSE,pathlen:0
  keyUsage= critical,digitalSignature,keyAgreement
  extendedKeyUsage= clientAuth,serverAuth
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  Then generate the necessary RSA keys and form certificates:

  $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes 
-x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1

  $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem 
-sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey 
rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt 
-CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ c_rehash CA

  $ openssl genpkey 

[Touch-packages] [Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.1.1f-1ubuntu4.4

---
openssl (1.1.1f-1ubuntu4.4) groovy; urgency=medium

  * Allow x509 certificates which set basicConstraints=CA:FALSE,pathlen:0
to validate, as it is common on self-signed leaf certificates.
(LP: #1926254)
- d/p/lp-1926254-1-Allow-certificates-with-Basic-Constraints-CA-fa.patch
- d/p/lp-1926254-2-Set-X509_V_ERR_INVALID_EXTENSION-error-for-inva.patch
- d/p/lp-1926254-3-Add-test-cases-for-the-non-CA-certificate-with-.patch
  * Split d/p/pr12272.patch into multiple patchfiles to fix dpkg-source
error when attempting to build a source package, due to pr12272.patch
patching files multiple times within the same patch. (LP: #1927161)
- d/p/lp-1927161-1-x86-Add-endbranch-to-indirect-branch-targets-fo.patch
- d/p/lp-1927161-2-Use-swapcontext-for-Intel-CET.patch
- d/p/lp-1927161-3-x86-Always-generate-note-gnu-property-section-f.patch
- d/p/lp-1927161-4-x86_64-Always-generate-note-gnu-property-sectio.patch
- d/p/lp-1927161-5-x86_64-Add-endbranch-at-function-entries-for-In.patch

 -- Matthew Ruffell   Wed, 05 May 2021
12:13:30 +1200

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

Title:
  dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch'
  patches files multiple times; split the diff in multiple files or
  merge the hunks into a single one

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Groovy:
  Fix Released
Status in openssl source package in Hirsute:
  Fix Committed
Status in openssl source package in Impish:
  Fix Released

Bug description:
  [impact]

  openssl doesn't build source properly because of a badly-constructed
  patch

  [test case]

  $ pull-lp-source openssl groovy
  ...
  $ cd openssl-1.1.1f/
  $ quilt pop -a
  ...
  $ dpkg-buildpackage -d -S
  dpkg-buildpackage: info: source package openssl
  dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3
  dpkg-buildpackage: info: source distribution groovy-security
  dpkg-buildpackage: info: source changed by Marc Deslauriers 

   dpkg-source --before-build .
  dpkg-source: warning: can't parse dependency perl:native
  dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' 
patches files multiple times; split the diff in multiple files or merge the 
hunks into a single one
  dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned 
exit status 25

  Test builds are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test

  [regression potential]

  any regression would likely cause a failed build or would affect the
  functionality that patch pr12272 was added for, which is adding
  support for Intel CET

  [scope]

  this is needed only for g and later

  this is caused by the bad patch 'pr12272.patch' which is only included
  in g/h/i, so this does not apply to f or earlier

  [other info]

  note that if the patches are applied, this bug is bypassed; i.e. if
  'quilt pop -a' is removed from the test case above, the bug doesn't
  reproduce. this is only a problem when the patches aren't already
  applied and dpkg-buildpackage needs to call dpkg-source to apply the
  patches.

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.9

---
zfs-linux (0.8.3-1ubuntu12.9) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:09:45
+0100

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

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package virtualbox -
6.1.16-dfsg-6~ubuntu1.20.04.2

---
virtualbox (6.1.16-dfsg-6~ubuntu1.20.04.2) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:42:15
+0100

** Changed in: virtualbox-hwe (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package r8168 - 8.048.00-1ubuntu0.20.04.2

---
r8168 (8.048.00-1ubuntu0.20.04.2) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:08:42
+0100

** Changed in: rtl8812au (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package v4l2loopback - 0.12.3-1ubuntu0.4

---
v4l2loopback (0.12.3-1ubuntu0.4) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:09:12
+0100

** Changed in: virtualbox (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package lttng-modules -
2.12.2-1ubuntu1~20.04.2

---
lttng-modules (2.12.2-1ubuntu1~20.04.2) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:08:09
+0100

** Changed in: nvidia-graphics-drivers-340 (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package virtualbox-hwe - 6.1.16-dfsg-
6ubuntu1.20.04.2

---
virtualbox-hwe (6.1.16-dfsg-6ubuntu1.20.04.2) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:06:25
+0100

** Changed in: zfs-linux (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package iptables-netflow - 2.4-2ubuntu0.4

---
iptables-netflow (2.4-2ubuntu0.4) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:07:51
+0100

** Changed in: liblzf (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package rtl8812au - 4.3.8.12175.20140902+dfsg-
0ubuntu13~20.04.2

---
rtl8812au (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:08:52
+0100

** Changed in: sysdig (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package sysdig - 0.26.4-1ubuntu0.3

---
sysdig (0.26.4-1ubuntu0.3) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:09:03
+0100

** Changed in: v4l2loopback (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-
0ubuntu7~20.04.2

---
bcmwl (6.30.223.271+bdcom-0ubuntu7~20.04.2) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:05:27
+0100

** Changed in: dahdi-linux (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package oss4 - 4.2-build2010-5ubuntu6~20.04.2

---
oss4 (4.2-build2010-5ubuntu6~20.04.2) focal; urgency=medium

  * No change rebuild in security pocket. LP: #1914279.

 -- Dimitri John Ledkov   Thu, 29 Apr 2021 16:08:32
+0100

** Changed in: r8168 (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


  1   2   3   4   5   6   7   8   9   10   >