[Touch-packages] [Bug 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04

[Simon Chopin]

@suoko: could you retry with the current version from jammy (22.04)? The
Qt packages have been updated a couple of weeks ago with better OpenSSL
3 support, which hopefully fixes your issue?

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  New

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1947588] Re: Infinite Loop in OpenSSL s_server

[Simon Chopin]

Hi Matt, thanks for taking the time to report this, as well as
investigating the different versions that might be affected.

I just checked, and both Impish and Jammy are affected as well (the
latter using OpenSSL 3.0).

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Impish:
  New
Status in openssl source package in Jammy:
  New

Bug description:
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j  16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options:  bn(64,64) rc4(16x,int) des(int) blowfish(ptr) 
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
  ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
  Seeding source: os-specific

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


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

[Touch-packages] [Bug 1947588] Re: Infinite Loop in OpenSSL s_server

[Simon Chopin]

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Impish:
  New
Status in openssl source package in Jammy:
  New

Bug description:
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j  16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options:  bn(64,64) rc4(16x,int) des(int) blowfish(ptr) 
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
  ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
  Seeding source: os-specific

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


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

[Touch-packages] [Bug 1947588] Re: Infinite Loop in OpenSSL s_server

[Simon Chopin]

** Also affects: openssl (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: openssl (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1947588

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Impish:
  New
Status in openssl source package in Jammy:
  New

Bug description:
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j  16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options:  bn(64,64) rc4(16x,int) des(int) blowfish(ptr) 
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
  ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
  Seeding source: os-specific

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


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

[Touch-packages] [Bug 1947588] Re: Infinite Loop in OpenSSL s_server

[Simon Chopin]

Disregard the (now deleted) comment regarding Focal, I got mixed up in
my terminals. Focal is affected, but Bionic is not.

I suspect this is caused by our patch that changes the semantics of
security level 2 to also drop support for (D)TLS < 1.2.

** Tags added: rls-ff-incoming rls-jj-incoming

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

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

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

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Focal:
  Confirmed
Status in openssl source package in Impish:
  Confirmed
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j  16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options:  bn(64,64) rc4(16x,int) des(int) blowfish(ptr) 
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
  ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
  Seeding source: os-specific

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


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

[Touch-packages] [Bug 1940715] Re: systemd-resolved restricts edns0 advertised max size to 512

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-resolved restricts edns0 advertised max size to 512

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Confirmed

Bug description:
  [impact]

  when talking to upstream nameservers, systemd-resolved limits its
  advertised max packet size as 512 in its edns0 opt. However, one of
  the primary benefits of edns0 is to allow using packet sizes larger
  than 512, which is the pre-edns0 max packet size.

  this results in systemd-resolved failing to handle responses larger
  than 512 with udp/edns0, and having to fall back to tcp. This is not
  optimal (since tcp dns imposes significantly higher overhead) and may
  even cause failures, if a firewall allows udp dns but blocks tcp dns
  traffic.

  [test case]

  enable debug logging in systemd-resolved, with 'sudo systemctl edit
  systemd-resolved' and then add:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  then save that file and restart systemd-resolved (or reboot).

  Make sure to flush the cache and reset server features before
  reproducing:

  $ sudo resolvectl flush-caches
  $ sudo resolvectl reset-server-features

  Lookup 'toomany.ddstreet.org' and check systemd-resolved logs to see
  if it used TCP fallback or not:

  ...
  Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Reply truncated, retrying 
via TCP.
  ...
  Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Verified we get a 
response at feature level TCP from DNS server 10.202.51.1.
  Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Added positive 
unauthenticated cache entry for toomany.ddstreet.org IN A 1799s on 
eth0/INET/10.202.51.1

  A correct lookup using larger EDNS0 response size looks like:

  ...
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using feature level 
UDP+EDNS0 for transaction 43808.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using DNS server 
10.202.51.1 for transaction 43808.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Announcing packet size 
1472 in egress EDNS(0) packet.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Emitting UDP, link MTU is 
1500, socket MTU is 0, minimal MTU is 40
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Sending query packet with 
id 43808 of size 49.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing query...
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Received dns UDP packet of 
size 689, ifindex=131, ttl=0, fragsize=0
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing incoming packet 
of size 689 on transaction 43808 (rcode=SUCCESS).
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Added positive 
unauthenticated non-confidential cache entry for toomany.ddstreet.org IN A 
1175s on eth0/INET/10.202.51.1
  ...

  [regression potential]

  failure to correctly look up dns records, or other problems while
  performing dns lookups with systemd-resolved

  [scope]

  this is needed for all releases

  this still needs fixing upstream:
  https://github.com/systemd/systemd/pull/20528

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


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

[Touch-packages] [Bug 1940715] Re: systemd-resolved restricts edns0 advertised max size to 512

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-resolved restricts edns0 advertised max size to 512

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Confirmed

Bug description:
  [impact]

  when talking to upstream nameservers, systemd-resolved limits its
  advertised max packet size as 512 in its edns0 opt. However, one of
  the primary benefits of edns0 is to allow using packet sizes larger
  than 512, which is the pre-edns0 max packet size.

  this results in systemd-resolved failing to handle responses larger
  than 512 with udp/edns0, and having to fall back to tcp. This is not
  optimal (since tcp dns imposes significantly higher overhead) and may
  even cause failures, if a firewall allows udp dns but blocks tcp dns
  traffic.

  [test case]

  enable debug logging in systemd-resolved, with 'sudo systemctl edit
  systemd-resolved' and then add:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  then save that file and restart systemd-resolved (or reboot).

  Make sure to flush the cache and reset server features before
  reproducing:

  $ sudo resolvectl flush-caches
  $ sudo resolvectl reset-server-features

  Lookup 'toomany.ddstreet.org' and check systemd-resolved logs to see
  if it used TCP fallback or not:

  ...
  Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Reply truncated, retrying 
via TCP.
  ...
  Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Verified we get a 
response at feature level TCP from DNS server 10.202.51.1.
  Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Added positive 
unauthenticated cache entry for toomany.ddstreet.org IN A 1799s on 
eth0/INET/10.202.51.1

  A correct lookup using larger EDNS0 response size looks like:

  ...
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using feature level 
UDP+EDNS0 for transaction 43808.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using DNS server 
10.202.51.1 for transaction 43808.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Announcing packet size 
1472 in egress EDNS(0) packet.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Emitting UDP, link MTU is 
1500, socket MTU is 0, minimal MTU is 40
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Sending query packet with 
id 43808 of size 49.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing query...
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Received dns UDP packet of 
size 689, ifindex=131, ttl=0, fragsize=0
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing incoming packet 
of size 689 on transaction 43808 (rcode=SUCCESS).
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Added positive 
unauthenticated non-confidential cache entry for toomany.ddstreet.org IN A 
1175s on eth0/INET/10.202.51.1
  ...

  [regression potential]

  failure to correctly look up dns records, or other problems while
  performing dns lookups with systemd-resolved

  [scope]

  this is needed for all releases

  this still needs fixing upstream:
  https://github.com/systemd/systemd/pull/20528

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


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

[Touch-packages] [Bug 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]

[Simon Chopin]

To be clear, the root issue is that the server is using an outdated,
insecure protocol that has been deemed so for more than a decade, and
OpenSSL finally decided to disable it by default. The "proper" way to
fix this would be for them to upgrade.

Now, that being said, we live in the real world and our users probably
don't have the power to make this decision.

I really don't understand why the upstream Python PR has been closed,
it'd have made our lives easier. We *could* carry the patch in our
Python 3.10 package, but that's just moving the problem, as our more
technical users would have this escape hatch but the others would still
be left out.

I'll get in touch with OpenSSL upstream to see if it's conceivable to
expose this flag as a configuration option.

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

Title:
  openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]

Status in openssl package in Ubuntu:
  New

Bug description:
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
   Table de version :
   *** 3.0.1-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  Using Ubuntu 22.04, I now get the following error message when
  attempting to connect to our office VPN using "gp-saml-gui
  (https://github.com/dlenski/gp-saml-gui)" :

  #
  dominique@Doombuntu:~$ .local/bin/gp-saml-gui  server_url
  Looking for SAML auth tags in response to 
https://server_url/global-protect/prelogin.esp...
  usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT] 
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f 
EXTRA] server [openconnect_extra ...]
  gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] 
unsafe legacy renegotiation disabled (_ssl.c:997)
  #
  #
  #

  gp-saml-gui uses python module requests.
  Using python ide, I can get the same results  :

  #
  >>> r = requests.get('https://server_url')
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, 
in urlopen
  httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382, 
in _make_request
  self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012, 
in _validate_conn
  conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in 
connect
  self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in 
ssl_wrap_socket
  ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in 
_ssl_wrap_socket_impl
  return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
  return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
  self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
  self._sslobj.do_handshake()
  ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy 
renegotiation disabled (_ssl.c:997)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in 
send
  resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, 
in urlopen
  retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in 
increment
  raise MaxRetryError(_pool, url, error or ResponseError(cause))
  urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url', 
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, 
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation 
disabled (_ssl.c:997)')))

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
  return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
  return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in 
request
  resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in 
send
  r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 

[Touch-packages] [Bug 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]

[Simon Chopin]

... And while looking for what exactly to suggest upstream, I realized
that GitHub search only prints out the first match in a given file,
which mean I missed the config options part of
https://www.openssl.org/docs/man3.0/man3/SSL_CONF_cmd_value_type.html
(search for UnsafeLegacyServerConnect), which, combined with
https://www.openssl.org/docs/man3.0/man5/config.html makes me think the
following snippet should work, assuming the Python modules actually
loads the config file:

[ssl_configuration]
 client = client_tls_config

 [client_tls_config]
 Options = UnsafeLegacyServerConnect

This is completely untested though :)

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

Title:
  openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]

Status in openssl package in Ubuntu:
  New

Bug description:
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
   Table de version :
   *** 3.0.1-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  Using Ubuntu 22.04, I now get the following error message when
  attempting to connect to our office VPN using "gp-saml-gui
  (https://github.com/dlenski/gp-saml-gui)" :

  #
  dominique@Doombuntu:~$ .local/bin/gp-saml-gui  server_url
  Looking for SAML auth tags in response to 
https://server_url/global-protect/prelogin.esp...
  usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT] 
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f 
EXTRA] server [openconnect_extra ...]
  gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] 
unsafe legacy renegotiation disabled (_ssl.c:997)
  #
  #
  #

  gp-saml-gui uses python module requests.
  Using python ide, I can get the same results  :

  #
  >>> r = requests.get('https://server_url')
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, 
in urlopen
  httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382, 
in _make_request
  self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012, 
in _validate_conn
  conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in 
connect
  self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in 
ssl_wrap_socket
  ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in 
_ssl_wrap_socket_impl
  return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
  return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
  self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
  self._sslobj.do_handshake()
  ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy 
renegotiation disabled (_ssl.c:997)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in 
send
  resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, 
in urlopen
  retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in 
increment
  raise MaxRetryError(_pool, url, error or ResponseError(cause))
  urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url', 
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, 
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation 
disabled (_ssl.c:997)')))

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
  return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
  return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in 
request
  resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in 
send
  r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in 
send
  raise SSLError(e, request=request)
  requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url', 
port=443): Max re

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

[Sebastien Bacher]

any chance you could provide the journal log requested?

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

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

Status in network-manager package in Ubuntu:
  Incomplete

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/network-manager/+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 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy

[Sebastien Bacher]

there were some recent fixes around owe on bug #1963906 but that's on a
GNOME session, unsure if that matches your issue?

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

-- 
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:
  New

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 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs

[Sebastien Bacher]

I would start by reinstalling libgail-common, restart and see if that
brings the issue back. I also think you can install the pending
upgrades, it shouldn't make a difference here

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

Title:
  segfault in libgtk-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

  Version of library is 2.24.32-4ubuntu4 and library file is dated
  2021-03-31 here.

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


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

[Touch-packages] [Bug 1903350] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: el subproceso instalado paquete lvm2 script post-installation devolvió el código de salida de error 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: el subproceso
  instalado paquete lvm2 script post-installation devolvió el código de
  salida de error 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Crash installing gnome-boxes on the terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov  6 16:33:17 2020
  ErrorMessage: el subproceso instalado paquete lvm2 script post-installation 
devolvió el código de salida de error 1
  InstallationDate: Installed on 2020-09-18 (48 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: lvm2
  Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: el subproceso 
instalado paquete lvm2 script post-installation devolvió el código de salida de 
error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[leonpano]

this file is full log 
beacause i dont want to try to upgrade and is not working

** Attachment added: "logfull.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+attachment/5567725/+files/logfull.log

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

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

Status in network-manager package in Ubuntu:
  Incomplete

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/network-manager/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Olivier Tilloy]

** Bug watch added: Debian Bug tracker #923345
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345

** Also affects: evince (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345
   Importance: Unknown
   Status: Unknown

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged
Status in evince package in Debian:
  Unknown

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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


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

[Touch-packages] [Bug 1963903] Re: expat relax fix for CVE-2022-25236 and possible regressions

[Launchpad Bug Tracker]

This bug was fixed in the package expat - 2.4.1-2ubuntu0.3

---
expat (2.4.1-2ubuntu0.3) impish-security; urgency=medium

  * SECURITY UPDATE: Stack exhaustion
- debian/patches/CVE-2022-25313.patch: prevent
  stack exhaustion in build_model in expat/lib/xmlparse.c.
- debian/patches/fix-build_model-regression.patch: fix build_model
  regression in expat/lib/xmlparse.c.
- debian/patches/protect-against-nested-element*: in expat/lib/xmlparse.
- CVE-2022-25313
  * SECURITY UPDATE: Integer overflow
- debian/patches/CVE-2022-25314.patch: prevent integer overflow in
  copyString in expat/lib/xmlparse.c.
- CVE-2022-25314
  * SECURITY UPDATE: Integer overflow
- debian/patches/CVE-2022-25315.patch: prevent integer overflow in
  storeRawNames in expat/lib/xmlparse.c.
- CVE-2022-25315
  * SECURITY UPDATE: relax fix to CVE-2022-25236 with regard to
RFC 3986 URI characters and possibly regressions
- debian/patches/CVE-2022-25236-3.patch: add a note on namespace URI
  validation in expat/doc/reference.html, expat/lib/expat.h.
- debian/patches/CVE-2022-25236-4.patch: document namespace separator
  effect right in header expat/lib/expat.h.
- debian/patches/CVE-2022-25236-5.patch: cover relaxed fix in tests.
- debian/patches/CVE-2022-25236-6.patch: relax fix with regard to
  RFC 3986 URI characters in expat/lib/xmlparse.c. (LP: #1963903)

 -- Leonidas Da Silva Barbosa   Mon, 21 Feb
2022 14:42:01 -0300

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-25236

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-25313

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-25314

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-25315

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

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

Title:
  expat relax fix for CVE-2022-25236 and possible regressions

Status in expat package in Ubuntu:
  Fix Released

Bug description:
  Sebastian Pipping report to us that these additional fixes are
  required to fix properly CVE-2022-25236 in regard to RCF 3986 URI
  characters and possibly regressions as the merge request points.

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


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

[Touch-packages] [Bug 1963903] Re: expat relax fix for CVE-2022-25236 and possible regressions

[Launchpad Bug Tracker]

This bug was fixed in the package expat - 2.2.5-3ubuntu0.7

---
expat (2.2.5-3ubuntu0.7) bionic-security; urgency=medium

  * SECURITY UPDATE: Stack exhaustion
- debian/patches/CVE-2022-25313.patch: prevent
  stack exhaustion in build_model in expat/lib/xmlparse.c.
- debian/patches/fix-build_model-regression.patch: fix build_model
  regression in expat/lib/xmlparse.c.
- CVE-2022-25313
  * SECURITY UPDATE: Integer overflow
- debian/patches/CVE-2022-25314.patch: prevent integer overflow in
  copyString in expat/lib/xmlparse.c.
- CVE-2022-25314
  * SECURITY UPDATE: Integer overflow
- debian/patches/CVE-2022-25315.patch: prevent integer overflow in
  storeRawNames in expat/lib/xmlparse.c.
- CVE-2022-25315
  * SECURITY UPDATE: relax fix to CVE-2022-25236 with regard to
RFC 3986 URI characters and possibly regressions
- debian/patches/CVE-2022-25236-3.patch: add a note on namespace URI
  validation in expat/doc/reference.html, expat/lib/expat.h.
- debian/patches/CVE-2022-25236-4.patch: document namespace separator
  effect right in header expat/lib/expat.h.
- debian/patches/CVE-2022-25236-5.patch: cover relaxed fix in tests.
- debian/patches/CVE-2022-25236-6.patch: relax fix with regard to
  RFC 3986 URI characters in expat/lib/xmlparse.c. (LP: #1963903)

 -- Leonidas Da Silva Barbosa   Tue, 08 Mar
2022 09:28:37 -0300

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

Title:
  expat relax fix for CVE-2022-25236 and possible regressions

Status in expat package in Ubuntu:
  Fix Released

Bug description:
  Sebastian Pipping report to us that these additional fixes are
  required to fix properly CVE-2022-25236 in regard to RCF 3986 URI
  characters and possibly regressions as the merge request points.

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


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

[Touch-packages] [Bug 1963903] Re: expat relax fix for CVE-2022-25236 and possible regressions

[Launchpad Bug Tracker]

This bug was fixed in the package expat - 2.2.9-1ubuntu0.4

---
expat (2.2.9-1ubuntu0.4) focal-security; urgency=medium

  * SECURITY UPDATE: Stack exhaustion
- debian/patches/CVE-2022-25313.patch: prevent
  stack exhaustion in build_model in expat/lib/xmlparse.c.
- debian/patches/fix-build_model-regression.patch: fix build_model
  regression in expat/lib/xmlparse.c.
- debian/patches/protect-against-nested-element*: in expat/lib/xmlparse.
- CVE-2022-25313
  * SECURITY UPDATE: Integer overflow
- debian/patches/CVE-2022-25314.patch: prevent integer overflow in
  copyString in expat/lib/xmlparse.c.
- CVE-2022-25314
  * SECURITY UPDATE: Integer overflow
- debian/patches/CVE-2022-25315.patch: prevent integer overflow in
  storeRawNames in expat/lib/xmlparse.c.
- CVE-2022-25315
  * SECURITY UPDATE: relax fix to CVE-2022-25236 with regard to
RFC 3986 URI characters and possibly regressions
- debian/patches/CVE-2022-25236-3.patch: add a note on namespace URI
  validation in expat/doc/reference.html, expat/lib/expat.h.
- debian/patches/CVE-2022-25236-4.patch: document namespace separator
  effect right in header expat/lib/expat.h.
- debian/patches/CVE-2022-25236-5.patch: cover relaxed fix in tests.
- debian/patches/CVE-2022-25236-6.patch: relax fix with regard to
  RFC 3986 URI characters in expat/lib/xmlparse.c. (LP: #1963903)
  * removing duplicated tests
- debian/patches/fix_test_dup.patch: removing tests were duplicated in
  expat/tests/runtests.c.

 -- Leonidas Da Silva Barbosa   Mon, 21 Feb
2022 15:48:46 -0300

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

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

Title:
  expat relax fix for CVE-2022-25236 and possible regressions

Status in expat package in Ubuntu:
  Fix Released

Bug description:
  Sebastian Pipping report to us that these additional fixes are
  required to fix properly CVE-2022-25236 in regard to RCF 3986 URI
  characters and possibly regressions as the merge request points.

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


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

[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()

[Robie Basak]

I think we've concluded that we're not going to ship the configuration
file parts in the Impish and Focal uploads, so I'll reject them from the
queue now. The Bionic queue upload is ready now though.

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

Title:
  Apply default TTL to records obtained from getaddrinfo()

Status in keyutils package in Ubuntu:
  Fix Released
Status in keyutils source package in Focal:
  Incomplete
Status in keyutils source package in Impish:
  Incomplete

Bug description:
  [Impact]
  

  There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for
  DNS resolution. The keyutils package contains the userspace utility to
  update the kernel keyring with the DNS mapping to IP address. Prior to
  1.6.2, this utility may erroneously set unlimited lifetime for this
  keyring in the kernel.

  [Test plan]
  ===

  1. Create a file share on an SMB server (can be a samba server) with
  two IP addresses. Make sure that FQDN of the server resolves to one of
  these addresses.

  2. mount the created share on the cifs client using the FQDN for the
  server. Make sure that the mount point is accessible.

  3. Using the ss command on the client, to kill the sockets that
  connect to the server: sudo ss -K dport :445

  4. Now update the DNS entry to make sure that the server FQDN now
  resolves to the second IP address of the server. Make sure that
  nslookup on the client now resolves to the new IP address.

  5. Repeat step 3 to kill the sockets that connect to server to force
  re-connection again.

  Without the fix, after step 5, with the "ss -t" command, you'll see
  that the client has reconnected to the old IP address, even when DNS
  lookups return the new IP.

  With the fix (after a reboot of the client machine to make sure that
  kernel keys are refreshed), you'll see that the client reconnects to
  the new IP address.

  The bug is due to unlimited lifetime set by key.dns_resolver (which is
  part of keyutils package). As a result, even if IP address for the DNS
  entries change, the kernel filesystems would continue to use old IP
  address, due to the cached keys. This issue causes clients to
  misbehave when Azure Files service endpoints move to a different
  cluster.

  [Where problems could occur]
  

  Address records obtained from getaddrinfo() don't come with any TTL
  information, even if they're obtained from the DNS, so if someone is
  relying on this particularly, might face some problem/regression but I
  don't think they would face that as it would still be highly
  configurable.

  [Other information]
  ===

  This request is essentially from one of our cloud partners and they're
  highly affected by this.

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


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

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Bug Watch Updater]

** Changed in: evince (Debian)
   Status: Unknown => New

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged
Status in evince package in Debian:
  New

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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


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

[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()

[Robie Basak]

Hello Utkarsh, or anyone else affected,

Accepted keyutils into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/keyutils/1.5.9-9.2ubuntu2.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: keyutils (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  Apply default TTL to records obtained from getaddrinfo()

Status in keyutils package in Ubuntu:
  Fix Released
Status in keyutils source package in Bionic:
  Fix Committed
Status in keyutils source package in Focal:
  Incomplete
Status in keyutils source package in Impish:
  Incomplete

Bug description:
  [Impact]
  

  There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for
  DNS resolution. The keyutils package contains the userspace utility to
  update the kernel keyring with the DNS mapping to IP address. Prior to
  1.6.2, this utility may erroneously set unlimited lifetime for this
  keyring in the kernel.

  [Test plan]
  ===

  1. Create a file share on an SMB server (can be a samba server) with
  two IP addresses. Make sure that FQDN of the server resolves to one of
  these addresses.

  2. mount the created share on the cifs client using the FQDN for the
  server. Make sure that the mount point is accessible.

  3. Using the ss command on the client, to kill the sockets that
  connect to the server: sudo ss -K dport :445

  4. Now update the DNS entry to make sure that the server FQDN now
  resolves to the second IP address of the server. Make sure that
  nslookup on the client now resolves to the new IP address.

  5. Repeat step 3 to kill the sockets that connect to server to force
  re-connection again.

  Without the fix, after step 5, with the "ss -t" command, you'll see
  that the client has reconnected to the old IP address, even when DNS
  lookups return the new IP.

  With the fix (after a reboot of the client machine to make sure that
  kernel keys are refreshed), you'll see that the client reconnects to
  the new IP address.

  The bug is due to unlimited lifetime set by key.dns_resolver (which is
  part of keyutils package). As a result, even if IP address for the DNS
  entries change, the kernel filesystems would continue to use old IP
  address, due to the cached keys. This issue causes clients to
  misbehave when Azure Files service endpoints move to a different
  cluster.

  [Where problems could occur]
  

  Address records obtained from getaddrinfo() don't come with any TTL
  information, even if they're obtained from the DNS, so if someone is
  relying on this particularly, might face some problem/regression but I
  don't think they would face that as it would still be highly
  configurable.

  [Other information]
  ===

  This request is essentially from one of our cloud partners and they're
  highly affected by this.

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


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

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

[Neurer]

Public bug reported:

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

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

-- 
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 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs

[dhdur...@verizon.net]

I will take a stab at this later today.

Yesterday while searching a bit I may have encountered the reason these
particular packages have a problem.  I was doing a search and it may be
that the packages having the problem I am seeing are all qt5 users.
Could there be a problem between qt5 and the libgail under some
circumstances?  Is there a qt5 configuration file somewhere that might
offer a way to tweak things?

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

Title:
  segfault in libgtk-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

  Version of library is 2.24.32-4ubuntu4 and library file is dated
  2021-03-31 here.

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


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

[Touch-packages] [Bug 1947588] Re: Infinite Loop in OpenSSL s_server

[Simon Chopin]

** Tags removed: rls-ff-incoming

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Focal:
  Confirmed
Status in openssl source package in Impish:
  Confirmed
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j  16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options:  bn(64,64) rc4(16x,int) des(int) blowfish(ptr) 
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
  ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
  Seeding source: os-specific

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


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

[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()

[Shyam Prasad]

Thanks for the update, Robie. 
I'll let you know how our testing goes with this soon.

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

Title:
  Apply default TTL to records obtained from getaddrinfo()

Status in keyutils package in Ubuntu:
  Fix Released
Status in keyutils source package in Bionic:
  Fix Committed
Status in keyutils source package in Focal:
  Incomplete
Status in keyutils source package in Impish:
  Incomplete

Bug description:
  [Impact]
  

  There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for
  DNS resolution. The keyutils package contains the userspace utility to
  update the kernel keyring with the DNS mapping to IP address. Prior to
  1.6.2, this utility may erroneously set unlimited lifetime for this
  keyring in the kernel.

  [Test plan]
  ===

  1. Create a file share on an SMB server (can be a samba server) with
  two IP addresses. Make sure that FQDN of the server resolves to one of
  these addresses.

  2. mount the created share on the cifs client using the FQDN for the
  server. Make sure that the mount point is accessible.

  3. Using the ss command on the client, to kill the sockets that
  connect to the server: sudo ss -K dport :445

  4. Now update the DNS entry to make sure that the server FQDN now
  resolves to the second IP address of the server. Make sure that
  nslookup on the client now resolves to the new IP address.

  5. Repeat step 3 to kill the sockets that connect to server to force
  re-connection again.

  Without the fix, after step 5, with the "ss -t" command, you'll see
  that the client has reconnected to the old IP address, even when DNS
  lookups return the new IP.

  With the fix (after a reboot of the client machine to make sure that
  kernel keys are refreshed), you'll see that the client reconnects to
  the new IP address.

  The bug is due to unlimited lifetime set by key.dns_resolver (which is
  part of keyutils package). As a result, even if IP address for the DNS
  entries change, the kernel filesystems would continue to use old IP
  address, due to the cached keys. This issue causes clients to
  misbehave when Azure Files service endpoints move to a different
  cluster.

  [Where problems could occur]
  

  Address records obtained from getaddrinfo() don't come with any TTL
  information, even if they're obtained from the DNS, so if someone is
  relying on this particularly, might face some problem/regression but I
  don't think they would face that as it would still be highly
  configurable.

  [Other information]
  ===

  This request is essentially from one of our cloud partners and they're
  highly affected by this.

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


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

[Touch-packages] [Bug 1964494] [NEW] Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs

[Alejandro Santoyo Gonzalez]

Public bug reported:

A customer reported network disconnections on their storage 
servers when running 'netplan apply'. The culprit was that
they have link-local addresses configured and the Duplicate 
Address Detection (DAD) mechanism was delaying the interfaces 
from coming back up. 

As a workaround we tried to disable DAD for the interfaces 
but that's not working in Ubuntu 22.04:

I've noticed that setting DuplicateAddressDetection=none for an
interface with a link-local address (e.g., 169.254.*) via a 
.network file added to /etc/systemd/network/ doesn't really 
disable Duplicate Address Detection.

OS and package versions:

 - Description: Ubuntu Jammy Jellyfish (development branch). Release: 22.04
 - systemd 249.5-2ubuntu4

Reproducer:
---
1- Set up Ubuntu 22.04 VM
2- Increase systemlog level:

  mkdir -p /etc/systemd/system/systemd-networkd.service.d/
  cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf  /etc/systemd/system/systemd-networkd.service.d/10-debug.conf 

[Touch-packages] [Bug 1963904] Re: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup

[Brian Murray]

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

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

Title:
  
/usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup

Status in packagekit package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
1.2.5-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e43a7af1acb9c04a2066e00f2785c7c200145bcc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Touch-packages] [Bug 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs

[Dan Streetman]

> I think this commit [1] may be related (landed in systemd v249)

yeah, that commit seems to be intentionally forcing ACD on for
statically configured ipv4, i'm not sure quite why, it seems like a
user-configured setting should be honored; but possibly Yu was trying to
default it to on instead of overriding user config.

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

Title:
  Setting DuplicateAddressDetection=none doesn't disable DAD for link-
  local IPs

Status in systemd package in Ubuntu:
  New

Bug description:
  A customer reported network disconnections on their storage 
  servers when running 'netplan apply'. The culprit was that
  they have link-local addresses configured and the Duplicate 
  Address Detection (DAD) mechanism was delaying the interfaces 
  from coming back up. 

  As a workaround we tried to disable DAD for the interfaces 
  but that's not working in Ubuntu 22.04:

  I've noticed that setting DuplicateAddressDetection=none for an
  interface with a link-local address (e.g., 169.254.*) via a 
  .network file added to /etc/systemd/network/ doesn't really 
  disable Duplicate Address Detection.

  OS and package versions:
  
   - Description:   Ubuntu Jammy Jellyfish (development branch). Release: 
22.04
   - systemd 249.5-2ubuntu4

  Reproducer:
  ---
  1- Set up Ubuntu 22.04 VM
  2- Increase systemlog level:

mkdir -p /etc/systemd/system/systemd-networkd.service.d/
cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf 

[Touch-packages] [Bug 1962454] Re: Oops pages show wrong time window in JournalErrors

[Brian Murray]

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

** Changed in: errors
   Status: New => Invalid

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

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

Title:
  Oops pages show wrong time window in JournalErrors

Status in Errors:
  Invalid
Status in apport package in Ubuntu:
  Triaged

Bug description:
  For example, I just experienced a crash at:

Feb 28 17:31:12

  And the JournalErrors entries are:

Feb 28 17:31:30 - Feb 28 17:31:41

  So don't relate to the crash.

  But it should be possible to tell journalctl to collect entries
  starting *before* the crash and cover the full crash timeframe.

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


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

[Touch-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists

[Brian Murray]

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

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

Title:
  Ubuntu reboots instead of powering off if a software updates exists

Status in gnome-shell package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  Invalid

Bug description:
  When I want to turn off a computer, I got a checkbox "Install deferred
  updates" (see screenshot, I'm not sure if my back-translation is
  correct).

  If the checkbox is checked, Ubuntu box reboots instead of powering
  off. It is not "rebopot to install updates". It just reboots to
  desktop again. If I uncheck the box, it powers off normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 26 00:05:44 2022
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago)

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


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

[Touch-packages] [Bug 1923052] Re: screen reader does not read ubiquity window

[Brian Murray]

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

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

Title:
  screen reader does not read ubiquity window

Status in at-spi2-core package in Ubuntu:
  Incomplete
Status in orca package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions


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

[Touch-packages] [Bug 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs

[Alejandro Santoyo Gonzalez]

I agree, a user-configured setting should be honored. Another thing to
consider is that according to the Jammy systemd.network man page, the 
default should be 'ipv6' so one would expect that to be a global 
default, but it gets overridden for link-local IPs due to this commit.  


[1] https://manpages.ubuntu.com/manpages/jammy/man5/systemd.network.5.html

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

Title:
  Setting DuplicateAddressDetection=none doesn't disable DAD for link-
  local IPs

Status in systemd package in Ubuntu:
  New

Bug description:
  A customer reported network disconnections on their storage 
  servers when running 'netplan apply'. The culprit was that
  they have link-local addresses configured and the Duplicate 
  Address Detection (DAD) mechanism was delaying the interfaces 
  from coming back up. 

  As a workaround we tried to disable DAD for the interfaces 
  but that's not working in Ubuntu 22.04:

  I've noticed that setting DuplicateAddressDetection=none for an
  interface with a link-local address (e.g., 169.254.*) via a 
  .network file added to /etc/systemd/network/ doesn't really 
  disable Duplicate Address Detection.

  OS and package versions:
  
   - Description:   Ubuntu Jammy Jellyfish (development branch). Release: 
22.04
   - systemd 249.5-2ubuntu4

  Reproducer:
  ---
  1- Set up Ubuntu 22.04 VM
  2- Increase systemlog level:

mkdir -p /etc/systemd/system/systemd-networkd.service.d/
cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf 

[Touch-packages] [Bug 1947588] Re: Infinite Loop in OpenSSL s_server

[Brian Murray]

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

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

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

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Focal:
  Confirmed
Status in openssl source package in Impish:
  Confirmed
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j  16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options:  bn(64,64) rc4(16x,int) des(int) blowfish(ptr) 
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
  ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
  Seeding source: os-specific

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


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

[Touch-packages] [Bug 1964500] [NEW] Se congela el sistema y no responde

[Matías Ezequiel Kühn]

Public bug reported:

I don't know if the error reported is correct. The problem I have is
that the system freezes and becomes unresponsive, both the keyboard and
touchpad are unresponsive. It is not a single error of an isolated
program, but of the system. The only way to get it to work again is to
press the off button and restart. That way it will work properly again.
This problem occurred twice. I was not using a lot of computer
resources, just a few browser windows. It could be a kernel problem or
something else. I am available for more help information or orders for
possible solutions. I don't have a lot of knowledge, but whatever I can
do or research, and that will help to solve the bug I will do it.

Translated with www.DeepL.com/Translator (free version)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 10 13:39:43 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.2.2, 5.13.0-30-generic, x86_64: installed
 acpi-call, 1.2.2, 5.13.0-35-generic, x86_64: installed
 tp_smapi, 0.43, 5.13.0-28-generic, x86_64: installed
 tp_smapi, 0.43, 5.13.0-30-generic, x86_64: installed
 tp_smapi, 0.43, 5.13.0-35-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo ThinkPad E595 [17aa:5124]
InstallationDate: Installed on 2021-08-01 (221 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20NES0KM00
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=f42b194c-a5b3-4d08-a343-87ab7e4c88ca ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/17/2020
dmi.bios.release: 1.20
dmi.bios.vendor: LENOVO
dmi.bios.version: R11ET40W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NES0KM00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET40W(1.20):bd11/17/2020:br1.20:efr1.20:svnLENOVO:pn20NES0KM00:pvrThinkPadE495:rvnLENOVO:rn20NES0KM00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:
dmi.product.family: ThinkPad E495
dmi.product.name: 20NES0KM00
dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
dmi.product.version: ThinkPad E495
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu

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

Title:
  Se congela el sistema y no responde

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't know if the error reported is correct. The problem I have is
  that the system freezes and becomes unresponsive, both the keyboard
  and touchpad are unresponsive. It is not a single error of an isolated
  program, but of the system. The only way to get it to work again is to
  press the off button and restart. That way it will work properly
  again. This problem occurred twice. I was not using a lot of computer
  resources, just a few browser windows. It could be a kernel problem or
  something else. I am available for more help information or orders for
  possible solutions. I don't have a lot of knowledge, but whatever I
  can do or research, and that will help to solve the bug I will do it.

  Translated with www.DeepL.com/Translator (free version)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Er

[Touch-packages] [Bug 1962038] Re: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

[Steve Langasek]

dropping the update-excuse tag, since this bug has nothing to do with
why the packages are or aren't migrating out of -proposed AFAIK

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

Title:
  wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

Status in procps package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in procps source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  New
Status in procps source package in Jammy:
  New
Status in systemd source package in Jammy:
  In Progress

Bug description:
  [Impact]

  I've just learned that systemd is setting kernel.sysrq to 16 in
  /usr/lib/sysctl.d/50-default.conf.  This is inconsistent with
  /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176
  by default.  systemd should drop its setting to defer to the file that
  we have been carrying in procps for a very long time.

  Therefore, users can only sync their storage but not do any other
  actions using the magic sysrq key.

  [Test Plan]

  $ sysctl kernel.sysrq
  => This should show "kernel.sysrq = 176" as set by 
/etc/sysctl.d/10-magic-sysrq.conf
  $ sysctl net.ipv4.conf.all.rp_filter
  => This should show "net.ipv4.conf.all.rp_filter=2" as set by 
/etc/sysctl.d/10-network-security.conf

  [Where problems could occur]

   * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf
   * If something is broken it could fail to apply any of systemd's sysctl 
configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be 
in place.

  [Other Info]
   
   * None

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


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

[Touch-packages] [Bug 1962038] Re: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

[Steve Langasek]

oh correction, it does because of the added autopkgtest :)

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

Title:
  wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

Status in procps package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in procps source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  New
Status in procps source package in Jammy:
  New
Status in systemd source package in Jammy:
  In Progress

Bug description:
  [Impact]

  I've just learned that systemd is setting kernel.sysrq to 16 in
  /usr/lib/sysctl.d/50-default.conf.  This is inconsistent with
  /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176
  by default.  systemd should drop its setting to defer to the file that
  we have been carrying in procps for a very long time.

  Therefore, users can only sync their storage but not do any other
  actions using the magic sysrq key.

  [Test Plan]

  $ sysctl kernel.sysrq
  => This should show "kernel.sysrq = 176" as set by 
/etc/sysctl.d/10-magic-sysrq.conf
  $ sysctl net.ipv4.conf.all.rp_filter
  => This should show "net.ipv4.conf.all.rp_filter=2" as set by 
/etc/sysctl.d/10-network-security.conf

  [Where problems could occur]

   * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf
   * If something is broken it could fail to apply any of systemd's sysctl 
configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be 
in place.

  [Other Info]
   
   * None

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


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

[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs

[dhdur...@verizon.net]

How do I reinstall libgail-common?  I used dpkg -i with
libgail-3-0_3.24.20-0ubuntu1_amd64.deb with no change in behavior.  I
went back to
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.20-0ubuntu1/+build/19437463
but I don't see a libgail-common file there.

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

Title:
  segfault in libgtk-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

  Version of library is 2.24.32-4ubuntu4 and library file is dated
  2021-03-31 here.

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


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

[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs

[dhdur...@verizon.net]

I just thought to look in synaptic and I see it there.  Should I install
from there, or is there a reason to do so in another manner?

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

Title:
  segfault in libgtk-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

  Version of library is 2.24.32-4ubuntu4 and library file is dated
  2021-03-31 here.

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


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

[Touch-packages] [Bug 1964506] [NEW] Ping: checks payloads incorrectly, ignores all mismatch replies

[Matt Whiteley]

Public bug reported:

Problematic commit reverted upstream causing incorrect behavior in
Ubuntu Focal.

Discussion: https://github.com/iputils/iputils/issues/320
Fix: https://github.com/iputils/iputils/pull/321
Release: https://github.com/iputils/iputils/releases/tag/20210722

Could this patch be added for a Focal update please?

1) Ubuntu 20.04.3 LTS
2) 3:20190709-3
3)

focal$ ping -c 1 -s 1200 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

4)

xenial$ ping -c 1 -s 1200 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  New

Bug description:
  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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


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

[Touch-packages] [Bug 1963904] Re: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup

[Brian Murray]

** Tags added: fr-2103

** Also affects: packagekit (Ubuntu Jammy)
   Importance: High
   Status: Triaged

** Tags removed: rls-jj-incoming

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

Title:
  
/usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Jammy:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
1.2.5-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e43a7af1acb9c04a2066e00f2785c7c200145bcc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Touch-packages] [Bug 1929345] Re: Pressing calculator key generates infinitely many key-press key-release events

[calcopiritus]

I have found that the steps in this answer:
https://askubuntu.com/a/1367801

Fixed the problem for me

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

Title:
  Pressing calculator key generates infinitely many key-press key-
  release events

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Full description is posted in this AskUbuntu question:
  https://askubuntu.com/q/1336575/625814

  I've got a new notebook HP Omen 15, manufactured in 2020. I has
  Calculator key, this key is actual normal media key.

  Pressing on it launches calculator only once, after the OS is booted.
  No reaction for other presses.

  If I run xev and press Calculator I see infinitely many messages about
  pressing and releasing XF86Calculator key:

  ...
  KeyRelease event, serial 42, synthetic NO, window 0x3e1,
  root 0x29e, subw 0x0, time 52918, (151,-96), root:(151,806),
  state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyPress event, serial 42, synthetic NO, window 0x3e1,
  root 0x29e, subw 0x0, time 52918, (151,-96), root:(151,806),
  state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 42, synthetic NO, window 0x3e1,
  root 0x29e, subw 0x0, time 52958, (151,-96), root:(151,806),
  state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyPress event, serial 42, synthetic NO, window 0x3e1,
  root 0x29e, subw 0x0, time 52958, (151,-96), root:(151,806),
  state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 42, synthetic NO, window 0x3e1,
  root 0x29e, subw 0x0, time 52999, (151,-96), root:(151,806),
  state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
  ...

  Then I press Ctrl-C to stop this stream.
  This happens only once after the system is booted, next runs of xev don't 
show any events after pressing this key.

  If I run showkey, it always shows scan codes and key codes for that
  key:

  $ sudo showkey -s
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  0x9c
  0xe0 0x21
  0x1d
  ^Ccaught signal 2, cleaning up...
  0xe0 0x21
  $ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 140 press
  keycode  29 press
  ^Ccaught signal 2, cleaning up...

  Debugging with evtest shows that this key doesn't generate any events,
  while some other keys do:

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:  Power Button
  /dev/input/event1:  Lid Switch
  /dev/input/event2:  Power Button
  /dev/input/event3:  AT Translated Set 2 keyboard
  /dev/input/event4:  Video Bus
  /dev/input/event5:  HP WMI hotkeys
  /dev/input/event6:  HDA NVidia HDMI/DP,pcm=3
  /dev/input/event7:  SONiX USB Keyboard
  /dev/input/event8:  SONiX USB Keyboard Consumer Control
  /dev/input/event9:  SONiX USB Keyboard System Control
  /dev/input/event10: PixArt Dell MS116 USB Optical Mouse
  /dev/input/event11: HDA NVidia HDMI/DP,pcm=7
  /dev/input/event12: HDA NVidia HDMI/DP,pcm=8
  /dev/input/event13: HDA NVidia HDMI/DP,pcm=9
  /dev/input/event14: HDA NVidia HDMI/DP,pcm=10
  /dev/input/event15: HDA NVidia HDMI/DP,pcm=11
  /dev/input/event16: SYNA32A5:00 06CB:CE17 Mouse
  /dev/input/event17: SYNA32A5:00 06CB:CE17 Touchpad
  /dev/input/event18: HD-Audio Generic Mic
  /dev/input/event19: HD-Audio Generic Headphone
  /dev/input/event20: HP Wide Vision HD Camera: HP Wi
  /dev/input/event21: WI-XB400 (AVRCP)
  Select the device event number [0-21]: 5
  Input driver version is 1.0.1
  Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
  Input device name: "HP WMI hotkeys"
  Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
  Event code 138 (KEY_HELP)
  Event code 141 (KEY_SETUP)
  Event code 148 (KEY_PROG1)
  Event code 153 (KEY_DIRECTION)
  Event code 184 (KEY_F14)
  Event code 185 (KEY_F15)
  Event code 186 (KEY_F16)
  Event code 187 (KEY_F17)
  Event code 224 (KEY_BRIGHTNESSDOWN)
  Event code 225 (KEY_BRIGHTNESSUP)
  Event code 

[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs

[Sebastien Bacher]

yes, installing from synaptic is fine. The package comes from gtk2
that's why it's not on the gtk3 buildpage

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

Title:
  segfault in libgtk-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

  Version of library is 2.24.32-4ubuntu4 and library file is dated
  2021-03-31 here.

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


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

[Touch-packages] [Bug 1962038] Re: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 249.10-0ubuntu2

---
systemd (249.10-0ubuntu2) jammy; urgency=medium

  * Fix deadlock between pid1 and dbus-daemon (LP: #1871538)
File: 
debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=100a7bfc2d0f82c3afbede04a022c655529cffac
  * Don't override Ubuntu's default sysctl values (LP: #1962038)
File: 
debian/patches/debian/UBUNTU-Don-t-override-Ubuntu-s-default-sysctl-values-LP-1962038.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10cdb7da3539b3a3c3e619b470a75c83e46ef11

 -- Lukas Märdian   Tue, 08 Mar 2022 14:58:00 +0100

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

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

Title:
  wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

Status in procps package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in procps source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  New
Status in procps source package in Jammy:
  New
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  I've just learned that systemd is setting kernel.sysrq to 16 in
  /usr/lib/sysctl.d/50-default.conf.  This is inconsistent with
  /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176
  by default.  systemd should drop its setting to defer to the file that
  we have been carrying in procps for a very long time.

  Therefore, users can only sync their storage but not do any other
  actions using the magic sysrq key.

  [Test Plan]

  $ sysctl kernel.sysrq
  => This should show "kernel.sysrq = 176" as set by 
/etc/sysctl.d/10-magic-sysrq.conf
  $ sysctl net.ipv4.conf.all.rp_filter
  => This should show "net.ipv4.conf.all.rp_filter=2" as set by 
/etc/sysctl.d/10-network-security.conf

  [Where problems could occur]

   * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf
   * If something is broken it could fail to apply any of systemd's sysctl 
configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be 
in place.

  [Other Info]
   
   * None

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


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

[Touch-packages] [Bug 1961477] Re: software-properties-gtk not running

[Hans Joachim Desserud]

Thanks for taking your time to report this issue and help making Ubuntu
better.

Could you please attach the error message you get when running from the
console? I don't see any error message on my 20.04 test system, but
there might be some clue if it is caused by archive settings or
something else.

** Changed in: software-properties (Ubuntu)
   Status: New => Incomplete

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

Title:
  software-properties-gtk not running

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  When I try to run the program from Ubuntu nothing happens. An error
  occurs when trying to run the program from the console. Attempts to
  roll back the version were unsuccessful.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.99.9.8
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 19 15:33:18 2022
  InstallationDate: Installed on 2022-01-10 (39 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 249.10-0ubuntu2

---
systemd (249.10-0ubuntu2) jammy; urgency=medium

  * Fix deadlock between pid1 and dbus-daemon (LP: #1871538)
File: 
debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=100a7bfc2d0f82c3afbede04a022c655529cffac
  * Don't override Ubuntu's default sysctl values (LP: #1962038)
File: 
debian/patches/debian/UBUNTU-Don-t-override-Ubuntu-s-default-sysctl-values-LP-1962038.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10cdb7da3539b3a3c3e619b470a75c83e46ef11

 -- Lukas Märdian   Tue, 08 Mar 2022 14:58:00 +0100

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

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  New
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  New
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeic

[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs

[dhdur...@verizon.net]

Installed libgail-common via synaptic as requested and restarted the
system.  The results are not what I expected:

dhdurgee@z560:~/Downloads$ fcl
Gtk-Message: 12:46:26.155: Failed to load module "gail"

** (fcl:2132): WARNING **: 12:46:26.238: 
(../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: 
(root)
dhdurgee@z560:~/Downloads$ apt-cache showpkg libgail-common
Package: libgail-common
Versions: 
2.24.32-4ubuntu4 
(/var/lib/apt/lists/pubmirrors.dal.corespace.com_ubuntu_dists_focal_main_binary-amd64_Packages)
 Description Language: 
 File: 
/var/lib/apt/lists/pubmirrors.dal.corespace.com_ubuntu_dists_focal_main_binary-amd64_Packages
  MD5: 97f579410f9d8e3edb5f60b6c06b9ef7
 Description Language: 
 File: 
/var/lib/apt/lists/pubmirrors.dal.corespace.com_ubuntu_dists_focal_main_binary-i386_Packages
  MD5: 97f579410f9d8e3edb5f60b6c06b9ef7
 Description Language: en
 File: 
/var/lib/apt/lists/pubmirrors.dal.corespace.com_ubuntu_dists_focal_main_i18n_Translation-en
  MD5: 97f579410f9d8e3edb5f60b6c06b9ef7


Reverse Depends: 
  libgail-common:i386,libgail-common 2.24.32-4ubuntu4
  ubuntu-unity-desktop,libgail-common
  ubuntu-mate-desktop,libgail-common
  ubuntu-mate-core,libgail-common
  ubuntu-budgie-desktop,libgail-common
  multimedia-devel,libgail-common
  libgnomecanvas2-0,libgail-common
  libgail-dev,libgail-common 2.24.32-4ubuntu4
  libgail-common:i386,libgail-common 2.24.32-4ubuntu4
  libgtk2.0-0,libgail-common
Dependencies: 
2.24.32-4ubuntu4 - libatk1.0-0 (2 1.32.0) libc6 (2 2.4) libgail18 (5 
2.24.32-4ubuntu4) libgdk-pixbuf2.0-0 (2 2.22.1) libglib2.0-0 (2 2.37.3) 
libgtk2.0-0 (2 2.24.0) libpango-1.0-0 (2 1.28.3) libx11-6 (0 (null)) 
libgail-common:i386 (35 2.24.32-4ubuntu4) libgail-common:i386 (38 
2.24.32-4ubuntu4) 
Provides: 
2.24.32-4ubuntu4 - 
Reverse Provides: 
dhdurgee@z560:~/Downloads$ 

Is this what you expected?  I expected either the load failed message to
go away or for the crash to return.

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

Title:
  segfault in libgtk-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

  Version of library is 2.24.32-4ubuntu4 and library file is dated
  2021-03-31 here.

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


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

[Touch-packages] [Bug 1964502] [NEW] Settings->Bluetooth windows freezes while connecting bluetooth device Honor freebuds 2

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Steps:
1) Go to Settings->Bluetooth
2) Try to pair Honor freebuds 2

Expected result:
Device is succesfully connected

Actual result:
While pairing windows is freezes, then it closes

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  avladimir   1014 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 10 19:57:52 2022
InstallationDate: Installed on 2022-03-06 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2020
dmi.bios.release: 1.20
dmi.bios.vendor: LENOVO
dmi.bios.version: DJCN20WW
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ThinkBook 14-IIL
dmi.ec.firmware.release: 1.17
dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN20WW:bd08/10/2020:br1.20:efr1.17:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:skuLENOVO_MT_20SL_BU_idea_FM_Thinkbook14-IIL:
dmi.product.family: Thinkbook 14-IIL
dmi.product.name: 20SL
dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
dmi.product.version: Lenovo ThinkBook 14-IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal
-- 
Settings->Bluetooth windows freezes while connecting bluetooth device Honor 
freebuds 2
https://bugs.launchpad.net/bugs/1964502
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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

[Touch-packages] [Bug 1964502] Re: Settings->Bluetooth windows freezes while connecting bluetooth device Honor freebuds 2

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Settings->Bluetooth windows freezes while connecting bluetooth device
  Honor freebuds 2

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps:
  1) Go to Settings->Bluetooth
  2) Try to pair Honor freebuds 2

  Expected result:
  Device is succesfully connected

  Actual result:
  While pairing windows is freezes, then it closes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  avladimir   1014 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 10 19:57:52 2022
  InstallationDate: Installed on 2022-03-06 (3 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2020
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN20WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.17
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN20WW:bd08/10/2020:br1.20:efr1.17:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:skuLENOVO_MT_20SL_BU_idea_FM_Thinkbook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs

[Sebastien Bacher]

the earlier experience of having the segfault not resolved after
removing it suggests that you might need to restart the session for the
change to be active, did you try to logout and log in again?

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

Title:
  segfault in libgtk-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

  Version of library is 2.24.32-4ubuntu4 and library file is dated
  2021-03-31 here.

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


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

[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs

[dhdur...@verizon.net]

I used synaptic to install the package and then did a restart of the
system after cleanly closing all running programs.  That of course
required me to log back in when the system restarted.  Is there more I
should do at this point?

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

Title:
  segfault in libgtk-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

  Version of library is 2.24.32-4ubuntu4 and library file is dated
  2021-03-31 here.

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


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

[Touch-packages] [Bug 1962038] Re: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

[Launchpad Bug Tracker]

This bug was fixed in the package procps - 2:3.3.17-6ubuntu2

---
procps (2:3.3.17-6ubuntu2) jammy; urgency=medium

  * Add basic autopkgtest to validate sysctl-defaults (LP: #1962038)

 -- Lukas Märdian   Fri, 25 Feb 2022 12:57:56 +0100

** Changed in: procps (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

Status in procps package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in procps source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  New
Status in procps source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  I've just learned that systemd is setting kernel.sysrq to 16 in
  /usr/lib/sysctl.d/50-default.conf.  This is inconsistent with
  /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176
  by default.  systemd should drop its setting to defer to the file that
  we have been carrying in procps for a very long time.

  Therefore, users can only sync their storage but not do any other
  actions using the magic sysrq key.

  [Test Plan]

  $ sysctl kernel.sysrq
  => This should show "kernel.sysrq = 176" as set by 
/etc/sysctl.d/10-magic-sysrq.conf
  $ sysctl net.ipv4.conf.all.rp_filter
  => This should show "net.ipv4.conf.all.rp_filter=2" as set by 
/etc/sysctl.d/10-network-security.conf

  [Where problems could occur]

   * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf
   * If something is broken it could fail to apply any of systemd's sysctl 
configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be 
in place.

  [Other Info]
   
   * None

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


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

[Touch-packages] [Bug 1964527] [NEW] Enable CONFIG_UNICODE for linux-gcp

[Khaled El Mously]

Public bug reported:

See https://lists.ubuntu.com/archives/kernel-team/2022-March/128565.html

NOTE: This config is enabled in other gcp kernels and in non-gcp
kernels.

** Affects: linux-gcp (Ubuntu)
 Importance: Undecided
 Assignee: Khaled El Mously (kmously)
 Status: New

** Affects: linux-gcp (Ubuntu Focal)
 Importance: Undecided
 Assignee: Khaled El Mously (kmously)
 Status: New

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

** No longer affects: klibc (Ubuntu)

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

** Changed in: linux-gcp (Ubuntu Focal)
 Assignee: (unassigned) => Khaled El Mously (kmously)

** Changed in: linux-gcp (Ubuntu)
 Assignee: (unassigned) => Khaled El Mously (kmously)

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

Title:
  Enable CONFIG_UNICODE for linux-gcp

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Focal:
  New

Bug description:
  See https://lists.ubuntu.com/archives/kernel-
  team/2022-March/128565.html

  NOTE: This config is enabled in other gcp kernels and in non-gcp
  kernels.

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


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

[Touch-packages] [Bug 1962093] Re: network-manager can't connect to pppoe since version 1.35.90

[Timofey]

Suddenly googled this bug report. I'm having the same problem with
networkmanager  1.36.2-1, but with ArchLinux

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

Title:
  network-manager can't connect to pppoe since version 1.35.90

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  System:kubuntu 22.04
  I create a Dsl connection with network-manager and it works ideal before I 
upgrading the network-manager from 1.35.8X to the higher.
  Now I can't connect to the Dsl, the network-manager reports errors. I found 
the messages in the syslogs as this:

  Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]:   [1645664039.3773] 
ppp-manager: starting PPP connection
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]:   [1645664039.3788] 
ppp-manager: pppd started with pid 1897
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded.
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so 
loaded.
  Feb 24 08:53:59 kUbuntu-Server kernel: [  184.286354] r8169 :04:01.0 
enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin 
/usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded.
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin 
/usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded.
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 
'serial connection'
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via 
interface enp4s1
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to 
cc:1a:fa:e8:2a:20 via interface enp4s1
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 
'establish'
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]:   [1645664039.5519] 
manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10)
  Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface 
naming scheme 'v249'.
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 
'authenticate'
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, 
requesting credentials...
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials 
from NetworkManager
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS.
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS.
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication 
succeeded
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number 
CC:1A:FA:E8:2A:20 authorized
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 
'network'
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number 
CC:1A:FA:E8:2A:20 authorized
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local  IP address *.*.*.*(I marked 
the IP)
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 
'running'
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local  IP address 
*.*.*.*(I marked the IP)
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address 
*.*.*.*(I marked the IP)
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary   DNS address 
*.*.*.*(I marked the IP)
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address 
*.*.*.*(I marked the IP)
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked 
the IP)
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]:   [1645664039.8762] 
device (ppp0): state change: unmanaged -> unavailable (reason 
'connection-assumed', sys-iface-state: 'external')
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary   DNS address *.*.*.*(I 
marked the IP)
  Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I 
marked the IP)
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]:   [1645664039.8767] 
device (ppp0): state change: unavailable -> disconnected (reason 'none', 
sys-iface-state: 'external')
  Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]:   [1645664039.8773] 
device (enp4s1): could not take control of link 10: the device already has 
ifindex 2
  Feb 24 08:53:59 kUbuntu-Server Network

[Touch-packages] [Bug 1964542] [NEW] monitor not recognized displayport

[Lsdp]

Public bug reported:

when the pc starts up or comes out of sleep mode the primary screen
remains black. To reactivate it I have to go through screen clone apply
and redo join the screens and apply.

Thanks

Ps:   have done several research and attempt, without success, on the
internet including in your forums.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.103.01  Thu Jan  6 
12:10:04 UTC 2022
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2)
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 10 18:45:17 2022
DistUpgraded: 2022-02-23 17:47:37,810 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: impish
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 470.103.01, 5.13.0-32-generic, x86_64: installed
 nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GM206 [GeForce GTX 960] [3842:2966]
InstallationDate: Installed on 2022-02-15 (23 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: ASUS All Series
ProcEnviron:
 LANGUAGE=fr_CA:fr
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=c8e08c76-0308-495c-8c5a-83f9aa24b1a0 ro quiet splash nomodeset 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to impish on 2022-02-23 (15 days ago)
dmi.bios.date: 07/10/2019
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4101
dmi.board.asset.tag: Default string
dmi.board.name: SABERTOOTH X99
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4101:bd07/10/2019:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuAll:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug impish third-party-packages ubuntu

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

Title:
  monitor not recognized displayport

Status in xorg package in Ubuntu:
  New

Bug description:
  when the pc starts up or comes out of sleep mode the primary screen
  remains black. To reactivate it I have to go through screen clone
  apply and redo join the screens and apply.

  Thanks

  Ps:   have done several research and attempt, without success, on the
  internet including in your forums.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default mod

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

[Bill Yu]

Hi Robie,

May we have your comment on this. Since we would like to have this
solution in the latest kernel, need you help to check 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 1964557] [NEW] Problem with mobile hotspot.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi, I use Ubuntu 20.04 LTS version in my VivoBook 15_ASUS Laptop X507UF.
I live in a remote area where the only option for Internet is my cell
phones network data. I use this mobile internet via Wi-Fi connection.

The problem is, if I do not start the mobile Personal Hotspot before
starting my laptop the internet connection via Wi-Fi does not work. The
Wi-Fi network icon on top right corner comes with a question mark in the
middle.

The Internet does not come even after I restart the NetworkManager.

I get the Internet connection only after I restart my laptop. That
means,

1. At first I have to enable Personal Hotspot from my mobile and then
2. I have to start my laptop.

Not the other way around.

Some times I forget this and I need to restart my laptop over again to
get the Internet Connection.

I believe this is a bug in the Wi-Fi connection module and also in
NetworkManager. I mean restarting the NetworkManager should do the job
instead of restarting the whole laptop.

Thanks.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment wi-fi
-- 
Problem with mobile hotspot.
https://bugs.launchpad.net/bugs/1964557
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager 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 1964542] Re: [nvidia] One monitor fails to wake after resuming from sleep

[Daniel van Vugt]

Thanks for the bug report.

Next time the problem happens please immediately run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

** Summary changed:

- monitor not recognized displayport
+ [nvidia] One monitor fails to wake after resuming from sleep

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470
(Ubuntu)

** Tags added: multimonitor nvidia

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: New => Incomplete

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

Title:
  [nvidia] One monitor fails to wake after resuming from sleep

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  when the pc starts up or comes out of sleep mode the primary screen
  remains black. To reactivate it I have to go through screen clone
  apply and redo join the screens and apply.

  Thanks

  Ps:   have done several research and attempt, without success, on the
  internet including in your forums.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.103.01  Thu Jan  6 
12:10:04 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2)
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 10 18:45:17 2022
  DistUpgraded: 2022-02-23 17:47:37,810 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.103.01, 5.13.0-32-generic, x86_64: installed
   nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GM206 [GeForce GTX 960] [3842:2966]
  InstallationDate: Installed on 2022-02-15 (23 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=c8e08c76-0308-495c-8c5a-83f9aa24b1a0 ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2022-02-23 (15 days ago)
  dmi.bios.date: 07/10/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4101:bd07/10/2019:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuAll:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1964542/+subscriptions


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

[Touch-packages] [Bug 1964557] Re: Problem with mobile hotspot.

[Kamrul Hasan]

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

** Tags removed: bot-comment

** Tags added: network-manager

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

Title:
  Problem with mobile hotspot.

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi, I use Ubuntu 20.04 LTS version in my VivoBook 15_ASUS Laptop
  X507UF. I live in a remote area where the only option for Internet is
  my cell phones network data. I use this mobile internet via Wi-Fi
  connection.

  The problem is, if I do not start the mobile Personal Hotspot before
  starting my laptop the internet connection via Wi-Fi does not work.
  The Wi-Fi network icon on top right corner comes with a question mark
  in the middle.

  The Internet does not come even after I restart the NetworkManager.

  I get the Internet connection only after I restart my laptop. That
  means,

  1. At first I have to enable Personal Hotspot from my mobile and then
  2. I have to start my laptop.

  Not the other way around.

  Some times I forget this and I need to restart my laptop over again to
  get the Internet Connection.

  I believe this is a bug in the Wi-Fi connection module and also in
  NetworkManager. I mean restarting the NetworkManager should do the job
  instead of restarting the whole laptop.

  Thanks.

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


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

[Touch-packages] [Bug 1964500] Re: System freezes and becomes unresponsive, both the keyboard and touchpad are unresponsive

[Daniel van Vugt]

Thanks for the bug report. Next time the problem happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. Check for crashes by following:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Summary changed:

- Se congela el sistema y no responde
+ System freezes and becomes unresponsive, both the keyboard and touchpad are 
unresponsive

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  System freezes and becomes unresponsive, both the keyboard and
  touchpad are unresponsive

Status in Ubuntu:
  Incomplete

Bug description:
  I don't know if the error reported is correct. The problem I have is
  that the system freezes and becomes unresponsive, both the keyboard
  and touchpad are unresponsive. It is not a single error of an isolated
  program, but of the system. The only way to get it to work again is to
  press the off button and restart. That way it will work properly
  again. This problem occurred twice. I was not using a lot of computer
  resources, just a few browser windows. It could be a kernel problem or
  something else. I am available for more help information or orders for
  possible solutions. I don't have a lot of knowledge, but whatever I
  can do or research, and that will help to solve the bug I will do it.

  Translated with www.DeepL.com/Translator (free version)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 10 13:39:43 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.2.2, 5.13.0-30-generic, x86_64: installed
   acpi-call, 1.2.2, 5.13.0-35-generic, x86_64: installed
   tp_smapi, 0.43, 5.13.0-28-generic, x86_64: installed
   tp_smapi, 0.43, 5.13.0-30-generic, x86_64: installed
   tp_smapi, 0.43, 5.13.0-35-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2021-08-01 (221 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20NES0KM00
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=f42b194c-a5b3-4d08-a343-87ab7e4c88ca ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2020
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET40W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NES0KM00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET40W(1.20):bd11/17/2020:br1.20:efr1.20:svnLENOVO:pn20NES0KM00:pvrThinkPadE495:rvnLENOVO:rn20NES0KM00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NES0KM00
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

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

[Amit Kumar]

Public bug reported:

I found this bug when I upgrade my ubuntu 20.04 LTS using command "apt-
get upgrade"

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam-runtime 1.3.1-5ubuntu4.3
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: crc32_pclmul
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Mar 11 10:43:38 2022
ErrorMessage: installed libpam-runtime package post-installation script 
subprocess returned error exit status 255
InstallationDate: Installed on 2022-03-10 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: pam
Title: package libpam-runtime 1.3.1-5ubuntu4.3 failed to install/upgrade: 
installed libpam-runtime package post-installation script subprocess returned 
error exit status 255
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

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

Status in pam package in Ubuntu:
  New

Bug description:
  I found this bug when I upgrade my ubuntu 20.04 LTS using command
  "apt-get upgrade"

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-runtime 1.3.1-5ubuntu4.3
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: crc32_pclmul
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Mar 11 10:43:38 2022
  ErrorMessage: installed libpam-runtime package post-installation script 
subprocess returned error exit status 255
  InstallationDate: Installed on 2022-03-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: pam
  Title: package libpam-runtime 1.3.1-5ubuntu4.3 failed to install/upgrade: 
installed libpam-runtime package post-installation script subprocess returned 
error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1964560] [NEW] file transfers have trouble finishing

[androo]

Public bug reported:

Ubuntu 21.10 with wayland windowing system sits on completed file
transfers on and off usb and takes its time realising its finished and
closing the little transfer progress logo.

running an HP elitedesk 800 G1 SFF with 16gb ram, i5 4690 cpu and an HD
4600 onboard graphics card.

It's either the linux system or old flash drives causing it. Don't think
its the circuit boards.

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

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

Title:
  file transfers have trouble finishing

Status in wayland package in Ubuntu:
  New

Bug description:
  Ubuntu 21.10 with wayland windowing system sits on completed file
  transfers on and off usb and takes its time realising its finished and
  closing the little transfer progress logo.

  running an HP elitedesk 800 G1 SFF with 16gb ram, i5 4690 cpu and an
  HD 4600 onboard graphics card.

  It's either the linux system or old flash drives causing it. Don't
  think its the circuit boards.

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


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

[Touch-packages] [Bug 1964560] Re: file transfers have trouble finishing

[Daniel van Vugt]

Flash drives are usually very slow devices. Next time a transfer has
trouble finishing please open a Terminal window and run:

  sync

If the command returns immediately then this is a Nautilus bug. If the
command does not return until the file transfer finishes then this is
either a kernel bug or just the slowness of the flash drive.

** Package changed: wayland (Ubuntu) => nautilus (Ubuntu)

** Tags added: impish

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

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

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

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

Title:
  file transfers have trouble finishing

Status in linux package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 21.10 with wayland windowing system sits on completed file
  transfers on and off usb and takes its time realising its finished and
  closing the little transfer progress logo.

  running an HP elitedesk 800 G1 SFF with 16gb ram, i5 4690 cpu and an
  HD 4600 onboard graphics card.

  It's either the linux system or old flash drives causing it. Don't
  think its the circuit boards.

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


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

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

[Mathew Hodson]

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

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

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

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  New

Bug description:
  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
 results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
 for deflateBound(). Since zlib project does not accept
 patches at the moment, the fix has been integrated into
 the DFLTCC pull request:
 https://github.com/madler/zlib/pull/410
 The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
 #include 
 #include 
 #include 
 int main() {
 Bytef in_buf[128], out_buf[1024];
 for (size_t i = 0; i < sizeof(in_buf); i++)
 in_buf[i] = rand();
 uLongf dest_len = compressBound(sizeof(in_buf));
 assert(dest_len <= sizeof(out_buf));
 int ret = compress(out_buf, &dest_len,
in_buf, sizeof(in_buf));
 assert(ret == Z_OK);
 }

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


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

[Touch-packages] [Bug 1958019]

[darnellkeithj]

Can't someone just make a kernel build for ubuntu or some widely used
Linux version and put it on github? There is a lot of patching going on
here but no good documentation on how to do it.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs

[Launchpad Bug Tracker]

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

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

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

Title:
  Setting DuplicateAddressDetection=none doesn't disable DAD for link-
  local IPs

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  A customer reported network disconnections on their storage 
  servers when running 'netplan apply'. The culprit was that
  they have link-local addresses configured and the Duplicate 
  Address Detection (DAD) mechanism was delaying the interfaces 
  from coming back up. 

  As a workaround we tried to disable DAD for the interfaces 
  but that's not working in Ubuntu 22.04:

  I've noticed that setting DuplicateAddressDetection=none for an
  interface with a link-local address (e.g., 169.254.*) via a 
  .network file added to /etc/systemd/network/ doesn't really 
  disable Duplicate Address Detection.

  OS and package versions:
  
   - Description:   Ubuntu Jammy Jellyfish (development branch). Release: 
22.04
   - systemd 249.5-2ubuntu4

  Reproducer:
  ---
  1- Set up Ubuntu 22.04 VM
  2- Increase systemlog level:

mkdir -p /etc/systemd/system/systemd-networkd.service.d/
cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf