date:20230601

This bug was fixed in the package network-manager - 1.42.4-1ubuntu5

---
network-manager (1.42.4-1ubuntu5) mantic; urgency=medium

  * d/network-manager.postinst: fix netplan migration logic.
The "continue" is being executed in a subshell so it's not skipping the
next commands. It will fail if Network Manager is not running. See LP: 
#2022023
  * d/network-manager.preinst: use /var/lib/NetworkManager for backups
/root is not a system directory so we shouldn't use it. It might not
even exist or the package manager might run in a sandbox and not have
access to it. See LP: #2021937

 -- Danilo Egea Gondolfo   Thu, 01
Jun 2023 15:17:57 +0100

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

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

Title:
  preinst writes to /root

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  As part of my sandboxed APT I noticed that the package failed to
  install as it was trying to write to /root.

  /root is a user directory, not a system one, which may not even exist
  because the administrator changed it to like /home/root, for example,
  and we definitely should not be writing system files in user
  directories.

  Preparing to unpack .../16-network-manager_1.42.4-1ubuntu4_amd64.deb ...  
 
  mkdir: cannot create directory ‘/root/NetworkManager.bak’: Read-only file 
system
  cp: cannot create directory 
'/root/NetworkManager.bak/system-connections_1.42.4-1ubuntu2': No such file or 
directory
  dpkg: error processing archive 
/tmp/apt-dpkg-install-x9x0Qo/16-network-manager_1.42.4-1ubuntu4_amd64.deb 
(--unpack):
   new network-manager package pre-installation script subprocess returned 
error exit status 1

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


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

[Touch-packages] [Bug 2022023] Re: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 8

This bug was fixed in the package network-manager - 1.42.4-1ubuntu5

---
network-manager (1.42.4-1ubuntu5) mantic; urgency=medium

  * d/network-manager.postinst: fix netplan migration logic.
The "continue" is being executed in a subshell so it's not skipping the
next commands. It will fail if Network Manager is not running. See LP: 
#2022023
  * d/network-manager.preinst: use /var/lib/NetworkManager for backups
/root is not a system directory so we shouldn't use it. It might not
even exist or the package manager might run in a sandbox and not have
access to it. See LP: #2021937

 -- Danilo Egea Gondolfo   Thu, 01
Jun 2023 15:17:57 +0100

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

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

Title:
  package network-manager 1.42.4-1ubuntu4 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 8

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I am using netplan for my network config.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.4-1ubuntu4
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Thu Jun  1 12:05:16 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 8
  InstallationDate: Installed on 2020-04-25 (1131 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IpRoute:
   default via 192.168.56.1 dev enp7s0 proto static 
   192.168.56.0/30 dev enp7s0 proto kernel scope link src 192.168.56.2
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.3, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.22ubuntu1
   apt  2.7.0
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 8
  UpgradeStatus: Upgraded to mantic on 2023-06-01 (0 days ago)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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


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

[Touch-packages] [Bug 2021484] Re: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway

2023-06-01 Thread Seth Arnold

Hello Cristobal, can you make changes from that interface? Or is it
read-only?

Thanks

** Information type changed from Private Security to Public Security

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

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

Title:
  Editing a VPN ask to introduce credentials but if you cancel can be
  accessed anyway

Status in ubuntu-settings package in Ubuntu:
  Incomplete

Bug description:
  I'm logged as a normal user without admin privileges. When I try to
  edit a VPN I'm asked to introduce the credentials of the admin,
  nevertheless if I click cancel I can still access to the VPN
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-settings 20.04.6
  ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 29 11:16:38 2023
  InstallationDate: Installed on 2022-05-04 (389 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2022107] Re: printing dubugging doesnt work!

2023-06-01 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  printing dubugging doesnt work!

Status in cups package in Ubuntu:
  New

Bug description:
  1  cupsdisable OKI-C332-411ACB 
  cupsdisable: Operation failed: client-error-not-found

  2   wget http://people.canonical.com/~pitti/tmp/cups.upstart.debug
  --2023-06-01 21:57:49--  
http://people.canonical.com/~pitti/tmp/cups.upstart.debug
  Resolving people.canonical.com (people.canonical.com)... 185.125.188.97
  Connecting to people.canonical.com 
(people.canonical.com)|185.125.188.97|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: https://people.canonical.com/~pitti/tmp/cups.upstart.debug 
[following]
  --2023-06-01 21:57:49--  
https://people.canonical.com/~pitti/tmp/cups.upstart.debug
  Connecting to people.canonical.com 
(people.canonical.com)|185.125.188.97|:443... connected.
  HTTP request sent, awaiting response... 403 Forbidden
  2023-06-01 21:57:49 ERROR 403: Forbidden.

  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04

  sudo: aa-complain: command not found

  /usr/lib/cups/backend/snmp
  network socket://192.168.1.201 "OKI DATA CORP C332" "C332" "MFG:OKI DATA 
CORP;CMD:PCL,XPS,IBMPPR,EPSONFX,POSTSCRIPT,PDF,PCLXL,HIPERMIP,URF;MDL:C332;CLS:PRINTER;DES:OKI
 C332;CID:OK_N_B800;" ""

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.2
  ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  1 21:59:57 2023
  InstallationDate: Installed on 2023-04-25 (37 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Lpstat: device for OKI_C332_411ACB@oki-c332-411acb.local: 
implicitclass://OKI_C332_411ACB%40oki-c332-411acb.local/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 3151:3020 YICHIP Wireless Device
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Novatech N150ZU
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-72-generic 
root=UUID=2c0e4998-ac9a-4c3c-ab96-b2b45fe5eab7 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TNO
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150ZU
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TNO:bd06/24/2019:br7.7:efr7.4:svnNovatech:pnN150ZU:pvrNotApplicable:rvnNovatech:rnN150ZU:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

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


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

[Touch-packages] [Bug 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1

2023-06-01 Thread Seth Arnold

Am I reading the ps faux output from comment #5 correctly, that
needrestart is responsible for starting a dpkg process that starts a
debconf frontend, but there's no terminal available to this process?

Why is needrestart doing operations that would need a debconf frontend?
Should it be doing them, or is it a surprise? Should it be setting the
frontend non-interactive environment variable? Or should it stop doing
the dpkg operations?

Or, did I misread the thing?

Thanks

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

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

Title:
  package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade:
  installed libssl3:amd64 package post-installation script subprocess
  returned error exit status 1

Status in needrestart package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  encounter error when attempting to do sudo update, upgrade, and full-
  upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libssl3:amd64 3.0.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  1 10:28:26 2023
  ErrorMessage: installed libssl3:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-01 (150 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: openssl
  Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: 
installed libssl3:amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2019986] Re: package openjdk-17-jre-headless:amd64 17.0.7+7~us1-0ubuntu1~22.04.2 failed to install/upgrade: end of file on stdin at conffile prompt

2023-06-01 Thread Vladimir Petko

I was not able to reproduce the issue during testing following steps:
- disable updates and security
- install openjdk-17-jdk
- update configuration files
- enable updates and security
- run unattended upgrades

The package is not updated

** Changed in: openjdk-17 (Ubuntu)
   Status: New => Invalid

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Incomplete

** Changed in: openjdk-17 (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  package openjdk-17-jre-headless:amd64 17.0.7+7~us1-0ubuntu1~22.04.2
  failed to install/upgrade: end of file on stdin at conffile prompt

Status in openjdk-17 package in Ubuntu:
  Incomplete
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Crash occurred first thing in the morning, before any interaction.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: openjdk-17-jre-headless:amd64 17.0.7+7~us1-0ubuntu1~22.04.2
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  AptOrdering:
   openjdk-17-jdk:amd64: Install
   openjdk-17-jdk-headless:amd64: Install
   openjdk-17-jre:amd64: Install
   openjdk-17-jre-headless:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed May 17 06:23:45 2023
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2022-05-21 (360 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.9
  SourcePackage: openjdk-17
  Title: package openjdk-17-jre-headless:amd64 17.0.7+7~us1-0ubuntu1~22.04.2 
failed to install/upgrade: end of file on stdin at conffile prompt
  UpgradeStatus: Upgraded to jammy on 2022-08-31 (258 days ago)
  modified.conffile..etc.java-17-openjdk.jvm-amd64.cfg:
   -server KNOWN
   -client IGNORE
   -zero KNOWN
   -dcevm KNOWN
  modified.conffile..etc.java-17-openjdk.security.blocked.certs: [modified]
  modified.conffile..etc.java-17-openjdk.security.default.policy: [modified]
  modified.conffile..etc.java-17-openjdk.security.java.policy: [modified]
  modified.conffile..etc.java-17-openjdk.security.java.security: [modified]
  modified.conffile..etc.java-17-openjdk.security.nss.cfg:
   name = NSS
   nssDbMode = noDb
   attributes = compatibility
   handleStartupErrors = ignoreMultipleInitialisation
  modified.conffile..etc.java-17-openjdk.swing.properties:
   # uncomment to set the default look and feel to GTK
   #swing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel
  mtime.conffile..etc.java-17-openjdk.jfr.default.jfc: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.jfr.profile.jfc: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.jvm-amd64.cfg: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.logging.properties: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.management.jmxremote.access: 
2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.management.management.properties: 
2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.net.properties: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.psfont.properties.ja: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.psfontj2d.properties: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.security.blocked.certs: 
2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.security.default.policy: 
2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.security.java.policy: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.security.java.security: 
2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.security.nss.cfg: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.security.policy.README.txt: 
2023-01-20T00:56:27
  
mtime.conffile..etc.java-17-openjdk.security.policy.limited.default_US_export.policy:
 2023-01-20T00:56:27
  
mtime.conffile..etc.java-17-openjdk.security.policy.limited.default_local.policy:
 2023-01-20T00:56:27
  
mtime.conffile..etc.java-17-openjdk.security.policy.limited.exempt_local.policy:
 2023-01-20T00:56:27
  
mtime.conffile..etc.java-17-openjdk.security.policy.unlimited.default_US_export.policy:
 2023-01-20T00:56:27
  
mtime.conffile..etc.java-17-openjdk.security.policy.unlimited.default_local.policy:
 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.security.public_suffix_list.dat: 
2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.sound.properties: 2023-01-20T00:56:27
  mtime.conffile..etc.java-17-openjdk.swing.properties: 2023-01-17T14:28:11

To manage notifications about this bug go to:

[Touch-packages] [Bug 2020838] Re: [regression][jammy] augenrules Error sending add rule data request (No such file or directory)

2023-06-01 Thread Seth Arnold

Awesome find! Probably for many users, that's a perfectly fine change, I
suspect that auditing home directories isn't going to be a top priority
for many people.

However, the sheer confusion of this issue is troubling: going from
these error messages to "I have to remove a systemd configuration
directive" is a big leap. At least now there's a bug report on the
internet with both the error message and the solution, so the next
person will have an easier time of it, but it probably will still only
come after frustration.

But I'm leery of removing hardening options. Opinions from the wider
world?

Thanks

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

Title:
  [regression][jammy] augenrules Error sending add rule data request (No
  such file or directory)

Status in audit package in Ubuntu:
  New

Bug description:
  The rule '-a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F
  auid>=1000 -F auid!=unset -k privileged' can not be loaded during
  system boot up.

  # lsb_release -rc
  Release:  22.04
  Codename: jammy

  # dpkg -l|grep audit
  ii  auditd  1:3.0.7-1build1 
amd64User space tools for security auditing
  ii  libaudit-common 1:3.0.7-1build1 
all  Dynamic library for security auditing - common files
  ii  libaudit1:amd64 1:3.0.7-1build1 
amd64Dynamic library for security auditing
  ii  libauparse0:amd64   1:3.0.7-1build1 
amd64Dynamic library for parsing security auditing

  # cat /etc/audit/rules.d/audit.rules|grep -v ^#|grep -v ^$
  -D
  -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F 
auid!=unset -k privileged
  -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts
  -b 8192
  --backlog_wait_time 6
  -f 1

  # ls -l /home/ubuntu/test.sh 
  -rwxr-xr-x 1 root ubuntu 19 May 25 14:19 /home/ubuntu/test.sh

  # cat /home/ubuntu/test.sh
  #!/bin/bash
  echo 1

  
  # >/etc/audit/audit.rules

  reboot the system, no rule can be loaded

  # auditctl -l
  No rules

  syslog:

  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: Error sending add rule 
data request (No such file or directory)
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: There was an error in 
line 5 of /etc/audit/audit.rules
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: No rules
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0

  # cat /etc/audit/audit.rules
  ## This file is automatically generated from /etc/audit/rules.d
  -D
  -b 8192
  -f 1
  -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F 
auid!=unset -k privileged
  -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts
  --backlog_wait_time 6

  But I can manually load the rule file. Seems this issue only happen
  during system boot up.

  # auditctl -R /etc/audit/audit.rules
  No rules
  enabled 1
  failure 1
  pid 476
  rate_limit 0
  backlog_limit 8192
  lost 0
  backlog 4
  backlog_wait_time 15000
  backlog_wait_time_actual 0
  enabled 1
  failure 1
  pid 476
  rate_limit 0
  backlog_limit 8192
  lost 0
  backlog 4
  backlog_wait_time 15000
  backlog_wait_time_actual 0
  enabled 1
  failure 1
  pid 476
  rate_limit 0
  backlog_limit 8192
  lost 0
  backlog 14
  backlog_wait_time 6
  backlog_wait_time_actual 0

  # auditctl -l
  -a always,exit -S all -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F 
auid!=-1 -F key=privileged
  -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=-1 -F key=mounts

  If I move the file /home/ubuntu/test.sh

[Touch-packages] [Bug 589496] Re: bash --rcfile does not behave as documented

2023-06-01 Thread Michael McNeil Forbes

My use case: I want to be able to spawn a clean shell with a customized
development environment (python) from a Makefile  (i.e. `make shell`
runs `bash --init-file .init_file.bash` which does not inherit cruft
from the environment (such as activated conda environments, PATHs etc.)

```
shell:
bash --init-file .init_file.bash
```

This worked fine until I started trying to use this on Debian-based
systems with -DSYS_BASHRC where, sometimes, admins activate a conda
environment for all users by default.

So, no admin access in the typical case.  Now a user can do this by
running `bash --norc` then manually sourcing `.init_file.bash` from that
shell.

How do I achieve this effect from my Makefile?  This is what I would
have expected `bash --norc --init-file .init_file.bash` but that is not
what bash does.  I tend to agree that ignoring `--rcfile` flag behaviour
with `--norc` is the error... but it looks like that is not going to
change.

So what do I do?  That non-admins are "not supposed to be able to bypass
it" seems moot, since they can with `--norc`. Am I missing something?

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

Title:
  bash --rcfile does not behave as documented

Status in bash package in Ubuntu:
  Confirmed
Status in bash package in Debian:
  New

Bug description:
  Binary package hint: bash

  the bash manpage says this about --rcfile

  --rcfile file
  Execute commands from file instead of the system  wide  initial‐
  ization file /etc/bash.bashrc and the standard personal initial‐
  ization file ~/.bashrc if the shell is interactive (see  INVOCA‐
  TION below).

  under INVOCATION it says

  When  an  interactive  shell that is not a login shell is started, bash
  reads and executes commands from  /etc/bash.bashrc  and  ~/.bashrc,  if
  these  files  exist.  This may be inhibited by using the --norc option.
  The --rcfile file option will force bash to read and  execute  commands
  from file instead of /etc/bash.bashrc and ~/.bashrc.

  but when i execute
  $ bash --rcfile somercfilewhichreallydoesexistandisreadableandall
  it will still read /etc/bash/bashrc (can be verified by adding --verbose)

  using lucid with bash 4.1-2ubuntu3

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


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

[Touch-packages] [Bug 2021929] Re: upgrade to exiv2 0.28.0

2023-06-01 Thread Hans Joachim Desserud

** Tags added: upgrade-software-version

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

Title:
  upgrade to exiv2 0.28.0

Status in exiv2 package in Ubuntu:
  New

Bug description:
  The latest release is 0.28.0 and fixes some bugs I've encountered

  https://github.com/Exiv2/exiv2/releases/tag/v0.28.0

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


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

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

2023-06-01 Thread Graeme Hewson

CUPS 2.4.3 has been released, which should fix this problem.

https://github.com/OpenPrinting/cups/releases/tag/v2.4.3

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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

[Touch-packages] [Bug 2012943] Re: systemd-resolved crashes due to use-after-free bug

2023-06-01 Thread Nick Rosbrook

I agree that the remaining failures look unrelated to this systemd
update, and they should be hinted:

fwupd/1.7.9-1~20.04.1 armhf: This is a known issue (bug 1994143) and is 
addressed by a fwupd upload in focal-proposed.
linux-azure-5.15/5.15.0-1039.46~20.04.1 amd64, 
linux-lowlatency-hwe-5.15/5.15.0-73.80~20.04.1 arm64: These are failing with 
badpkg[1][2], which appears to be caused by toolchain dependency issues.

[1] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/linux-lowlatency-hwe-5.15/20230531_172319_82f87@/log.gz
[2] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/linux-azure-5.15/20230531_140824_1120e@/log.gz

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

Title:
  systemd-resolved crashes due to use-after-free bug

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

Bug description:
  [ Impact ]

  The continuous systemd-resolved crashes delay/hang the device startup.
  And this leads to unresponsive devices in the system. Specifically, the crash 
looks like:

  Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service.
  Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main 
process exited, code=killed, status=11/SEGV
  [...]
  Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting.
  Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main 
process exited, code=killed, status=6/ABRT

  [ Test Plan ]

  The exact steps to reproduce this issue are still not known.
  But we see this crash only in Static IP Addressing mode enabled, where 
systemd-resolved is enabled for LLMNR service.
  But we were not able to see this crash in DHCP mode.

  Steps to reproduce:
  1) Powercycle the device.
  2) Soft-reboot.

  It was also pointed out by Brian Murray that this error in the Ubuntu
  error tracker is likely the same bug:
  https://errors.ubuntu.com/problem/3cb08ae5efaa4d8c6ce992f7cebd2751ae3f168f.
  Therefore, we would expect to stop seeing this error in the tracker as
  a result of this patch.

  [ Where problems could occur ]

  The patch[1] simply disables the timer event source for a DNS query
  when the struct representing that query is free'd. I cannot see any
  realistic regression potential, because if the timer event fired on
  the DNS query after it has been free'd, then that would be this bug.
  I.e. no working code should be relying on the timer event source still
  being around after the query is free'd.

  [1]
  
https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b

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


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

[Touch-packages] [Bug 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created

2023-06-01 Thread Simon Déziel

@slyon I saw that https://git.launchpad.net/network-
manager/commit/?h=netplan/lunar-
gu=900b2e15bce37363b263a224e60674f804114693 requires the `file`
package to be available. Some systems don't have installed, albeit
probably not common on desktops but I though I'd mention just in case.

That same commit also seem to have a bogus error handling if `nm-online
-qs` fails:

```
nm-online -qs || (echo "SKIP: NetworkManager is not ready ..." 1>&2 && continue)
```

The `continue` will be run in the `()` subshell. I think this could be
fixed by using `{}` instead.

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

Title:
The Netplan Everywhere NetworkManager fails to supply Netplan with
networking information until a connection is deleted and re-created

Status in netplan:
Invalid
Status in network-manager package in Ubuntu:
Fix Released

Bug description:
Steps to reproduce:

1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a
WiFi adapter. (I used Lubuntu Lunar.)
2. Connect to WiFi and install all updates.
3. Enable the Netplan Everywhere PPA and install the updated NetworkManager
from it (further details at
https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3)
4. When the installation finishes, run "sudo netplan get".

Expected result: Networking information related to the WiFi connection
should appear in the "sudo netplan get" output.

Actual result: "sudo netplan get" returns the following:

** (process:4088): WARNING **: 12:41:41.394; Permissions for
/etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration
should NOT be accessible by others.
network:
version: 2
renderer: NetworkManager

End of output. Additionally, the /etc/netplan folder does not contain
files that I would expect to be there that would contain the
networking info.

Additional information:

If I disconnect from WiFi, then delete my WiFi connection entirely in
nmtui, and *then* reconnect to the same WiFi network, "sudo netplan
get" returns the expected networking information. /etc/netplan is also
properly populated after doing this.

This bug seems like it will probably cause unintended behavior after
an upgrade from 23.04 (which uses normal NetworkManager) to 23.10
(which is supposed to be using the Netplan Everywhere NetworkManager).
People probably won't know to entirely delete the WiFi and other
connections and then reconnect them in order for the netplan output to
be usable.

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2023-06-01 Thread Jeremy Bícha

** Changed in: slang2 (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: rasqal (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: nginx (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Fix Released
Status in anope package in Ubuntu:
  Fix Released
Status in apache2 package in Ubuntu:
  Fix Released
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Fix Released
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in grep package in Ubuntu:
  Fix Released
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Fix Released
Status in nginx package in Ubuntu:
  Fix Released
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Fix Released
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Fix Released
Status in python-pyscss package in Ubuntu:
  Fix Released
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Fix Released
Status in slang2 package in Ubuntu:
  Fix Released
Status in sssd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in tilix package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Incomplete
Status in postfix package in Debian:
  Fix Released
Status in zsh package in Debian:
  Confirmed

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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


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

[Touch-packages] [Bug 2022023] Re: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 8

** Merge proposal linked:
   
https://code.launchpad.net/~danilogondolfo/network-manager/+git/ubuntu-1/+merge/443876

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

Title:
  package network-manager 1.42.4-1ubuntu4 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 8

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am using netplan for my network config.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.4-1ubuntu4
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Thu Jun  1 12:05:16 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 8
  InstallationDate: Installed on 2020-04-25 (1131 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IpRoute:
   default via 192.168.56.1 dev enp7s0 proto static 
   192.168.56.0/30 dev enp7s0 proto kernel scope link src 192.168.56.2
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.3, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.22ubuntu1
   apt  2.7.0
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 8
  UpgradeStatus: Upgraded to mantic on 2023-06-01 (0 days ago)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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


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

[Touch-packages] [Bug 2022023] Re: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 8

2023-06-01 Thread Danilo Egea Gondolfo

Thanks for your bug report.

This problem seems to be caused by the netplan migration logic in the
postinst script. I'm looking into it.

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

Title:
  package network-manager 1.42.4-1ubuntu4 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 8

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am using netplan for my network config.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.4-1ubuntu4
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Thu Jun  1 12:05:16 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 8
  InstallationDate: Installed on 2020-04-25 (1131 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IpRoute:
   default via 192.168.56.1 dev enp7s0 proto static 
   192.168.56.0/30 dev enp7s0 proto kernel scope link src 192.168.56.2
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.3, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.22ubuntu1
   apt  2.7.0
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 8
  UpgradeStatus: Upgraded to mantic on 2023-06-01 (0 days ago)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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


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

[Touch-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

2023-06-01 Thread sir phobos

it seems that i've managed to update to it before it was pulled from
updates.

I just hope that 2020604 fix won't revert this fix.

choosing between a fix for kwin crash that often leads to the need to
relogin alltoghether, and a fix for minor chromium graphics glitches -
i'd prefer a fix for kwin

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Released
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


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

[Touch-packages] [Bug 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1

2023-06-01 Thread Derek

This is what I got from ps faux | less" and "/frontend.

Do you think is ok to kill the process? I can't think about that update
running, has I always get the same response since 7 days.




root1422  0.0  0.0  15424  7740 ?Ss   Mar30   2:37 sshd: 
/usr/sbin/sshd -D [listener] 0 of 10-100 startups
root 3400080  0.0  0.0  21632 13336 ?Ss   13:04   0:00  \_ sshd: 
root@pts/1
root 3413447  0.0  0.0   9140  5864 pts/1Ss   13:04   0:00  \_ -bash
root 3812617  0.0  0.0  10872  4288 pts/1R+   14:32   0:00  \_ 
ps faux
root 3812618  0.0  0.0   6560  2188 pts/1S+   14:32   0:00  \_ 
grep --color=auto -B 4 -A 1 frontend
root1497  0.0  0.0 107116 15836 ?Ssl  Mar30   0:00 
/usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown 
--wait-for-signal
--
root 1224019  0.0  0.0  13716  2516 ?Ss   Apr24   0:00 
/usr/bin/dpkg --force-confdef --force-confold --status-fd 63 --configure 
--pending
root 1224020  0.0  0.0   2888   880 ?SApr24   0:00  \_ sh -c 
(test -x /usr/lib/needrestart/dpkg-status && /usr/lib/needrestart/dpkg-status 
|| cat > /dev/null)
root 1224021  0.0  0.0   2888 4 ?SApr24   0:00  |   \_ sh 
-c (test -x /usr/lib/needrestart/dpkg-status && 
/usr/lib/needrestart/dpkg-status || cat > /dev/null)
root 1224022  0.0  0.0   2888   848 ?SApr24   0:00  |   \_ 
/bin/sh /usr/lib/needrestart/dpkg-status
root 1224024  1.7  0.0  26288  8432 ?SApr24 988:49  \_ 
/usr/bin/perl -w /usr/share/debconf/frontend 
/var/lib/dpkg/info/grub-efi-amd64-signed.postinst configure 
1.182~22.04.1+2.06-2ubuntu10
root 1224036  0.0  0.0   2888   892 ?SApr24   0:00  \_ 
/bin/sh /var/lib/dpkg/info/grub-efi-amd64-signed.postinst configure 
1.182~22.04.1+2.06-2ubuntu10

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

Title:
  package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade:
  installed libssl3:amd64 package post-installation script subprocess
  returned error exit status 1

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  encounter error when attempting to do sudo update, upgrade, and full-
  upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libssl3:amd64 3.0.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  1 10:28:26 2023
  ErrorMessage: installed libssl3:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-01 (150 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: openssl
  Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: 
installed libssl3:amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2021505] Re: Flaky DEP8 test: saslauthd

2023-06-01 Thread Andreas Hasenack

I have a fix for this.

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

Title:
  Flaky DEP8 test: saslauthd

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 package in Debian:
  New

Bug description:
  It looks like the saslauthd test is a bit flaky, and more so in
  platforms like arm64[1]:

  autopkgtest [15:14:52]: test saslauthd: [---
  Setting up saslauthd with mecanism sasldb
  Authentication of user user1887 with correct password should succeed... FAIL
  exit status: 255
  output:
  connect() : No such file or directory
  0:
  autopkgtest [15:14:53]: test saslauthd: ---]
  autopkgtest [15:14:53]: test saslauthd:  - - - - - - - - - - results - - - - 
- - - - - -
  saslauthdFAIL non-zero exit status 1

  The "connect()" error looks like the saslauthd unix socket isn't ready
  yet. That test happens right after a saslauthd restart:

  echo "Setting up saslauthd with mecanism ${mech}"
  setup_saslauthd ${mech} <--- restart happens here

  # test correct credentials
  echo -n "Authentication of user ${sasluser} with correct password should 
succeed... "
  result=0
  output=$(testsaslauthd -u "${sasluser}" -p "${saslpass}" 2>&1) || 
result=$? <--- this is the authentication test

  Maybe we should loop for a few times in a check for the socket, and if
  it still fails, add extra logging to the output so it can be
  troubleshooted better.

  
  1. https://autopkgtest.ubuntu.com/packages/c/cyrus-sasl2/mantic/arm64

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


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

[Touch-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

2023-06-01 Thread Timo Aaltonen

it was pulled from updates because it caused bug 2020604, and that has a
fix pending on the SRU queue

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Released
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


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

[Touch-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

2023-06-01 Thread Jamie Scott

According to the launchpad page for mesa 22.2.5-0ubuntu0.1~22.04.2
(https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.2)
the package is still in proposed, not updates. @tjaalton 's message in
#72 suggests it has been released to updates but this appears incorrect.

I'm on 22.04 with the updates archive enabled but not proposed and I'm
not seeing the available update. Temporarily enabling proposed and
looking at upgradable packages shows 22.2.5-0ubuntu0.1~22.04.2 which
matches up which the launchpad page.

Is there an ETA for this package to land in updates?

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Released
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


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

[Touch-packages] [Bug 1860178] Re: [nouveau] Desktop wallpaper is corrupt noise on GeForce 6150SE nForce 430

Thank you for reporting this bug to Ubuntu.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [nouveau] Desktop wallpaper is corrupt noise on GeForce 6150SE nForce
  430

Status in linux package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  Graphic environment unstable, desktop background degraded. Seems
  consequently to last system upgrade (2020.jan.17)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Jan 17 21:55:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
  InstallationDate: Installed on 2019-08-03 (167 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 
multicard reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser 
Printer
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: eMachines EL1358
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=52e5db54-2ea1-48ba-9efe-6b23d1188404 ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.name: EL1358
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr:
  dmi.product.family: eMachines Desktop
  dmi.product.name: EL1358
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: eMachines
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.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

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


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

[Touch-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

Thank you for reporting this bug to Ubuntu.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Won't Fix

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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


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

[Touch-packages] [Bug 1799947] Re: [radeon] Application windows in 18.04.01 go black but launcher is still visible

Thank you for reporting this bug to Ubuntu.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

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

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

Title:
  [radeon] Application windows in 18.04.01 go black but launcher is
  still visible

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  Intermittently and randomly, all application windows will go black.
  They are still there, and can be interacted with with keyboard
  shortcuts or if you know where to click with the mouse, but they are
  not drawn.

  The launcher itself is still displayed.

  Clicking Show Applications briefly draws the application window before
  switching to the background and application icons. The application
  icons are shown correctly. Selecting one switches to a black window
  for that application. The application window is again briefly
  displayed when dismissing the application icons by again clicking Show
  Applications.

  TTYs work normally.

  Killing gnome (from another TTY) and allowing it to relaunch results
  in a normal display again.

  This is being seen on an hp 6910p. This system also exhibits a
  corrupted lock screen since upgrade to 18.04.01. Neither of these
  behaviors were seen during two years running 16.04.01.

  Chrome is being used. Current 70.00.3538.77 (64-bit). Chrome is the
  most commonly used application on this machine, so it is possible that
  the behavior is being triggered by Chrome, however, the behavior
  affects all applications, including system applications like software
  update and terminal.

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


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

[Touch-packages] [Bug 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)

Thank you for reporting this bug to Ubuntu.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)

Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When Wayland is activated in GDM, nothing happens when selecting an
  account with the keyboard or typing in the password. I have to type,
  then wait, then move the mouse around for the characters to appears.

  Because I wouldn't believe this report, I made a video of the problem:
  
https://peertube.mastodon.host/videos/watch/a4d02b33-d71e-4b0e-82cf-f2a74f952ca5

  Moving from Wayland to X makes the issue disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 18:39:19 2018
  InstallationDate: Installed on 2018-06-17 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-24T23:13:52.497184

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


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

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

I've proposed a fix for the core22 serie now on
https://github.com/ubuntu/gnome-sdk/pull/143

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

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Confirmed
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics

2023-06-01 Thread Timo Aaltonen

That's correct, but so far llvm updates have been done in tandem with
mesa backports, so I'm not too worried about those this time.

The upstream solution should take that into account, though.

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  New
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland

Thank you for reporting this bug to Ubuntu.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen with
  nouveau + Wayland

Status in linux package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  WORKAROUND:

  Edit /etc/gdm3/custom.conf and uncomment:
#WaylandEnable=false

  ---

  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  ---
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click

** Tags removed: bionic

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

Title:
  Maximize vertically/horizontally doesn't work (in some apps) if
  configured via middle-click

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

** Tags removed: bionic xenial

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  New
Status in GTK+:
  New
Status in Mir:
  Fix Released
Status in Mutter:
  New
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions


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

[Touch-packages] [Bug 1370953] Re: layout switch is delayed

** Tags removed: bionic

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

Title:
  layout switch is delayed

Status in GNOME Shell:
  New
Status in console-setup package in Ubuntu:
  Incomplete
Status in gconf package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1370953/+subscriptions


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

[Touch-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore

** Description changed:

+ * Impact
+ 
+ The libheif loader is bailing out due to a missing plugin directory
+ which leads to image viewer as eog not being able to open pictures in
+ that format anymore
+ 
+ * Testcase
+ 
+ Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog
+ 
+ * Where problems could occur
+ 
+ The package build is using the option to not split the codec in separate
+ plugins but the version of Lunar doesn't handle the missing plugins
+ directory and bails out. The code of the version in mantic has been
+ refactored in a way which fixes this problem. For lunar it's easier to
+ just create the directory. The directory is included in the libheif1
+ binary but that should not create any conflict, it's a temporary
+ situation for lunar only and even if the soname changed dpkg allows for
+ several deb packages to provide the same directory.
+ 
+ --
+ 
+ 
  In previous Ubuntu versions, including 22.10, I was able to open
  HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does
  not work anymore in 23.04.
  
  Running eog in a terminal displays:
  $ eog IMG_9996.HEIC
  
  ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory.
  
  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537:
  gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed
  
  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed
  
  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed
  
  ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory.
  
  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed
  
  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed
  
  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed
  
  eog then shows "Could not load image “IMG_9996.HEIC”. Image loading
  failed."
  
- 
  gpicview even crashes immediately:
  $ gpicview IMG_9996.HEIC
  Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module"
  
  ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin
  directory.
  
  ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory.
  Segmentation fault (core dumped)
  
- 
  The problem concerns all HEIF/HEIC images I tested.
  
  The installed versions of the (possibly) relevant packages are:
  libheif1: 1.14.2-1
  heif-gdk-pixbuf: 1.14.2-1
  libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1
  eog: 44.0-1
  gpicview: 0.2.5-3build1

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

Title:
  Cannot open HEIF/HEIC images in 23.04/lunar anymore

Status in eog package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in libheif package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The libheif loader is bailing out due to a missing plugin directory
  which leads to image viewer as eog not being able to open pictures in
  that format anymore

  * Testcase

  Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in
  eog

  * Where problems could occur

  The package build is using the option to not split the codec in
  separate plugins but the version of Lunar doesn't handle the missing
  plugins directory and bails out. The code of the version in mantic has
  been refactored in a way which fixes this problem. For lunar it's
  easier to just create the directory. The directory is included in the
  libheif1 binary but that should not create any conflict, it's a
  temporary situation for lunar only and even if the soname changed dpkg
  allows for several deb packages to provide the same directory.

  --


  In previous Ubuntu versions, including 22.10, I was able to open
  HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does
  not work anymore in 23.04.

  Running eog in a terminal displays:
  $ eog IMG_9996.HEIC

  ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  **

[Touch-packages] [Bug 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1

2023-06-01 Thread Adrien Nader

I expect "frontend" to be "/usr/share/debconf/frontend" and therefore
that you have another update (still) running somewhere, waiting for you
to answer a question from debconf.

I like to look at the output of "ps faux" to get more context into what
has started process. You can either "ps faux | less" and "/frontend", or
soemthing like "ps faux | grep -B 4 -A 1 frontend" (show 4 lines Before
and 1 line After the match).

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

Title:
  package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade:
  installed libssl3:amd64 package post-installation script subprocess
  returned error exit status 1

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  encounter error when attempting to do sudo update, upgrade, and full-
  upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libssl3:amd64 3.0.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  1 10:28:26 2023
  ErrorMessage: installed libssl3:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-01 (150 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: openssl
  Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: 
installed libssl3:amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore

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

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

Title:
  Cannot open HEIF/HEIC images in 23.04/lunar anymore

Status in eog package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in libheif package in Ubuntu:
  Fix Released

Bug description:
  In previous Ubuntu versions, including 22.10, I was able to open
  HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does
  not work anymore in 23.04.

  Running eog in a terminal displays:
  $ eog IMG_9996.HEIC

  ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  eog then shows "Could not load image “IMG_9996.HEIC”. Image loading
  failed."

  
  gpicview even crashes immediately:
  $ gpicview IMG_9996.HEIC
  Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module"

  ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin
  directory.

  ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory.
  Segmentation fault (core dumped)

  
  The problem concerns all HEIF/HEIC images I tested.

  The installed versions of the (possibly) relevant packages are:
  libheif1: 1.14.2-1
  heif-gdk-pixbuf: 1.14.2-1
  libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1
  eog: 44.0-1
  gpicview: 0.2.5-3build1

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


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

[Touch-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore

The issue is fixed in
https://launchpad.net/ubuntu/+source/libheif/1.15.1-1 , we will issue a
stable update also for Lunar

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

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: eog (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Cannot open HEIF/HEIC images in 23.04/lunar anymore

Status in eog package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in libheif package in Ubuntu:
  Confirmed

Bug description:
  In previous Ubuntu versions, including 22.10, I was able to open
  HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does
  not work anymore in 23.04.

  Running eog in a terminal displays:
  $ eog IMG_9996.HEIC

  ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  eog then shows "Could not load image “IMG_9996.HEIC”. Image loading
  failed."

  
  gpicview even crashes immediately:
  $ gpicview IMG_9996.HEIC
  Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module"

  ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin
  directory.

  ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory.
  Segmentation fault (core dumped)

  
  The problem concerns all HEIF/HEIC images I tested.

  The installed versions of the (possibly) relevant packages are:
  libheif1: 1.14.2-1
  heif-gdk-pixbuf: 1.14.2-1
  libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1
  eog: 44.0-1
  gpicview: 0.2.5-3build1

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


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

[Touch-packages] [Bug 1782984] Proposed package removed from archive

The version of libx11 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Won't Fix
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is

[Touch-packages] [Bug 1782984] Proposed package removed from archive

The version of libx11 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Won't Fix
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is

[Touch-packages] [Bug 1782984] Proposed package removed from archive

The version of libx11 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Won't Fix
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is

[Touch-packages] [Bug 1782984] Proposed package removed from archive

The version of libx11 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

** Changed in: libx11 (Ubuntu Bionic)
   Status: Fix Committed => Won't Fix

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Won't Fix
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar)

[Touch-packages] [Bug 1813581] Proposed package removed from archive

The version of gpgme1.0 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

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

Title:
  gpgme1.0 ftbfs in 18.04 LTS

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Bionic:
  Won't Fix

Bug description:
  [Impact]
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  gpgme1.0 ftbfs.

  * Start testing of TofuInfoTest *
  Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.3.0)
  PASS   : TofuInfoTest::initTestCase()
  PASS   : TofuInfoTest::testTofuNull()
  PASS   : TofuInfoTest::testTofuInfo()
  PASS   : TofuInfoTest::testTofuSignCount()
  PASS   : TofuInfoTest::testTofuKeyList()
  PASS   : TofuInfoTest::testTofuPolicy()
  FAIL!  : TofuInfoTest::testTofuConflict() 'sig.validity() == 
Signature::Marginal' returned FALSE. ()
     Loc: [t-tofuinfo.cpp(458)]
  PASS   : TofuInfoTest::cleanupTestCase()
  Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms
  * Finished testing of TofuInfoTest *
  FAIL: t-tofuinfo

  [Test case]
  build it

  [Regression potential]
  This only changes the test suite run during build, and that one currently 
fails, so it can't cause any regression.

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


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

[Touch-packages] [Bug 1813581] Proposed package removed from archive

The version of gpgme1.0 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

** Changed in: gpgme1.0 (Ubuntu Bionic)
   Status: Fix Committed => Won't Fix

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

Title:
  gpgme1.0 ftbfs in 18.04 LTS

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Bionic:
  Won't Fix

Bug description:
  [Impact]
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  gpgme1.0 ftbfs.

  * Start testing of TofuInfoTest *
  Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.3.0)
  PASS   : TofuInfoTest::initTestCase()
  PASS   : TofuInfoTest::testTofuNull()
  PASS   : TofuInfoTest::testTofuInfo()
  PASS   : TofuInfoTest::testTofuSignCount()
  PASS   : TofuInfoTest::testTofuKeyList()
  PASS   : TofuInfoTest::testTofuPolicy()
  FAIL!  : TofuInfoTest::testTofuConflict() 'sig.validity() == 
Signature::Marginal' returned FALSE. ()
     Loc: [t-tofuinfo.cpp(458)]
  PASS   : TofuInfoTest::cleanupTestCase()
  Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms
  * Finished testing of TofuInfoTest *
  FAIL: t-tofuinfo

  [Test case]
  build it

  [Regression potential]
  This only changes the test suite run during build, and that one currently 
fails, so it can't cause any regression.

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


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

[Touch-packages] [Bug 1886790] Update Released

The verification of the Stable Release Update for lxc has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
  (device_add_remove_test)

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

   * The device_add_remove_test test fails on the affected series (e.g. Bionic).
   * Having the test fixed for the affected series (for example, Bionic) will 
allow us to run the LXC test suite without maintaining local changes for this 
test.

  [ Test Plan ]

   * Run the affected test on an affected series (e.g. Bionic).
   * The test should pass.

  [ Where problems could occur ]

   * The regression risk is very low, and the changes only affect the
  tests, so the regression scope is minimal.

  [ Other Info ]

  Upstream drop of network_latency: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113
  Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587

  Original bug report:

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz

  The failing test seems to be:

  FAIL: lxc-tests: lxc-test-device-add-remove (0s)
  ---
  Adding /dev/network_latency to the container (device_add_remove_test) 
failed...
  ---

  This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note
  that this testcase is successful on Focal with the same kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions


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

[Touch-packages] [Bug 1848587] Re: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2

This bug was fixed in the package lxc - 3.0.3-0ubuntu1~18.04.3

---
lxc (3.0.3-0ubuntu1~18.04.3) bionic; urgency=medium

  * Fix tests issue by avoiding falling back to inexistent trusty LXC images
and using the bionic ones (LP: #1939537)

lxc (3.0.3-0ubuntu1~18.04.2) bionic; urgency=medium

  * Cherry-pick upstream bugfixes (LP: #1848587 LP: #1886790):
- tests: use /dev/loop-control instead of /dev/network_latency
- This unbreaks adt-matrix / adt testing of Bionic hwe kernels

 -- Andrei Gherzan   Fri, 05 May 2023
14:06:12 +0200

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

Title:
  lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

   * Test suite fails due to inexistent device (/dev/network_latency).

  [ Test Plan ]

   * Run the test suite.
   * The test should pass.

  [ Where problems could occur ]

   * The regression risk is very low, and the changes only affect the
  tests, so the regression scope is minimal.

  [ Other Info ]

  Original bug report:

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz

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


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

[Touch-packages] [Bug 1848587] Update Released

The verification of the Stable Release Update for lxc has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

   * Test suite fails due to inexistent device (/dev/network_latency).

  [ Test Plan ]

   * Run the test suite.
   * The test should pass.

  [ Where problems could occur ]

   * The regression risk is very low, and the changes only affect the
  tests, so the regression scope is minimal.

  [ Other Info ]

  Original bug report:

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz

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


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

[Touch-packages] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)

This bug was fixed in the package lxc - 3.0.3-0ubuntu1~18.04.3

---
lxc (3.0.3-0ubuntu1~18.04.3) bionic; urgency=medium

  * Fix tests issue by avoiding falling back to inexistent trusty LXC images
and using the bionic ones (LP: #1939537)

lxc (3.0.3-0ubuntu1~18.04.2) bionic; urgency=medium

  * Cherry-pick upstream bugfixes (LP: #1848587 LP: #1886790):
- tests: use /dev/loop-control instead of /dev/network_latency
- This unbreaks adt-matrix / adt testing of Bionic hwe kernels

 -- Andrei Gherzan   Fri, 05 May 2023
14:06:12 +0200

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

Title:
  lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
  (device_add_remove_test)

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

   * The device_add_remove_test test fails on the affected series (e.g. Bionic).
   * Having the test fixed for the affected series (for example, Bionic) will 
allow us to run the LXC test suite without maintaining local changes for this 
test.

  [ Test Plan ]

   * Run the affected test on an affected series (e.g. Bionic).
   * The test should pass.

  [ Where problems could occur ]

   * The regression risk is very low, and the changes only affect the
  tests, so the regression scope is minimal.

  [ Other Info ]

  Upstream drop of network_latency: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113
  Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587

  Original bug report:

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz

  The failing test seems to be:

  FAIL: lxc-tests: lxc-test-device-add-remove (0s)
  ---
  Adding /dev/network_latency to the container (device_add_remove_test) 
failed...
  ---

  This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note
  that this testcase is successful on Focal with the same kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions


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

[Touch-packages] [Bug 1939537] Update Released

The verification of the Stable Release Update for lxc has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching
  image." on X-hwe and older releases

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

   * The following tests fail as they try to use inexistent LXC images:
     * lxc-test-apparmor-mount
     * lxc-test-autostart
     * lxc-test-unpriv
     * lxc-test-usernic

   * Having them fixed for the affected series (for example, Bionic)
  will allow us to run the LXC test suite without maintaining local
  changes for these tests.

  [ Test Plan ]

   * Run the affected tests on an affected series (e.g. Bionic).
   * The tests should pass.

  [ Where problems could occur ]

   * The regression risk is very low and the changes only affect the
  tests so the regression scope is minimal.

  [Other info]

  Original bug report:

  Issue found on node onibi 4.15.0-142-generic #146~16.04.1

  With bug 1916087 resolved, the following tests:
    * lxc-test-apparmor-mount
    * lxc-test-autostart
    * lxc-test-unpriv
    * lxc-test-usernic

  Are now failing with:
    ERROR: Couldn't find a matching image.

  This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target 
release is "trusty" or the system release if supported. It will be checked with:
    ubuntu-distro-info --supported

  However Xenial is an ESM series now, it won't use xenial as the target
  release but use trusty instead.

  The attempt to download trusty image will fail with this error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+subscriptions


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

[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases

This bug was fixed in the package lxc - 3.0.3-0ubuntu1~18.04.3

---
lxc (3.0.3-0ubuntu1~18.04.3) bionic; urgency=medium

  * Fix tests issue by avoiding falling back to inexistent trusty LXC images
and using the bionic ones (LP: #1939537)

lxc (3.0.3-0ubuntu1~18.04.2) bionic; urgency=medium

  * Cherry-pick upstream bugfixes (LP: #1848587 LP: #1886790):
- tests: use /dev/loop-control instead of /dev/network_latency
- This unbreaks adt-matrix / adt testing of Bionic hwe kernels

 -- Andrei Gherzan   Fri, 05 May 2023
14:06:12 +0200

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

Title:
  Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching
  image." on X-hwe and older releases

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

   * The following tests fail as they try to use inexistent LXC images:
     * lxc-test-apparmor-mount
     * lxc-test-autostart
     * lxc-test-unpriv
     * lxc-test-usernic

   * Having them fixed for the affected series (for example, Bionic)
  will allow us to run the LXC test suite without maintaining local
  changes for these tests.

  [ Test Plan ]

   * Run the affected tests on an affected series (e.g. Bionic).
   * The tests should pass.

  [ Where problems could occur ]

   * The regression risk is very low and the changes only affect the
  tests so the regression scope is minimal.

  [Other info]

  Original bug report:

  Issue found on node onibi 4.15.0-142-generic #146~16.04.1

  With bug 1916087 resolved, the following tests:
    * lxc-test-apparmor-mount
    * lxc-test-autostart
    * lxc-test-unpriv
    * lxc-test-usernic

  Are now failing with:
    ERROR: Couldn't find a matching image.

  This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target 
release is "trusty" or the system release if supported. It will be checked with:
    ubuntu-distro-info --supported

  However Xenial is an ESM series now, it won't use xenial as the target
  release but use trusty instead.

  The attempt to download trusty image will fail with this error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+subscriptions


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

[Touch-packages] [Bug 1733321] Proposed package removed from archive

The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run

[Touch-packages] [Bug 1733321] Proposed package removed from archive

The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run

[Touch-packages] [Bug 1733321] Proposed package removed from archive

The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run

[Touch-packages] [Bug 1733321] Proposed package removed from archive

The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run

[Touch-packages] [Bug 1733321] Proposed package removed from archive

The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

** Changed in: network-manager (Ubuntu Bionic)
   Status: Fix Committed => Won't Fix

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download

[Touch-packages] [Bug 1733321] Proposed package removed from archive

The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run

[Touch-packages] [Bug 1974223] Proposed package removed from archive

The version of unattended-upgrades in the proposed pocket of Bionic that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: Fix Committed => Won't Fix

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

Title:
  FTBFS and autopkgtest failure since changes in apt for automatic
  kernel removal

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Won't Fix
Status in unattended-upgrades source package in Focal:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [Impact]
  Since the following changes in apt have landed in focal-updates (and is 
currently in bionic-proposed), unattended-upgrades FTBFS and fails autopkgtest 
on both series:

    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

  [Test plan]
  1. focal:
* run autopkgtest against -updates:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=updates 
--test-name run-tests -- 
* try to build the package
  2. bionic:
* run autopkgtest against -proposed:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=proposed 
--test-name run-tests -- 
* try to build the package

  [Where problems could occur]
* The fix only affects the test-suite (that runs both at build time & 
autopkgtest time) so the impact should be minimal. Something wrong in the patch 
would make the unattended package FTBFS or fail autopkgtest but it is already 
failing ATM.
* The new tests dependency on apt can trigger more autopkgtest runs. Since 
unattended-upgrades has a non-trivial autopkgtest suite, this can have a slight 
impact on the queues.

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


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

[Touch-packages] [Bug 1974223] Proposed package removed from archive

The version of unattended-upgrades in the proposed pocket of Bionic that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.

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

Title:
  FTBFS and autopkgtest failure since changes in apt for automatic
  kernel removal

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Won't Fix
Status in unattended-upgrades source package in Focal:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [Impact]
  Since the following changes in apt have landed in focal-updates (and is 
currently in bionic-proposed), unattended-upgrades FTBFS and fails autopkgtest 
on both series:

    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

  [Test plan]
  1. focal:
* run autopkgtest against -updates:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=updates 
--test-name run-tests -- 
* try to build the package
  2. bionic:
* run autopkgtest against -proposed:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=proposed 
--test-name run-tests -- 
* try to build the package

  [Where problems could occur]
* The fix only affects the test-suite (that runs both at build time & 
autopkgtest time) so the impact should be minimal. Something wrong in the patch 
would make the unattended package FTBFS or fail autopkgtest but it is already 
failing ATM.
* The new tests dependency on apt can trigger more autopkgtest runs. Since 
unattended-upgrades has a non-trivial autopkgtest suite, this can have a slight 
impact on the queues.

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


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

[Touch-packages] [Bug 1974223] Proposed package removed from archive