date:20220317

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1945114, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1965452/+attachment/5570204/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1965452/+attachment/5570206/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1965452/+attachment/5570210/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1965452/+attachment/5570211/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1965452/+attachment/5570212/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965452/+attachment/5570213/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965452/+attachment/5570214/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1945114

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGSEGV in g_type_create_instance()

Status in apport package in Ubuntu:
  New

Bug description:
  Dash To Panel

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: apport-gtk 2.20.11-0ubuntu79
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:11380649:2022-03-18 01:21:03.894274711 +0300:2022-03-18 
01:21:04.894274711 +0300:/var/crash/_usr_bin_gjs-console.1000.crash
   640:1000:124:7279496:2022-03-18 01:21:06.638510227 +0300:2022-03-18 
01:21:07.638510227 +0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 18 01:21:05 2022
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2022-03-17 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220316)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 
3.10.1-0ubuntu2
  PythonDetails: /usr/bin/python3.10, Python 3.10.3, python-is-python3, 3.9.2-2
  SegvAnalysis:
   Segfault happened at: 0x7f7d19f63cf4:mov0x18(%rax),%rax
   PC (0x7f7d19f63cf4) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: apport-gtk crashed with SIGSEGV in g_type_create_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Touch-packages] [Bug 1951279] Re: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds

2022-03-17 Thread Bug Watch Updater

** Changed in: openssl (Debian)
   Status: New => Fix Released

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

Title:
  OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds

Status in OpenSSL:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Confirmed
Status in openssl package in Debian:
  Fix Released

Bug description:
  Description
  ---

  It seems that current Ubuntu 20.04 (Focal) distribution for
  Arm64/Aarch64 raise a segmentation fault when certain validates some
  certificates.

  This issue affects only to Arm64/Aarch64 all the tools statically or
  dynamically linked with this version of the library are affected
  (Libcurl4, Curl, Wget, OpenJDK, Curl-PHP, etc).

  
  Environment and platform
  
  Linux 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:29:20 UTC 2021 aarch64 
aarch64 aarch64 GNU/Linux

  
  Steps to reproduce
  --

  1. Run:

  curl -v https://graph.facebook.com/v12.0/act_111/

  or

  wget https://graph.facebook.com/v12.0/act_111/

  
  Result received
  ---

  Segmentation fault (core dumped)

  
  Notes
  -

  This bug was found by the Curl users:
  See: https://github.com/curl/curl/issues/8024

  I believe that this bug is related to
  https://ubuntu.com/security/CVE-2020-1967 that maybe used as a vector
  point for code injection.

  Actually there isn't any replacement for OpenSSL 1.1.1f for Focal
  (Arm64), so it makes difficult to use Ubuntu 20.04 in a production
  environment.

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

ssh mclibre@127.0.0.1

** Attachment added: "5_ssh_myself.png"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+attachment/5570199/+files/5_ssh_myself.png

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

ip_addr

** Attachment added: "1_ip_addr.png"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+attachment/5570195/+files/1_ip_addr.png

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

/etc/dhcp/dhclient.conf (1)

** Attachment added: "6_dhclient_conf_1.png"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+attachment/5570200/+files/6_dhclient_conf_1.png

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

systemctl status ssh

** Attachment added: "4_systemctl_status_ssh.png"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+attachment/5570198/+files/4_systemctl_status_ssh.png

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

/etc/netplan/00-installer-config.yaml

** Attachment added: "8_00_installer_config_yaml.png"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+attachment/5570202/+files/8_00_installer_config_yaml.png

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

systemctl status (2)

** Attachment added: "3_systemctl_status_2.png"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+attachment/5570197/+files/3_systemctl_status_2.png

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

/etc/dhcp/dhclient.conf (2)

** Attachment added: "7_dhclient_conf_2.png"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+attachment/5570201/+files/7_dhclient_conf_2.png

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

systemctl status (1)

** Attachment added: "2_systemctl_status_1.png"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+attachment/5570196/+files/2_systemctl_status_1.png

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

Thank you for your help, paride. Now, answering your questions:

Yes, I am using last versions of Packer (1.8.0) and VirtualBox (6.1.32).
Host is Windows 10. Ubuntu 20.04 works, but .1, .2, .3 and .4 update
releases don't. By the way, the situation is worse in jammy daily builds
because I can not even begin the unattended instalation (I have opened a
question about this problem in Ubuntu forums
https://ubuntuforums.org/showthread.php?t=2472899).

ens33 is in user-data file just because I copied a working example of
autoinstall file.

I can ssh login from the machine to itself.

I have made some screenshots showing the output of commands you asked me
for.

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1956835] Re: zsys cleanup of /boot should be reevaluated

** Summary changed:

- package linux-firmware 1.187.24 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
+ zsys cleanup of /boot should be reevaluated

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

** Tags added: rls-jj-incoming

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

Title:
  zsys cleanup of /boot should be reevaluated

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After updating the system, rebooted and this error appeared.
  Fixed a problem related to /boot/grub/grubenv - "Error in environment" and 
grub-common.service
  by providing absolute path to grub-editenv.  /boot/grub/grubenv was full of 
0x0, rather than 0x2323 as it has now.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.24
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   3520 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 17:37:06 2022
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-11-12 (422 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic 
root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.24 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2018
  dmi.bios.release: 15.113
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.71
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.38
  dmi.chassis.asset.tag: CNU3109W10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 66.56
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.71:bd04/12/2018:br15.113:efr66.56:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:skuC3Q91UC#ABU:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8470p
  dmi.product.sku: C3Q91UC#ABU
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

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


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

[Touch-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

2022-03-17 Thread Launchpad Bug Tracker

This bug was fixed in the package cups - 2.4.1op1-1ubuntu3

---
cups (2.4.1op1-1ubuntu3) jammy; urgency=low

  * Fixed crasher in the patch for temporary queues for local services
in the previous release. Updated the patch and the upstream pull
request (LP: #1965112, Upstream pull request #353).

 -- Till Kamppeter   Wed, 16 Mar 2022 18:24:08
+0100

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

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

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


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

[Touch-packages] [Bug 1965438] [NEW] tar_1.29b-2ubuntu0.3 fails to build with nodoc build profile

2022-03-17 Thread Alex Kompel

Public bug reported:

tar source package fails to build with nodoc build profile
(DEB_BUILD_PROFILES="nodoc")

$ lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04

$ apt-get source tar
$ cd tar-1.29b
$ DEB_BUILD_PROFILES="nodoc nocheck" debuild -us -uc
...
dh_testdir
dh_testroot
dh_installdocs
mv -f debian/tar/usr/share/doc/tar/ChangeLog \
debian/tar/usr/share/doc/tar/changelog
mv: cannot stat 'debian/tar/usr/share/doc/tar/ChangeLog': No such file or 
directory
debian/rules:87: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2

-

dh_installdocs and dh_installman  are no-op under nodoc profile so build
script should not assume that doc files are present:

diff -ru tar-1.29b.orig/debian/rules tar-1.29b/debian/rules
--- tar-1.29b.orig/debian/rules 2022-03-17 10:58:33.940191507 -0700
+++ tar-1.29b/debian/rules  2022-03-17 11:29:57.061510969 -0700
@@ -88,15 +88,15 @@
dh_testroot
dh_installdocs
mv -f debian/tar/usr/share/doc/tar/ChangeLog \
-   debian/tar/usr/share/doc/tar/changelog
+   debian/tar/usr/share/doc/tar/changelog || true
mv -f debian/tar/usr/share/doc/tar/ChangeLog.1 \
-   debian/tar/usr/share/doc/tar/changelog.1
+   debian/tar/usr/share/doc/tar/changelog.1 || true
dh_installexamples
dh_installmenu
dh_installcron
dh_installman doc/tar.1 doc/rmt.8 debian/tarcat.1
mv debian/tar/usr/share/man/man8/rmt.8 \
-  debian/tar/usr/share/man/man8/rmt-tar.8
+  debian/tar/usr/share/man/man8/rmt-tar.8 || true
dh_installinfo
rm -f debian/tar/usr/share/info/dir*
dh_installmime

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

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

Title:
  tar_1.29b-2ubuntu0.3 fails to build with nodoc build profile

Status in tar package in Ubuntu:
  New

Bug description:
  tar source package fails to build with nodoc build profile
  (DEB_BUILD_PROFILES="nodoc")

  $ lsb_release -rd
  Description:Ubuntu 18.04.6 LTS
  Release:18.04

  $ apt-get source tar
  $ cd tar-1.29b
  $ DEB_BUILD_PROFILES="nodoc nocheck" debuild -us -uc
  ...
  dh_testdir
  dh_testroot
  dh_installdocs
  mv -f debian/tar/usr/share/doc/tar/ChangeLog \
  debian/tar/usr/share/doc/tar/changelog
  mv: cannot stat 'debian/tar/usr/share/doc/tar/ChangeLog': No such file or 
directory
  debian/rules:87: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  -

  dh_installdocs and dh_installman  are no-op under nodoc profile so
  build script should not assume that doc files are present:

  diff -ru tar-1.29b.orig/debian/rules tar-1.29b/debian/rules
  --- tar-1.29b.orig/debian/rules 2022-03-17 10:58:33.940191507 -0700
  +++ tar-1.29b/debian/rules  2022-03-17 11:29:57.061510969 -0700
  @@ -88,15 +88,15 @@
  dh_testroot
  dh_installdocs
  mv -f debian/tar/usr/share/doc/tar/ChangeLog \
  -   debian/tar/usr/share/doc/tar/changelog
  +   debian/tar/usr/share/doc/tar/changelog || true
  mv -f debian/tar/usr/share/doc/tar/ChangeLog.1 \
  -   debian/tar/usr/share/doc/tar/changelog.1
  +   debian/tar/usr/share/doc/tar/changelog.1 || true
  dh_installexamples
  dh_installmenu
  dh_installcron
  dh_installman doc/tar.1 doc/rmt.8 debian/tarcat.1
  mv debian/tar/usr/share/man/man8/rmt.8 \
  -  debian/tar/usr/share/man/man8/rmt-tar.8
  +  debian/tar/usr/share/man/man8/rmt-tar.8 || true
  dh_installinfo
  rm -f debian/tar/usr/share/info/dir*
  dh_installmime

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


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

[Touch-packages] [Bug 1965437] [NEW] Cannot change background 22.04

2022-03-17 Thread Chief

Public bug reported:

Background stuck on black. Cannot change via GUI or CLI

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 17 18:57:43 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.32, 5.15.0-22-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0584]
InstallationDate: Installed on 2022-03-15 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
MachineType: Dell Inc. Latitude 6430U
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=0b7063d6-5898-4f7f-ac0b-73d105ab566a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2018
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0JCV3H
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/30/2018:br4.6:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0JCV3H:rvrA02:cvnDellInc.:ct9:cvr:skuLatitude6430U:
dmi.product.name: Latitude 6430U
dmi.product.sku: Latitude 6430U
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2

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


** Tags: amd64 apport-bug jammy reproducible ubuntu wayland-session

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

Title:
  Cannot change background 22.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Background stuck on black. Cannot change via GUI or CLI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 18:57:43 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-22-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0584]
  InstallationDate: Installed on 2022-03-15 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  MachineType: Dell Inc. Latitude 6430U
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=0b7063d6-5898-4f7f-ac0b-73d105ab566a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0JCV3H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/30/2018:br4.6:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0JCV3H:rvrA02:cvnDellInc.:ct9:cvr:skuLatitude6430U:
  dmi.product.name: Latitude 6430U
  dmi.product.sku: Latitude 6430U
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1

[Touch-packages] [Bug 1964483] Re: Update supported mirror protocol according to official archive mirrors list

** Tags added: rls-kk-incoming

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

Title:
  Update supported mirror protocol according to official archive mirrors
  list

Status in software-properties package in Ubuntu:
  New

Bug description:
  While mirrors listed on https://launchpad.net/ubuntu/+archivemirrors
  support https, this is not reflected in software-properties-gtk ->
  Download from -> other dialogue. Example: Charite Berlin supports
  https, but only http is available from the "Protocol" dialogue.

  Editing /etc/apt/sources.list mitigates the issue, though
  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/1814072 is still unresolved.

  lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  apt-cache policy software-properties-gtk
  software-properties-gtk:
  Installed: 0.99.19

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


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

[Touch-packages] [Bug 1965112] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965112/+attachment/5570110/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1965112/+attachment/5569535/+files/CoreDump.gz

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

** Summary changed:

- cupsd crashed with SIGSEGV in __strcmp_evex()
+ cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

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


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

[Touch-packages] [Bug 1965112] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965112/+attachment/5570108/+files/Stacktrace.txt

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

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


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

[Touch-packages] [Bug 1965112] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1965112/+attachment/5570109/+files/StacktraceSource.txt

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

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


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

[Touch-packages] [Bug 1965112] cupsd crashed with SIGSEGV in __strcmp_evex()

StacktraceTop:
 __strnlen_avx2_rtm () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:256
 create_local_printer (con=0x55ea82141090) at 
/build/cups-y1LIcO/cups-2.4.1op1/scheduler/ipp.c:5539
 cupsdProcessIPPRequest (con=0x55ea82141090) at 
/build/cups-y1LIcO/cups-2.4.1op1/scheduler/ipp.c:604
 cupsdReadClient (con=0x55ea82141090) at 
/build/cups-y1LIcO/cups-2.4.1op1/scheduler/client.c:1814
 cupsdDoSelect (timeout=) at 
/build/cups-y1LIcO/cups-2.4.1op1/scheduler/select.c:480

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

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


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

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

2022-03-17 Thread Bill Yu

Hi Robie and Lukas,

From our understanding, the concern is only related to Jammy, not focal.
Is that OK to change to fix released on focal.
This is one of the blocking issue for Stella Magneta platform. 
We need your help to comment on this. Thank you.

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Impish:
  In Progress
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

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


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

[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

2022-03-17 Thread Bruce Elrick

For posterity, here is an example of the relevant part of the client
trace output when the bug is active, i.e. data is sent with the
ClientRequest:

$ grep -B1 -A4 CertificateRequest s_client.log
  Inner Content Type = Handshake (22)
CertificateRequest, Length=1570
  request_context (len=0): 
  extensions, length = 1567
extension_type=status_request(5), length=1521
   - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   0..

Here is an example of the relevant part of the client trace output when
this is fixed:

$ grep -B1 -A4 CertificateRequest s_client.log
  Inner Content Type = Handshake (22)
CertificateRequest, Length=45
  request_context (len=0): 
  extensions, length = 42
extension_type=signature_algorithms(13), length=38
  ecdsa_secp256r1_sha256 (0x0403)

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

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


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

[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: Incomplete

** Also affects: systemd (Ubuntu Jammy)
   Importance: High
   Status: New

** Tags removed: rls-ii-incoming rls-jj-incoming

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with
  linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  New
Status in linux source package in Jammy:
  Incomplete
Status in systemd source package in Jammy:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

  The "tests-in-lxd" testcase is failing with all kernels in Impish:

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service snap-lxd-22662.mount 
---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
   journal for failed service snap-snapd-15177.mount ---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
  FAIL
  [...]
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []

  First list contains 2 additional elements.
  First extra element 0:
  'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'

  + []
  - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
  -  '22662',
  -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
  -  '15177']

  
  This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:

  "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

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


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

[Touch-packages] [Bug 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows

** Tags added: fr-2116

** Also affects: software-properties (Ubuntu Jammy)
   Importance: High
   Status: New

** Tags removed: rls-jj-incoming

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

Title:
  apt-add-repository requires --login for private repos, breaking
  automated workflows

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Jammy:
  New

Bug description:
  On Focal, in an automated environment (such as a launchpad builder), a
  used can do the following workflow:

  curl
  "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
  --output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu focal main"

  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
  Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
  Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 
Packages [3288 B] 
  Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main 
Translation-en [1892 B]  

  However, on Jammy, I get the following:

  
  curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT}; 
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu jammy main"

  Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, 
in lpppa
  self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 
592, in __call__
  response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
429, in _request
  raise error
  lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
  Response headers:
  ---
  -content-encoding: gzip
  content-length: 91
  content-type: text/plain;charset=utf-8
  date: Wed, 16 Mar 2022 19:54:16 GMT
  server: gunicorn/19.8.1
  status: 404
  vary: Accept-Encoding
  x-powered-by: Zope (www.zope.org), Python (www.python.org)
  x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
  x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
  ---
  Response body:
  ---
  b"Object: , 
name: '$REPO'"
  ---

  
  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
  self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
  if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, 
in description
  return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, 
in lpppa
  raise ShortcutException(msg)
  softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa 
'$REPO/proposed' not found (use --login if private)

  Impish similarly breaks. Digging through changelogs, I see various
  entries in Impish forward, starting with version 0.99.0 where a
  refactor was done.

  using `--login` is not possible in an automated setup (such as a
  builder) as it starts an OAuth dance, which requires human
  interaction. this will break existing automation utilizing apt-add-
  repository for users when migrating to Jammy

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


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

[Touch-packages] [Bug 1940505] Re: monero FTBFS on riscv64

2022-03-17 Thread Lukas Märdian

monero builds fine nowadays on riscv64

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

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

Title:
  monero FTBFS on riscv64

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Invalid
Status in monero package in Ubuntu:
  Fix Released

Bug description:
  monero FTBFS on riscv64 due to toolchain issues:

  [ 64%] Linking CXX executable signature_fuzz_tests
  cd "/<>/obj-riscv64-linux-gnu/tests/fuzz" && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/signature_fuzz_tests.dir/link.txt --verbose=1
  /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -DNO_AES  -fno-strict-aliasing -std=c++11 
-D_GNU_SOURCE   -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite-strings 
-Wno-error=extra -Wno-error=deprecated-declarations -Wno-unused-parameter 
-Wno-unused-variable -Wno-error=unused-variable -Wno-error=undef 
-Wno-error=uninitialized -Wlogical-op -Wno-error=maybe-uninitialized 
-Wno-error=cpp -Wno-reorder -Wno-missing-field-initializers  -fPIC  -Wformat 
-Wformat-security -fstack-protector -fstack-protector-strong 
-fstack-clash-protection -fno-strict-aliasing -ftemplate-depth=900 
-Wl,-Bsymbolic-functions -Wl,-z,relro  -pie -Wl,-z,relro -Wl,-z,now 
-Wl,-z,noexecstack  -rdynamic 
CMakeFiles/signature_fuzz_tests.dir/signature.cpp.o 
CMakeFiles/signature_fuzz_tests.dir/fuzzer.cpp.o -o signature_fuzz_tests  
../../lib/libwallet.a ../../src/cryptonote_core/libcryptonote_core.a 
../../src/p2p/libp2p.a ../../contrib/epee/src/libepee.a 
../../src/device/libdevice.a -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl 
../../src/rpc/librpc_base.a ../../src/mnemonics/libmnemonics.a 
../../src/device_trezor/libdevice_trezor.a 
../../src/cryptonote_core/libcryptonote_core.a ../../src/multisig/libmultisig.a 
../../src/blockchain_db/libblockchain_db.a 
../../external/db_drivers/liblmdb/liblmdb.a ../../src/ringct/libringct.a 
../../src/cryptonote_basic/libcryptonote_basic.a ../../src/device/libdevice.a 
-lhidapi-libusb ../../src/ringct/libringct_basic.a ../../src/blocks/libblocks.a 
../../src/checkpoints/libcheckpoints.a ../../src/hardforks/libhardforks.a 
../../src/net/libnet.a ../../src/common/libcommon.a 
../../src/crypto/libcncrypto.a ../../contrib/epee/src/libepee.a 
../../external/easylogging++/libeasylogging.a -lrandomx -lunbound -lboost_regex 
-lboost_date_time -lssl -lcrypto -lzmq -lpgm -lnorm -lgssapi_krb5 -lsodium 
../../src/libversion.a -lminiupnpc -lboost_chrono -lboost_serialization 
-lboost_filesystem -lboost_system -lboost_thread -lboost_program_options 
-Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl  -latomic 
  ../../external/db_drivers/liblmdb/liblmdb.a(mdb.c.o): in function 
`mdb_node_add':
  
./obj-riscv64-linux-gnu/external/db_drivers/liblmdb/./external/db_drivers/liblmdb/mdb.c:8245:(.text+0x44e6):
 relocation truncated to fit: R_RISCV_JAL against `mdb_assert_fail.constprop.0'
  collect2: error: ld returned 1 exit status
  make[3]: *** [tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/build.make:166: 
tests/fuzz/signature_fuzz_tests] Error 1
  make[3]: Leaving directory '/<>/obj-riscv64-linux-gnu'
  make[2]: *** [CMakeFiles/Makefile2:4165: 
tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/all] Error 2
  make[2]: Leaving directory '/<>/obj-riscv64-linux-gnu'
  make[1]: *** [Makefile:163: all] Error 2
  make[1]: Leaving directory '/<>/obj-riscv64-linux-gnu'
  dh_auto_build: error: cd obj-riscv64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
  make: *** [debian/rules:47: binary-arch] Error 25
  dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

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


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

[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42

2022-03-17 Thread Matthieu Clemenceau

** Tags added: fr-2115

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with
  linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

  The "tests-in-lxd" testcase is failing with all kernels in Impish:

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service snap-lxd-22662.mount 
---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
   journal for failed service snap-snapd-15177.mount ---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
  FAIL
  [...]
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []

  First list contains 2 additional elements.
  First extra element 0:
  'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'

  + []
  - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
  -  '22662',
  -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
  -  '15177']

  
  This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:

  "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

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


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

[Touch-packages] [Bug 1965189] Re: Add session migration for GNOME 42 dark theme

2022-03-17 Thread Jeremy Bicha

** Description changed:

Test Case
-
1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance
and choose Dark
2. Upgrade to Ubuntu 22.04 LTS
3. Log out then log back in
4. Your apps should still be dark

Linked Issue

That test case is broken by the libhandy update. See LP: #1964841

We are updating gnome-control-center to set the correct gsettings value
(below) when choosing a dark theme.

Workaround
--
If you want the fix to apply without logging out at any time, you can run
session-migration --file
/usr/share/session-migration/scripts/dark-theme-migration.sh

- This requires gsettings-desktop-schemas 42~rc-1ubuntu2 or higher
+ This requires gsettings-desktop-schemas 42~rc-1ubuntu3 or higher

Or you can run this command yourself instead
gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'

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

Title:
Add session migration for GNOME 42 dark theme

Status in gsettings-desktop-schemas package in Ubuntu:
Fix Committed
Status in gsettings-desktop-schemas source package in Jammy:
Fix Committed

Bug description:
Test Case
-
1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance
and choose Dark
2. Upgrade to Ubuntu 22.04 LTS
3. Log out then log back in
4. Your apps should still be dark

Linked Issue

That test case is broken by the libhandy update. See LP: #1964841

We are updating gnome-control-center to set the correct gsettings
value (below) when choosing a dark theme.

Workaround
--
If you want the fix to apply without logging out at any time, you can run
session-migration --file
/usr/share/session-migration/scripts/dark-theme-migration.sh

This requires gsettings-desktop-schemas 42~rc-1ubuntu3 or higher

Or you can run this command yourself instead
gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1965189/+subscriptions

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

[Touch-packages] [Bug 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

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

Title:
  apt-add-repository requires --login for private repos, breaking
  automated workflows

Status in software-properties package in Ubuntu:
  New

Bug description:
  On Focal, in an automated environment (such as a launchpad builder), a
  used can do the following workflow:

  curl
  "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
  --output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu focal main"

  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
  Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
  Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 
Packages [3288 B] 
  Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main 
Translation-en [1892 B]  

  However, on Jammy, I get the following:

  
  curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT}; 
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu jammy main"

  Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, 
in lpppa
  self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 
592, in __call__
  response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
429, in _request
  raise error
  lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
  Response headers:
  ---
  -content-encoding: gzip
  content-length: 91
  content-type: text/plain;charset=utf-8
  date: Wed, 16 Mar 2022 19:54:16 GMT
  server: gunicorn/19.8.1
  status: 404
  vary: Accept-Encoding
  x-powered-by: Zope (www.zope.org), Python (www.python.org)
  x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
  x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
  ---
  Response body:
  ---
  b"Object: , 
name: '$REPO'"
  ---

  
  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
  self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
  if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, 
in description
  return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, 
in lpppa
  raise ShortcutException(msg)
  softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa 
'$REPO/proposed' not found (use --login if private)

  Impish similarly breaks. Digging through changelogs, I see various
  entries in Impish forward, starting with version 0.99.0 where a
  refactor was done.

  using `--login` is not possible in an automated setup (such as a
  builder) as it starts an OAuth dance, which requires human
  interaction. this will break existing automation utilizing apt-add-
  repository for users when migrating to Jammy

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


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

[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42

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

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

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with
  linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

  The "tests-in-lxd" testcase is failing with all kernels in Impish:

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service snap-lxd-22662.mount 
---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
   journal for failed service snap-snapd-15177.mount ---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
  FAIL
  [...]
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []

  First list contains 2 additional elements.
  First extra element 0:
  'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'

  + []
  - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
  -  '22662',
  -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
  -  '15177']

  
  This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:

  "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

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


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

[Touch-packages] [Bug 1618522] Re: netplan does not generates .network files just for ethernet

** Tags removed: rls-jj-incoming
** Tags added: rls-kk-incoming

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

Title:
  netplan does not generates .network files just for ethernet

Status in netplan.io package in Ubuntu:
  Triaged
Status in nplan package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  On my pi3 I have an image with the ubuntu-core snap rev 354 and I get
  the following netplan configuration file after the first boot:

  ubuntu@localhost:~$ cat /etc/netplan/00-initial-config.yaml
  network:
   version: 2
   ethernets:
     all:
  match:
   name: "*"
  dhcp4: true

  This generates the following .networkd file

  ubuntu@localhost:~$ cat /run/systemd/network/10-netplan-all.network
  [Match]
  Name=*

  [Network]
  DHCP=ipv4

  If I look now at the output of networkctl I see it also tries to
  manage my mlan0 device which is a WiFi one and should be managed
  according to the netplan rule:

  ubuntu@localhost:~$ networkctl
  IDX LINK TYPE   OPERATIONAL SETUP
    1 lo   loopback   carrier configured
    5 eth1 ether  no-carrier  configuring
    6 eth0 ether  routableconfigured
    7 mlan0wlan   no-carrier  configuring

  In summary, the networkd generator inside netplan currently does not
  limit the generated .network file to tell networkd to only look at
  ethernet devices but rather tell it to control every device available
  on the system.

  Expectation: Specifying a wildcard rule in a netplan configuration
  file for ethernet devices should tell the configured networking system
  to only consider ethernet devices and nothing else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1618522/+subscriptions


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

[Touch-packages] [Bug 1963767] Re: Microphone not working after suspend

2022-03-17 Thread Nazar Mokrynskyi

Yeah, situation on this laptop is very problematic. It loses microphone
audio all of a sudden often on its own (I unmute myself on Google Meet
and notice there is no audio from me).

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

Title:
  Microphone not working after suspend

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1965189] Re: Add session migration for GNOME 42 dark theme

2022-03-17 Thread Jeremy Bicha

** Changed in: gsettings-desktop-schemas (Ubuntu Jammy)
Status: In Progress => Fix Committed

** Description changed:

Test Case
-
1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance
and choose Dark
2. Upgrade to Ubuntu 22.04 LTS
- 3. Your apps should still be dark
+ 3. Log out then log back in
+ 4. Your apps should still be dark

Linked Issue

That test case is broken by the libhandy update. See LP: #1964841

We are updating gnome-control-center to set the correct gsettings value
(below) when choosing a dark theme.

- Implementation
- --
- We need to set gsettings org.gnome.desktop.interface color-scheme
'prefer-dark' for users using a theme name ending in "-dark"
+ Workaround
+ --
+ If you want the fix to apply without logging out at any time, you can run
+ session-migration --file
/usr/share/session-migration/scripts/dark-theme-migration.sh

- That gsettings schema is provided by gsettings-desktop-schemas.
+ This requires gsettings-desktop-schemas 42~rc-1ubuntu2 or higher

- I don't think we should do this in ubuntu-settings because there are
- people using GTK desktops that don't have ubuntu-settings installed.
-
- I suggest we use dh-migrations/session-migration to do this from gnome-
- settings-daemon.
-
- Let me know now if there is a better place for this.
+ Or you can run this command yourself instead
+ gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'

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

Title:
Add session migration for GNOME 42 dark theme

Status in gsettings-desktop-schemas package in Ubuntu:
Fix Committed
Status in gsettings-desktop-schemas source package in Jammy:
Fix Committed

Linked Issue

That test case is broken by the libhandy update. See LP: #1964841

We are updating gnome-control-center to set the correct gsettings
value (below) when choosing a dark theme.

Workaround
--
If you want the fix to apply without logging out at any time, you can run
session-migration --file
/usr/share/session-migration/scripts/dark-theme-migration.sh

This requires gsettings-desktop-schemas 42~rc-1ubuntu2 or higher

Or you can run this command yourself instead
gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1965189/+subscriptions

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

[Touch-packages] [Bug 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows

2022-03-17 Thread John Chittum

** Tags added: rls-jj-incoming

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

Title:
  apt-add-repository requires --login for private repos, breaking
  automated workflows

Status in software-properties package in Ubuntu:
  New

Bug description:
  On Focal, in an automated environment (such as a launchpad builder), a
  used can do the following workflow:

  curl
  "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
  --output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu focal main"

  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
  Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
  Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 
Packages [3288 B] 
  Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main 
Translation-en [1892 B]  

  However, on Jammy, I get the following:

  
  curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT}; 
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu jammy main"

  Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, 
in lpppa
  self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 
592, in __call__
  response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
429, in _request
  raise error
  lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
  Response headers:
  ---
  -content-encoding: gzip
  content-length: 91
  content-type: text/plain;charset=utf-8
  date: Wed, 16 Mar 2022 19:54:16 GMT
  server: gunicorn/19.8.1
  status: 404
  vary: Accept-Encoding
  x-powered-by: Zope (www.zope.org), Python (www.python.org)
  x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
  x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
  ---
  Response body:
  ---
  b"Object: , 
name: '$REPO'"
  ---

  
  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
  self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
  if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, 
in description
  return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, 
in lpppa
  raise ShortcutException(msg)
  softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa 
'$REPO/proposed' not found (use --login if private)

  Impish similarly breaks. Digging through changelogs, I see various
  entries in Impish forward, starting with version 0.99.0 where a
  refactor was done.

  using `--login` is not possible in an automated setup (such as a
  builder) as it starts an OAuth dance, which requires human
  interaction. this will break existing automation utilizing apt-add-
  repository for users when migrating to Jammy

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


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

[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42

2022-03-17 Thread Dimitri John Ledkov

** Tags added: rls-ii-incoming

** Tags added: rls-jj-incoming

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with
  linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

  The "tests-in-lxd" testcase is failing with all kernels in Impish:

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service snap-lxd-22662.mount 
---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
   journal for failed service snap-snapd-15177.mount ---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
  FAIL
  [...]
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []

  First list contains 2 additional elements.
  First extra element 0:
  'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'

  + []
  - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
  -  '22662',
  -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
  -  '15177']

  
  This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:

  "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

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


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

[Touch-packages] [Bug 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()

2022-03-17 Thread Bug Watch Updater

** Changed in: libusb
   Status: New => Fix Released

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

Title:
  fprintd crashed with SIGSEGV in log_v() from usbi_log() from
  libusb_unref_device()

Status in libusb:
  Fix Released
Status in fprintd package in Ubuntu:
  Won't Fix
Status in libusb package in Ubuntu:
  Fix Committed

Bug description:
  +

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.1-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Feb  7 21:58:32 2022
  ExecutablePath: /usr/libexec/fprintd
  InstallationDate: Installed on 2021-12-21 (50 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: /usr/libexec/fprintd
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7fd8a7a3855f:call   *%rax
   PC (0x7fd8a7a3855f) ok
   source "*%rax" (0xd86d54af5d1db0f9) not located in a known VMA region 
(needed readable region)!
   destination "(%rsp)" (0x7ffdceacc590) ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: fprintd
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   libusb_unref_device () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgusb.so.2
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: fprintd crashed with SIGSEGV in libusb_unref_device()
  UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago)
  UserGroups: N/A
  separator:

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


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

[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

I see your point; my suggestion here is to file a bug upstream with your
findings:

  https://github.com/WayneD/rsync/issues

I don't think this should be tackled on the Ubuntu side, especially
given that the issue is really minor and unlikely to affect a
significant amount of users. As you say what changed is a double-
verbosity info message with no promise of stability, the actual behavior
of rsync is correct.

If you file a bug upstream please mention it here, we'll track it and
once fixed we'll consider applying the fix to the supported Ubuntu
releases. Thanks!


** Changed in: rsync (Ubuntu)
   Importance: Undecided => Low

** Changed in: rsync (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1965189] Re: Add session migration for GNOME 42 dark theme

2022-03-17 Thread Jeremy Bicha

Since it's gsettings-desktop-schemas that provides the new schema, Seb
suggested we just add the migration there directly. Thanks!

** Package changed: gnome-settings-daemon (Ubuntu Jammy) => gsettings-
desktop-schemas (Ubuntu Jammy)

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

Title:
  Add session migration for GNOME 42 dark theme

Status in gsettings-desktop-schemas package in Ubuntu:
  In Progress
Status in gsettings-desktop-schemas source package in Jammy:
  In Progress

Bug description:
  Test Case
  -
  1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance 
and choose Dark
  2. Upgrade to Ubuntu 22.04 LTS
  3. Your apps should still be dark

  Linked Issue
  
  That test case is broken by the libhandy update. See LP: #1964841

  We are updating gnome-control-center to set the correct gsettings
  value (below) when choosing a dark theme.

  Implementation
  --
  We need to set gsettings org.gnome.desktop.interface color-scheme 
'prefer-dark' for users using a theme name ending in "-dark"

  That gsettings schema is provided by gsettings-desktop-schemas.

  I don't think we should do this in ubuntu-settings because there are
  people using GTK desktops that don't have ubuntu-settings installed.

  I suggest we use dh-migrations/session-migration to do this from
  gnome-settings-daemon.

  Let me know now if there is a better place for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1965189/+subscriptions


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

[Touch-packages] [Bug 1965189] [NEW] Add session migration for GNOME 42 dark theme

2022-03-17 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Test Case
-
1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance and 
choose Dark
2. Upgrade to Ubuntu 22.04 LTS
3. Your apps should still be dark

Linked Issue

That test case is broken by the libhandy update. See LP: #1964841

We are updating gnome-control-center to set the correct gsettings value
(below) when choosing a dark theme.

Implementation
--
We need to set gsettings org.gnome.desktop.interface color-scheme 'prefer-dark' 
for users using a theme name ending in "-dark"

That gsettings schema is provided by gsettings-desktop-schemas.

I don't think we should do this in ubuntu-settings because there are
people using GTK desktops that don't have ubuntu-settings installed.

I suggest we use dh-migrations/session-migration to do this from gnome-
settings-daemon.

Let me know now if there is a better place for this.

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: High
 Assignee: Jeremy Bicha (jbicha)
 Status: In Progress

** Affects: gsettings-desktop-schemas (Ubuntu Jammy)
 Importance: High
 Assignee: Jeremy Bicha (jbicha)
 Status: In Progress


** Tags: jammy
-- 
Add session migration for GNOME 42 dark theme
https://bugs.launchpad.net/bugs/1965189
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu.

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

[Touch-packages] [Bug 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2022-03-17 Thread Bug Watch Updater

** Changed in: firefox
   Status: New => Expired

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  Expired
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Incomplete
Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-03-17 Thread Ian! D. Allen

I am not arguing about the behaviour, which is correct and apparently hasn't 
changed.
I'm complaining about the unannounced change in message from "is uptodate" to 
"is newer".

Three problems:

1. The message "is newer" is an unannounced change from all previous
versions of rsync that say "is uptodate".  My scripts that look for "is
newer" are all broken, because now every file is flagged as newer, even
when the file is not newer.

2. I expect that a name flagged as "is newer" will be transferred when I
remove the --update option, and that does not happen because the file is
*NOT* newer; the message is wrong and no transfer happens.

3. The message changes with and without the --update option.  If rsync
says "is uptodate" without the --update option, why does that change to
"is newer" when you add the option?  Either the file is newer *OR* it is
uptodate; it can't be both.  Adding the --update option should not
change "is uptodate" to "is newer".  It is not newer; don't say it is.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

2022-03-17 Thread Łukasz Zemczak

Thank you for the detailed explanation Fabio, the impact of the bug is
now much better understood. Can I ask for an update of the Impact field
in the SRU description above? In a summary, but also getting into a bit
more details about how this differs from focal+ etc.

One thing I worry about in this SRU is basically what has been mentioned by Ben 
Hutchings as a follow up to the patch forwarded upstream:
https://lists.zytor.com/archives/klibc/2021-December/004635.html

I worry that since this issue in ipconfig has been around for *so long* that 
people could have actually started depending on the behavior being as-is. I 
don't think klibc's ipconfig is too widely used (as klibc-utils only has like 2 
reverse-dependencies), but it's still something to consider.
I think I'm not generally against this SRU. Similar to Robie I would like some 
regression potential analysis done and included in the [Where problems could 
occur] section - one of them being what I mentioned above. Can you think of any 
other issues this change could cause? In integration or in different parts of 
the code? Can we mitigate this somehow by performing some additional testing?

If you could modify the two sections of the SRU description, I'd be
ready to accept this into bionic-proposed.

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

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  Incomplete

Bug description:
  
  [Impact]
  In some cases, ipconfig can take a longer time than the user-specified 
timeouts, causing unexpected delays.

  [Test Plan]
  Any situation where ipconfig encounters an error sending the DHCP packet, it 
will automatically set a delay of 10 seconds, which could be longer than the 
user-specified timeout. It can be reproduced by creating a dummy interface and 
attempting to run ipconfig on it with a timeout value of less than 10:

  # ip link add eth1 type dummy
  # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
  Thu Nov 18 04:46:13 EST 2021
  IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  Thu Nov 18 04:46:23 EST 2021

  ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
  timestamps show an actual delay of 10 seconds.

  [Where problems could occur]
  Please see reproduction steps above. We are seeing this in production too 
(see comment #2).

  [Other Info]
  A patch to fix the issue is being proposed here. It is a safe fix - it only 
checks before going into sleep that the timeout never exceeds the 
user-requested value.

  [Original Description]

  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  This can happen at any time during the main event loop, which can end
  up extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:

  if (loop_timeout >= 0 &&
  now.tv_sec - start >= loop_timeout) {
  printf("IP-Config: no response after %d "
     "secs - giving up\n", loop_timeout);
  rc = -1;
  goto bail;
  }

  'loop_timeout' is the user-specified time-out. With a value of 2, in
  case of error, this line prints:

  IP-Config: no response after 2 secs - giving up

  So it thinks that it waited 2 seconds - however, in reality it had
  actually waited for 10 seconds.

  The suggested code-change ensures that the timeout that is actually
  used never exceeds the user-specified

[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

Hello Ian and thanks for this bug report. My question here is: is this
actually a bug?

The manpage for --update says:

  This forces rsync to skip any files which exist on the destination
  and have a modified time that is newer

It seems sensible to me to make this a '>=' comparison, and not a strict
'>' comparison: when considering modification times there's no need to
update a file which has the same timestamp of the source file.

In other words: I fail to see the problem here. Could you please
elaborate a bit more? Thanks!

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

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42

2022-03-17 Thread Kleber Sacilotto de Souza

** Summary changed:

- systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42
+ systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with 
linux/5.13.0-37.42

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with
  linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

  The "tests-in-lxd" testcase is failing with all kernels in Impish:

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service snap-lxd-22662.mount 
---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
   journal for failed service snap-snapd-15177.mount ---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
  FAIL
  [...]
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []

  First list contains 2 additional elements.
  First extra element 0:
  'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'

  + []
  - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
  -  '22662',
  -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
  -  '15177']

  
  This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:

  "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

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


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

[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42

2022-03-17 Thread Kleber Sacilotto de Souza

** Description changed:

  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be determined.
  
  Testing failed on:
- amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
- arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
- ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
- s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz
+ amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
+ arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
+ ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
+ s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz
+ 
+ The "tests-in-lxd" testcase is failing with all kernels in Impish:
+ 
+ test_no_failed (__main__.ServicesTest)
+ No failed units ...  journal for failed service snap-lxd-22662.mount 
---
+ -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
+  journal for failed service snap-snapd-15177.mount ---
+ -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
+ Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
+ FAIL
+ [...]
+ ==
+ FAIL: test_no_failed (__main__.ServicesTest)
+ No failed units
+ --
+ Traceback (most recent call last):
+   File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
+ self.assertEqual(failed, [])
+ AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []
+ 
+ First list contains 2 additional elements.
+ First extra element 0:
+ 'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'
+ 
+ + []
+ - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
+ -  '22662',
+ -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
+ -  '15177']
+ 
+ 
+ This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:
+ 
+ "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
+ 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with
  linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64:

[Touch-packages] [Bug 1965293] Missing required logs.

2022-03-17 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1965293

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

  The "tests-in-lxd" testcase is failing with all kernels in Impish:

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service snap-lxd-22662.mount 
---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
   journal for failed service snap-snapd-15177.mount ---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
  FAIL
  [...]
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []

  First list contains 2 additional elements.
  First extra element 0:
  'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'

  + []
  - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
  -  '22662',
  -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
  -  '15177']

  
  This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:

  "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

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

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1965293] [NEW] systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42

2022-03-17 Thread Kleber Sacilotto de Souza

Public bug reported:

This is a scripted bug report about ADT failures while running systemd
tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.

Testing failed on:
amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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

** Affects: linux (Ubuntu Impish)
 Importance: Undecided
 Status: Incomplete

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

** Also affects: systemd (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

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


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

[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

Hello Barto,

If I understand it correctly you can create working images using 20.04
ISOs *right now*, but with the exact same tooling images created with
20.04.x ISOs do not work. I think you have been clear about this, but it
is of course very important to know that the only moving part is the ISO
image.

Given that you have console access to the machine, at least for a few
minutes before Virtualbox tears it down, can you please share the output
of the following commands?

 - ip addr
 - systemctl status
 - systemctl status ssh

My wild guess here is that for some reason the 20.04.x images get a
different Ethernet interface name (you hardcoded ens33 in cloud-config).

Also: can you login from the machine to itself (ssh mclibre@127.0.0.1)?

Also: can you share the contents of /etc/dhcp/dhclient.conf and
/etc/netplan/00-installer-config.yaml?

Thank you.

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

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  New

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

The unsafe legacy disabled suggests it could be bug #1963834 and a
choice from upstream openssl to disable unsafe servers, maybe that's
something the eduroam admins need to sort out?

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  New

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1965008] Re: 'Software & Updates' crashes on tab 'Additional drivers'

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

** This bug has been marked a duplicate of bug 1964880
   software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'

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

Title:
  'Software & Updates' crashes on tab 'Additional drivers'

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Crash did not occur a couple of days ago.

  'sudo ubuntu-drivers list' has no problems listing the drivers.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 21:04:29 2022
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2022-02-26 (16 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4
  Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 
3.10.1-0ubuntu2
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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


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

[Touch-packages] [Bug 1901752] Re: Can’t connect to a specific Wi-Fi network with wpa_supplicant

Thank you for your bug report, do you have details on what sort of
configuration and security options is eduroam using?

Could you edit /lib/systemd/system/wpa_supplicant.service to add a '-d'
to the ExecStart cmd, restart, try to connect and share the 'journalctl
-b 0' log from the system?


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

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

Title:
  Can’t connect to a specific Wi-Fi network with wpa_supplicant

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  This is the error I get if I try to connect to a specific Wi-Fi
  network on Ubuntu 20.10 with wpa_supplicant:

  Error: Connection activation failed: (7) Secrets were required, but
  not provided.

  If I use iwd instead, everything works fine.

  I also can connect to other networks with wpa_supplicant.

  I had the same issue with the Live USB.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: wpasupplicant 2:2.9-1ubuntu8
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: i3
  Date: Tue Oct 27 20:55:39 2020
  InstallationDate: Installed on 2020-10-26 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy

Could you try if that's an issue under GNOME? There is a similar report
on https://forum.endeavouros.com/t/wpa3-networkmanager-plasma-nm-
weirdness/10439 which suggests it could be an issue with plasma

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

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

Title:
  Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to connect to an open (i.e. no ecryption) WLAN with
  network-manager 1.36.0-1ubuntu2 on 22.04 but it's failing with the
  following error message (after selecting the network from the network-
  manager applet prompt):

  Mär 08 10:50:04 Isaac-Laptop NetworkManager[31754]: 
  [1646733004.4425] audit: op="connection-add-activate" pid=12122
  uid=1000 result="fail" reason="802-11-wireless-security.key-mgmt:
  Access point does not support PSK but setting requires it"

  I haven't changed any of the default settings for network-manager and
  this network worked on 20.04.

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


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

[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

bug #1958267 is also a similar issue

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-02-27T21:07:16.553410

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

bug #1962541 seems a bit similar though the log here includes

> OpenSSL: openssl_handshake - SSL_connect error:0A000152:SSL
routines::unsafe legacy renegotiation disabled

I've reported it upstream now on
http://lists.infradead.org/pipermail/hostap/2022-March/040305.html

** Tags added: openssl3

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  New

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

Thanks for the Debug log, I reported the issue upstream now on
http://lists.infradead.org/pipermail/hostap/2022-March/040304.html

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-02-27T21:07:16.553410

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


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

[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

** Package changed: network-manager (Ubuntu) => wpa (Ubuntu)

** Changed in: wpa (Ubuntu)
   Status: Incomplete => Triaged

** Tags added: rls-jj-incoming

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-02-27T21:07:16.553410

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


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

[Touch-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.

The logs aren't really going to help there, we need someone having the
issue to run the cmd from #10, the one in comment #12 doesn't show the
issue so it was not done in an environment showing the problem

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

Title:
  When we install ModemManager1.16.6 and others, this will lead to
  ubuntu can not enter into GNOME UI.

Status in modemmanager package in Ubuntu:
  Incomplete

Bug description:
  1. We use sourcecode to install ModemManger1.16.6
  2. Ubuntu can not enter UI.
  3. We capture log and picture and add these on the attachment.

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


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

[Touch-packages] [Bug 1965281] [NEW] dpkg: error: le format de la base de données d'informationE: Sub-process /usr/bin/dpkg returned an error code (2)

2022-03-17 Thread Kanda Geedoo

Public bug reported:

dpkg: error: le format de la base de données d'informations (2) est
incorrect ou trop récent ; vous devriez essayer d'utiliser une version
plus récente de dpkg

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: base-files 11ubuntu5.4
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Mar 16 20:35:18 2022
ErrorMessage: le sous-processus new pre-installation script a retourné une 
erreur de sortie d'état 1
InstallationDate: Installed on 2021-12-29 (77 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: base-files
Title: package base-files 11ubuntu5.4 failed to install/upgrade: le 
sous-processus new pre-installation script a retourné une erreur de sortie 
d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  dpkg: error: le format de la base de données d'informationE: Sub-
  process /usr/bin/dpkg returned an error code (2)

Status in base-files package in Ubuntu:
  New

Bug description:
  dpkg: error: le format de la base de données d'informations (2) est
  incorrect ou trop récent ; vous devriez essayer d'utiliser une version
  plus récente de dpkg

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: base-files 11ubuntu5.4
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 16 20:35:18 2022
  ErrorMessage: le sous-processus new pre-installation script a retourné une 
erreur de sortie d'état 1
  InstallationDate: Installed on 2021-12-29 (77 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: base-files
  Title: package base-files 11ubuntu5.4 failed to install/upgrade: le 
sous-processus new pre-installation script a retourné une erreur de sortie 
d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.

2022-03-17 Thread LeoLin

Hi @Sebastien Bacher, could you help to check logs from DengYi provided
then kindly reply some suggestion?

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

Title:
  When we install ModemManager1.16.6 and others, this will lead to
  ubuntu can not enter into GNOME UI.

Status in modemmanager package in Ubuntu:
  Incomplete

Bug description:
  1. We use sourcecode to install ModemManger1.16.6
  2. Ubuntu can not enter UI.
  3. We capture log and picture and add these on the attachment.

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


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

[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"

2022-03-17 Thread Michael Vogt

** Changed in: shadow (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: shadow (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  [SRU] Please support group manipulation with "extrausers"

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Bionic:
  In Progress
Status in shadow source package in Focal:
  In Progress
Status in shadow source package in Impish:
  Won't Fix
Status in shadow source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  * In order to use the microk8s snap in Ubuntu Core, one currently
  needs to be root. This is far from optimal, since normally (on desktop
  and server installations) this is not necessary.

  * This make it hard to provide consistent documentation on microk8s
  across all supported device, if we have to take the "sudo" command
  into account, and how file permissions for generated files might be
  affected.

  
  [Test Plan]

  The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps
  are as following (replace "" with the actual path of your
  Ubuntu Core image file:

  qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \
  -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \
  -device virtio-net-pci,netdev=mynet0 \
  -drive file=,format=raw

  After configuring your account, connect to youd device via SSH:

  ssh @localhost -p 8022

  And issue these commands

  sudo snap install microk8s --channel=latest/edge/stable

  # microk8s is going to eat up all your disk space, so stop it as soon
  # as the prompt comes back:
  sudo microk8s stop

  # Add your user to the microk8s group
  sudo usermod -G snap_microk8s $(whoami)

  The last command will fail unless this bug is fixed. If the bug is
  fixed, the command will succeed, and after logging out and in again,
  you can verify that you've been added to the snap_microk8s group by
  running the "groups" command.

  
  [Where problems could occur]

  * The patch only touches error code paths and adds a fallback
  mechanism in them. Therefore, "normal" operations, where these
  commands would have succeeded before, will not be affected at all.

  * In those cases when usermod fails because it failed to find or load
  the requested user/group, we reset the user/group database paths to
  our writable user/group databases, and retry the operation. Note that
  the path for our database is hardcoded in the program source, so the
  security risk seems contained. We do not add additional command-line
  parameters.

  
  [Other Info]

  Original bug description
  

  Currently doing something like:

  sudo usermod -a -G snap_microk8s dbeamonte

  on a Ubuntu Core system will fail with

  usermod: /etc/group.15965: Read-only file system

  This is because the existing usermod patches to detect
  the extrausers file do not cover this case. Attached
  a simple patch that enables it. I will give this patch
  a test run in our image PPA for jammy and if things look
  good I would like upload to 22.04 and SRU for 20.04 and
  18.04.

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


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

[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2022-03-17 Thread Alex Tu

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

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


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

[Touch-packages] [Bug 1905022] Re: [22.04 FEAT] Upgrade OpenSSL to version 3.0

** Information type changed from Private to Public

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

Title:
  [22.04 FEAT] Upgrade OpenSSL to version 3.0

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Upgrade OpenSSL to version 3.0.
  At this point in time, Alpha 8 is available, see https://www.openssl.org/.

  Just in case this package will make the deadline.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1905022/+subscriptions


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

[Touch-packages] [Bug 1959407] Re: [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware - GDB Part

** Information type changed from Private to Public

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

Title:
  [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware - GDB Part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  BINUTILS: Support for new IBM Z Hardware

  This request will track the inclusion of the patches for this feature
  in GDB to provide the GDB disassembler support for the new
  instructions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959407/+subscriptions


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

[Touch-packages] [Bug 1959408] Re: [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware

** Information type changed from Private to Public

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

Title:
  [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  BINUTILS: Support for new IBM Z Hardware

  Upstream target: binutils = 2.37

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959408/+subscriptions


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

[Touch-packages] [Bug 1959463] Re: [22.04 FEAT] Upgrade binutils to latest version

** Information type changed from Private to Public

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

Title:
  [22.04 FEAT] Upgrade binutils to latest version

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  Upgrade binutils to latest version

  Description:
  Update binutils to latest version (2.37)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959463/+subscriptions


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

[Touch-packages] [Bug 1885990] Re: server: Match has no effect in include file (upstream 3122)

2022-03-17 Thread Patel

@seth arnold
THanks for the link, quite interesting. Unfortunately perusing it, I found that 
this particular change ticks almost all the wrong boxes - especially the 'do 
not touch really important software' (aka  critical infrastructure packages).

Also trying to find a contact is not obvious, there is a ref
(https://wiki.ubuntu.com/StableReleaseUpdates#Reviewing_procedure_and_tools)
to a ubuntu-bugs channel on freenode that don't seem to exist anymore.
Provided examples are almost 15 years old. Chances are good (or bad)
that many of this is not up-to-date.

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

Title:
  server: Match has no effect in include file (upstream 3122)

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Hello

  Ubuntu version: focal 20.04 LTS
  Version:
  openssh-server:
Installed: 1:8.2p1-4ubuntu0.1
Candidate: 1:8.2p1-4ubuntu0.1
  Expected: match statement in included files work as documented in the fine 
manual
  What happens: the statements are ignored.

  
  If you add Match statements in an included file, it will generate no error 
but have no effect.
  The exact same statements work in the main server config file 
(/etc/ssh/sshd_config)

  this is to track upstream bug 3122:

  https://bugzilla.mindrot.org/show_bug.cgi?id=3122

  it's fixed but will only be in 8.4 so it affects Ubuntu 20.04 LTS
  where openssh is at 8.2.

  I'm not *absolutely* whining for a backport since include files is a
  new feature for openssl in focal so it's not a regression. Would be
  nice though :),  because include files are standard for any server
  software in Linux since at least a decade...

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


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

[Touch-packages] [Bug 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()