[Touch-packages] [Bug 1970081] Re: The background image of the login window cannot be changed

[Martin Wimpress ]

Slick Greeter is back in Ubuntu MATE 24.10 and has a configuration tool
for change the background. Closed via
https://launchpad.net/ubuntu/+source/ubuntu-mate-settings/24.10.1

** Changed in: ubuntu-mate
   Status: New => Fix Released

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

Title:
  The background image of the login window cannot be changed

Status in Ubuntu MATE:
  Fix Released
Status in arctica-greeter package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 20.04 Mate to 22.04 Mate, my custom
  wallpaper was replaced with the default one. I can make a change via
  the menu, but it stays with the default background image.

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


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

[Touch-packages] [Bug 2081302] Re: Graphical crash loop on fresh installation

[Martin Wimpress ]

Closed for Ubuntu MATE via https://launchpad.net/ubuntu/+source/ubuntu-
mate-settings/24.10.1

** Changed in: ubuntu-mate
   Status: New => Fix Released

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

Title:
  Graphical crash loop on fresh installation

Status in Ubuntu MATE:
  Fix Released
Status in Ubuntu Unity:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Upon fresh install of Ubuntu Mate 24.10 beta 
(http://cdimage.ubuntu.com/ubuntu-mate/daily-live/20240918.1/oracular-desktop-amd64.iso),
 the installation completes successfully, but the reboot ends up in a kind of 
graphical crash loop.
  The mouse regularly warps back to the middle of the ever black screen.

  From time to time, I see a bunch of scrambled console output (see
  screenshot attached).

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


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

[Touch-packages] [Bug 2073776] Re: nsswitch.conf "passwd" entry misses "systemd", breaking DynamicUser=yes systemd units

[Martin Pitt]

OK, thanks for confirming!

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

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

Title:
  nsswitch.conf "passwd" entry misses "systemd", breaking
  DynamicUser=yes systemd units

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The 321-1~bpo22.04.1 version of cockpit-ws calls the cockpit user 
"cockpit-wsinstance":
  $ cat usr/lib/sysusers.d/cockpit-wsinstance.conf
  u cockpit-wsinstance - "User for cockpit-ws instances" -

  However the following systemd files still reference the old "cockpit-ws" 
username, so the service fails to start:
  $ grep -r cockpit-ws$ lib/systemd/system
  lib/systemd/system/cockpit-ws-user.service:Description=Dynamic user for 
cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:User=cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-https@.socket:SocketUser=cockpit-ws
  
lib/systemd/system/cockpit-wsinstance-https-factory.socket:SocketUser=cockpit-ws
  lib/systemd/system/cockpit.service:User=cockpit-ws
  lib/systemd/system/cockpit.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-http.socket:SocketUser=cockpit-ws

  Can these systemd files be updated to use the new username? Thanks!

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


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

[Touch-packages] [Bug 2073776] Re: nsswitch.conf "passwd" entry misses "systemd", breaking DynamicUser=yes systemd units

[Andrew Martin]

Yes, I had changed it with ansible

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

Title:
  nsswitch.conf "passwd" entry misses "systemd", breaking
  DynamicUser=yes systemd units

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The 321-1~bpo22.04.1 version of cockpit-ws calls the cockpit user 
"cockpit-wsinstance":
  $ cat usr/lib/sysusers.d/cockpit-wsinstance.conf
  u cockpit-wsinstance - "User for cockpit-ws instances" -

  However the following systemd files still reference the old "cockpit-ws" 
username, so the service fails to start:
  $ grep -r cockpit-ws$ lib/systemd/system
  lib/systemd/system/cockpit-ws-user.service:Description=Dynamic user for 
cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:User=cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-https@.socket:SocketUser=cockpit-ws
  
lib/systemd/system/cockpit-wsinstance-https-factory.socket:SocketUser=cockpit-ws
  lib/systemd/system/cockpit.service:User=cockpit-ws
  lib/systemd/system/cockpit.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-http.socket:SocketUser=cockpit-ws

  Can these systemd files be updated to use the new username? Thanks!

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


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

[Touch-packages] [Bug 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"

[Martin Schaaf]

My workaround is this command: "sudo fwts s4"
It hibernates the system without any change to the setup.
It is not very nice but works for now.

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

Title:
  systemctl hibernate error: "Call to Hibernate failed: Invalid
  argument"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped
  working.

  Trying to hibernate:
  systemctl hibernate

  I get:
  Call to Hibernate failed: Invalid argument

  systemctl status systemd-hibernate.service

  -
  × systemd-hibernate.service - Hibernate
   Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; 
static)
   Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 
1min 33s ago
 Docs: man:systemd-hibernate.service(8)
  Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate 
(code=exited, status=1/FAILURE)
 Main PID: 4473 (code=exited, status=1/FAILURE)
  CPU: 5ms

  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting 
systemd-hibernate.service - Hibernate...
  мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location 
to hibernate to: Invalid argument
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main 
process exited, code=exited, status=1/FAILURE
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed 
with result 'exit-code'.
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start 
systemd-hibernate.service - Hibernate.
  --

  Previous version (254.x) worked: swapfile(on EXT4 fs) is used to
  hibernate/resume, resume with resume_offset kernel parameters.

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


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

[Touch-packages] [Bug 2000001] Re: Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!!

[Martin-Éric Racine]

I really need to ask:

Have you narrowed down which package causes the issue? If yes, can you
please un-tag packages that are unrelated to the issue?

If you're just generally commenting on the relevance of enabling IPv6 on
standard Ubuntu installations, tagging all packages that perform network
configuration is the wrong approach.

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

Title:
  Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!!

Status in dhcp package in Ubuntu:
  New
Status in dhcpcd package in Ubuntu:
  New
Status in dhcpcd5 package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in network-manager-applet package in Ubuntu:
  New
Status in wicd package in Ubuntu:
  New

Bug description:
  Updated: 19.12.2022
  #

  Hi Support

  at startup of analysis:
  Wifi5/6 dropped randomly if ipv6 is enabled/disabled on 
gnome-network-manager-gui no Error on Logs! No red Kernel Messages.

  
  My Lab:
  At my Lab i disabled all ipv6 on my Subnet LAN Openwrt-Routers, and my Laptop 
loses "randomly" 20times a day the Internet but the Signal is 100% to the 
WIFI-Routers, no ping, no nslookup to first DSL-WAN Router possible.

  First Handling:
  After i manual enable/disable WIFI by switch is works again fast.

  
  Analysis:
  After some search on Net i disabled ipv6 in sysctl.conf !

  GTK-Apps Affected: seen on network-manager/network-manager-gnome/wicd
  Managers

  Hardware Change/Test:
  I tested / changed 3 different old wifi-5+ new wifi-6 intel AX 7260 HMW 
mini-pci-cards same problem!

  Now testing again..

  Thanks
  Linuxonlinehelp_eu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.4.0-135.152~18.04.2-generic 5.4.212
  Uname: Linux 5.4.0-135-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 18 11:24:20 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2021-08-19 (486 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IpRoute:
   default via 192.168.71.1 dev wlp3s0b1 proto dhcp metric 600
   169.254.0.0/16 dev wlp3s0b1 scope link metric 1000
   192.168.71.0/24 dev wlp3s0b1 proto kernel scope link src 192.168.71.123 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  http_proxy: http://127.0.0.1:8118/
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2022-06-30T19:17:37.737049
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp3s0b1  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
AXWIFI71bec4545b-24e6-40ef-a933-43121b9b819b  
/org/freedesktop/NetworkManager/ActiveConnection/3
   enp2s0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
   loloopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  no_proxy:

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


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

[Touch-packages] [Bug 2063154] Re: Wireguard imported with Network manager does not work after latest upgrade, wg-quick using the same config file works

[Martin Randau]

Well, with a new set of upgrades the problem seems to have resolved
itself.

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

Title:
  Wireguard imported with Network manager does not work after latest
  upgrade, wg-quick using the same config file works

Status in network-manager package in Ubuntu:
  New

Bug description:
  Until a few days ago, after some upgrade, wireguard config imported
  with Network manager worked ootb. Now, it does not, there is no
  handshake. Activating the same config file with wg-quick does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-1005.5-oem 6.8.1
  Uname: Linux 6.8.0-1005-oem x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 22:41:06 2024
  InstallationDate: Installed on 2024-04-08 (14 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
  IpRoute:
   default via 192.168.173.139 dev wlp1s0 proto dhcp src 192.168.173.61 metric 
600 
   192.168.173.0/24 dev wlp1s0 proto kernel scope link src 192.168.173.61 
metric 600
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE   STATE   IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION  
CON-UUID  CON-PATH  
  
   wlp1s0   wifi   connected   full  limited
   /org/freedesktop/NetworkManager/Devices/2  MR Net 1
f92fae58-e84a-487e-9bdd-8d1ffbf8ca17  
/org/freedesktop/NetworkManager/ActiveConnection/2  
   lo   loopback   connected (externally)  unknown   unknown
   /org/freedesktop/NetworkManager/Devices/1  lo  
6fc7aa03-b696-4081-a275-4dc81c74c13e  
/org/freedesktop/NetworkManager/ActiveConnection/1  
   P14s_wg  wireguard  connected (externally)  limited   limited
   /org/freedesktop/NetworkManager/Devices/4  P14s_wg 
40fadfce-b931-472f-b4cd-9922f77068ee  
/org/freedesktop/NetworkManager/ActiveConnection/14
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.46.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


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

[Touch-packages] [Bug 2063154] [NEW] Wireguard imported with Network manager does not work after latest upgrade, wg-quick using the same config file works

[Martin Randau]

Public bug reported:

Until a few days ago, after some upgrade, wireguard config imported with
Network manager worked ootb. Now, it does not, there is no handshake.
Activating the same config file with wg-quick does work.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager 1.46.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-1005.5-oem 6.8.1
Uname: Linux 6.8.0-1005-oem x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 22 22:41:06 2024
InstallationDate: Installed on 2024-04-08 (14 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
IpRoute:
 default via 192.168.173.139 dev wlp1s0 proto dhcp src 192.168.173.61 metric 
600 
 192.168.173.0/24 dev wlp1s0 proto kernel scope link src 192.168.173.61 metric 
600
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE   STATE   IP4-CONNECTIVITY  IP6-CONNECTIVITY 
 DBUS-PATH  CONNECTION  CON-UUID
  CON-PATH
 wlp1s0   wifi   connected   full  limited  
 /org/freedesktop/NetworkManager/Devices/2  MR Net 1
f92fae58-e84a-487e-9bdd-8d1ffbf8ca17  
/org/freedesktop/NetworkManager/ActiveConnection/2  
 lo   loopback   connected (externally)  unknown   unknown  
 /org/freedesktop/NetworkManager/Devices/1  lo  
6fc7aa03-b696-4081-a275-4dc81c74c13e  
/org/freedesktop/NetworkManager/ActiveConnection/1  
 P14s_wg  wireguard  connected (externally)  limited   limited  
 /org/freedesktop/NetworkManager/Devices/4  P14s_wg 
40fadfce-b931-472f-b4cd-9922f77068ee  
/org/freedesktop/NetworkManager/ActiveConnection/14
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.46.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


** Tags: amd64 apport-bug noble wayland-session

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

Title:
  Wireguard imported with Network manager does not work after latest
  upgrade, wg-quick using the same config file works

Status in network-manager package in Ubuntu:
  New

Bug description:
  Until a few days ago, after some upgrade, wireguard config imported
  with Network manager worked ootb. Now, it does not, there is no
  handshake. Activating the same config file with wg-quick does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-1005.5-oem 6.8.1
  Uname: Linux 6.8.0-1005-oem x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 22:41:06 2024
  InstallationDate: Installed on 2024-04-08 (14 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
  IpRoute:
   default via 192.168.173.139 dev wlp1s0 proto dhcp src 192.168.173.61 metric 
600 
   192.168.173.0/24 dev wlp1s0 proto kernel scope link src 192.168.173.61 
metric 600
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE   STATE   IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION  
CON-UUID  CON-PATH  
  
   wlp1s0   wifi   connected   full  limited
   /org/freedesktop/NetworkManager/Devices/2  MR Net 1
f92fae58-e84a-487e-9bdd-8d1ffbf8ca17  
/org/freedesktop/NetworkManager/ActiveConnection/2  
   lo   loopback   connected (externally)  unknown   unknown
   /org/freedesktop/NetworkManager/Devices/1  lo  
6fc7aa03-b696-4081-a275-4dc81c74c13e  
/org/freedesktop/NetworkManager/ActiveConnection/1  
   P14s_wg  wireguard  connected (externally)  limited   limited
   /org/freedesktop/NetworkManager/Devices/4  P14s_wg 
40fadfce-b931-472f-b4cd-9922f77068ee  
/org/freedesktop/NetworkManager/ActiveConnection/14
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.46.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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

[Touch-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

[Martin Wimpress ]

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: Triaged => In Progress

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: In Progress => Fix Committed

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Fix Committed
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

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


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

[Touch-packages] [Bug 2061726] [NEW] rsyslog apparmor denial on reading /proc/sys/net/ipv6/conf/all/disable_ipv6

[Martin Pitt]

Public bug reported:

One of our Cockpit integration tests [1] spotted an AppArmor regression
in rsyslogd. This is coincidental, the test passes and it doesn't do
anything with rsyslogd -- just something happens to happen in the
background to trigger this (and I can actually reproduce it locally
quite reliably).


Mar 08 10:48:20 m1.cockpit.lan systemd[1]: dpkg-db-backup.service: Deactivated 
successfully.
Mar 08 10:48:20 m1.cockpit.lan systemd[1]: Finished dpkg-db-backup.service - 
Daily dpkg database backup service.
Mar 08 10:48:20 m1.cockpit.lan systemd[1]: rsyslog.service: Sent signal SIGHUP 
to main process 752 (rsyslogd) on client request.
Mar 08 10:48:20 m1.cockpit.lan kernel: audit: type=1400 
audit(1615200500.418:125): apparmor="DENIED" operation="open" class="file" 
profile="rsyslogd" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=752 
comm="rsyslogd" requested_mask="r" denied_mask="r" fsuid=102 ouid=0
Mar 08 10:48:20 m1.cockpit.lan kernel: audit: type=1400 
audit(1615200500.418:126): apparmor="DENIED" operation="open" class="file" 
profile="rsyslogd" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=752 
comm="rsyslogd" requested_mask="r" denied_mask="r" fsuid=102 ouid=0


This happens on current Ubuntu 24.04 LTS noble devel, rsyslog 8.2312.0-3ubuntu8 
and apparmor 4.0.0-beta3-0ubuntu3.

[1] 
https://cockpit-logs.us-east-1.linodeobjects.com/pull-20317-ce39e07e-20240415-204952-ubuntu-stable-other/log.html#152
[2] 
https://cockpit-logs.us-east-1.linodeobjects.com/pull-20317-ce39e07e-20240415-204952-ubuntu-stable-other/TestHistoryMetrics-testEvents-ubuntu-stable-127.0.0.2-2901-FAIL.log.gz

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


** Tags: apparmor noble

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

Title:
  rsyslog apparmor denial on reading
  /proc/sys/net/ipv6/conf/all/disable_ipv6

Status in rsyslog package in Ubuntu:
  New

Bug description:
  One of our Cockpit integration tests [1] spotted an AppArmor
  regression in rsyslogd. This is coincidental, the test passes and it
  doesn't do anything with rsyslogd -- just something happens to happen
  in the background to trigger this (and I can actually reproduce it
  locally quite reliably).

  
  Mar 08 10:48:20 m1.cockpit.lan systemd[1]: dpkg-db-backup.service: 
Deactivated successfully.
  Mar 08 10:48:20 m1.cockpit.lan systemd[1]: Finished dpkg-db-backup.service - 
Daily dpkg database backup service.
  Mar 08 10:48:20 m1.cockpit.lan systemd[1]: rsyslog.service: Sent signal 
SIGHUP to main process 752 (rsyslogd) on client request.
  Mar 08 10:48:20 m1.cockpit.lan kernel: audit: type=1400 
audit(1615200500.418:125): apparmor="DENIED" operation="open" class="file" 
profile="rsyslogd" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=752 
comm="rsyslogd" requested_mask="r" denied_mask="r" fsuid=102 ouid=0
  Mar 08 10:48:20 m1.cockpit.lan kernel: audit: type=1400 
audit(1615200500.418:126): apparmor="DENIED" operation="open" class="file" 
profile="rsyslogd" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=752 
comm="rsyslogd" requested_mask="r" denied_mask="r" fsuid=102 ouid=0

  
  This happens on current Ubuntu 24.04 LTS noble devel, rsyslog 
8.2312.0-3ubuntu8 and apparmor 4.0.0-beta3-0ubuntu3.

  [1] 
https://cockpit-logs.us-east-1.linodeobjects.com/pull-20317-ce39e07e-20240415-204952-ubuntu-stable-other/log.html#152
  [2] 
https://cockpit-logs.us-east-1.linodeobjects.com/pull-20317-ce39e07e-20240415-204952-ubuntu-stable-other/TestHistoryMetrics-testEvents-ubuntu-stable-127.0.0.2-2901-FAIL.log.gz

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


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

[Touch-packages] [Bug 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

I also tried removing the Mesa Vulkan driver and set `export
LIBVA_DRIVER_NAME=i965`.  That gets rid of the warning message but I
still get a hang with Vivaldi and nextcloud-desktop still does not work.

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

Thanks. Sounds similar.  My nautilus and gnome-control center do work
strangely enough.   But the more clues the better.

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

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

** Project changed: wayland => wayland (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/2061257

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in wayland package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

I tried the same upgrade and test on an old Sandy Bridge laptop.
Everything works as expected there.  So a Haswell issue perhaps?

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

I tried the same test on an old Sandy Bridge laptop.  Everything works
as expected there.  So a Haswell issue?

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2061257] Re: With 24.04: Many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

** Summary changed:

- Many app failures under Wayland; no  issues with Xorg
+ With 24.04: Many graphical app failures under Wayland; no  issues with Xorg

** Summary changed:

- With 24.04: Many graphical app failures under Wayland; no  issues with Xorg
+ After 24.04 upgrade, many graphical app failures under Wayland; no  issues 
with Xorg

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2061257] [NEW] Many app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

Public bug reported:

Many applications seem to fail under a Wayland session that work correctly with 
an Xorg session. E.g.
- The nextcloud client app fails to contact the server and functions in the app 
will not launch with Wayland while they work perfectly in Xorg
- The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
- The Slack app works correct in Xorg not in Wayland.
- The Firefox snap works fine in both.

I assume that these are related?  Esp. that latter suggests to me that
there is some library problem?

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 19:58:00 2024
DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2021-11-11 (885 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20ARA0S100
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
dmi.bios.date: 03/19/2014
dmi.bios.release: 2.24
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET74WW (2.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ARA0S100
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: Not Available
dmi.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20ARA0S100
dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble 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/2061257

Title:
  Many app failures under Wayland; no  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [V

[Touch-packages] [Bug 2061257] Re: Many app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

I should also mention: this was an upgrade from 23.10 to 24.04 and all
of the apps worked correctly in 23.10.

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

Title:
  Many app failures under Wayland; no  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2061055] Re: Joining IPA domain does not restart ssh -- 'sshd.service' alias is not set up by default

[Martin Pitt]

Yeah, I could live with that -- but TBH I still consider this mostly a
bug in openssh. querying the status of sshd.service really should work.
Arch, RHEL, Fedora, OpenSUSE etc. all call this sshd.service.

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

Title:
  Joining IPA domain does not restart ssh -- 'sshd.service' alias is not
  set up by default

Status in freeipa package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New

Bug description:
  Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
  authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
  tries to restart sshd, but that fails as "sshd.service" is not a thing
  on Ubuntu:

  2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl', 'is-active', 
'sshd.service']
  2024-04-12T03:10:57Z DEBUG Process finished, return code=4

  (in /var/log/ipaclient-install.log)

  While that could be changed in freeipa, I'd argue that this is really
  a bug in Ubuntu's openssh package. Many upstream software, Ansible
  scripts etc. assume that the service is "sshd.service". In
  Debian/Ubuntu the primary unit is "ssh.service", but it has an
  `[Install] Alias=sshd.service`. That works in Debian because there
  sshd.service *actually* gets enabled by default, and ssh.socket isn't.

  But Ubuntu moved to socket activation (which is good!), so that
  ssh.socket is running by default. But that means that ssh.service
  never gets "systemctl enable"d, and hence the alias never gets set up:

  # systemctl status sshd.service
  Unit sshd.service could not be found.

  So if ssh.service is already running, it never gets restarted by "ipa-
  client-install".

  It would be really good to make that alias work by default -- if
  nothing else, just ship the symlink in the .deb, or create the symlink
  manually in the postinst?

  freeipa-client 4.10.2-2ubuntu3
  openssh-server 1:9.6p1-3ubuntu12

  Note: we have tested this functionality in Cockpit on Ubuntu for a long time 
already. But until very recently we had a workaround to force the creation of 
that alias:
  
https://github.com/cockpit-project/bots/commit/3bf1b20f3fa5fe202b9710b3fe78d2133ba03f5d
  We dropped it because it broke image builds due to some bugs in openssh's 
postinst, but it was a bad one anyway: actual users don't have that hack, and 
it hides bugs like this.

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


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

[Touch-packages] [Bug 2061055] Re: Joining IPA domain does not restart ssh -- 'sshd.service' alias is not set up by default

[Martin Pitt]

Timo: It doesn't fail on Debian. See the "That works in Debian
because.." in the description (TL/DR: Debian doesn't enable ssh.socket,
but ssh.service, which sets up the symlink)

** Description changed:

  Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
  authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
  tries to restart sshd, but that fails as "sshd.service" is not a thing
  on Ubuntu:
  
  2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl', 'is-active', 
'sshd.service']
  2024-04-12T03:10:57Z DEBUG Process finished, return code=4
  
  (in /var/log/ipaclient-install.log)
  
  While that could be changed in freeipa, I'd argue that this is really a
  bug in Ubuntu's openssh package. Many upstream software, Ansible scripts
  etc. assume that the service is "sshd.service". In Debian/Ubuntu the
  primary unit is "ssh.service", but it has an `[Install]
  Alias=sshd.service`. That works in Debian because there sshd.service
  *actually* gets enabled by default, and ssh.socket isn't.
  
  But Ubuntu moved to socket activation (which is good!), so that
  ssh.socket is running by default. But that means that ssh.service never
  gets "systemctl enable"d, and hence the alias never gets set up:
  
  # systemctl status sshd.service
  Unit sshd.service could not be found.
  
  So if ssh.service is already running, it never gets restarted by "ipa-
  client-install".
  
  It would be really good to make that alias work by default -- if nothing
- else, just create the symlink manually in the postinst?
+ else, just ship the symlink in the .deb, or create the symlink manually
+ in the postinst?
  
  freeipa-client 4.10.2-2ubuntu3
  openssh-server 1:9.6p1-3ubuntu12
  
- 
  Note: we have tested this functionality in Cockpit on Ubuntu for a long time 
already. But until very recently we had a workaround to force the creation of 
that alias:
  
https://github.com/cockpit-project/bots/commit/3bf1b20f3fa5fe202b9710b3fe78d2133ba03f5d
  We dropped it because it broke image builds due to some bugs in openssh's 
postinst, but it was a bad one anyway: actual users don't have that hack, and 
it hides bugs like this.

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

Title:
  Joining IPA domain does not restart ssh -- 'sshd.service' alias is not
  set up by default

Status in freeipa package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New

Bug description:
  Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
  authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
  tries to restart sshd, but that fails as "sshd.service" is not a thing
  on Ubuntu:

  2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl', 'is-active', 
'sshd.service']
  2024-04-12T03:10:57Z DEBUG Process finished, return code=4

  (in /var/log/ipaclient-install.log)

  While that could be changed in freeipa, I'd argue that this is really
  a bug in Ubuntu's openssh package. Many upstream software, Ansible
  scripts etc. assume that the service is "sshd.service". In
  Debian/Ubuntu the primary unit is "ssh.service", but it has an
  `[Install] Alias=sshd.service`. That works in Debian because there
  sshd.service *actually* gets enabled by default, and ssh.socket isn't.

  But Ubuntu moved to socket activation (which is good!), so that
  ssh.socket is running by default. But that means that ssh.service
  never gets "systemctl enable"d, and hence the alias never gets set up:

  # systemctl status sshd.service
  Unit sshd.service could not be found.

  So if ssh.service is already running, it never gets restarted by "ipa-
  client-install".

  It would be really good to make that alias work by default -- if
  nothing else, just ship the symlink in the .deb, or create the symlink
  manually in the postinst?

  freeipa-client 4.10.2-2ubuntu3
  openssh-server 1:9.6p1-3ubuntu12

  Note: we have tested this functionality in Cockpit on Ubuntu for a long time 
already. But until very recently we had a workaround to force the creation of 
that alias:
  
https://github.com/cockpit-project/bots/commit/3bf1b20f3fa5fe202b9710b3fe78d2133ba03f5d
  We dropped it because it broke image builds due to some bugs in openssh's 
postinst, but it was a bad one anyway: actual users don't have that hack, and 
it hides bugs like this.

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


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

[Touch-packages] [Bug 2061055] [NEW] Joining IPA domain does not restart ssh -- 'sshd.service' alias is not set up by default

[Martin Pitt]

Public bug reported:

Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
tries to restart sshd, but that fails as "sshd.service" is not a thing
on Ubuntu:

2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl', 'is-active', 'sshd.service']
2024-04-12T03:10:57Z DEBUG Process finished, return code=4

(in /var/log/ipaclient-install.log)

While that could be changed in freeipa, I'd argue that this is really a
bug in Ubuntu's openssh package. Many upstream software, Ansible scripts
etc. assume that the service is "sshd.service". In Debian/Ubuntu the
primary unit is "ssh.service", but it has an `[Install]
Alias=sshd.service`. That works in Debian because there sshd.service
*actually* gets enabled by default, and ssh.socket isn't.

But Ubuntu moved to socket activation (which is good!), so that
ssh.socket is running by default. But that means that ssh.service never
gets "systemctl enable"d, and hence the alias never gets set up:

# systemctl status sshd.service
Unit sshd.service could not be found.

So if ssh.service is already running, it never gets restarted by "ipa-
client-install".

It would be really good to make that alias work by default -- if nothing
else, just create the symlink manually in the postinst?

freeipa-client 4.10.2-2ubuntu3
openssh-server 1:9.6p1-3ubuntu12


Note: we have tested this functionality in Cockpit on Ubuntu for a long time 
already. But until very recently we had a workaround to force the creation of 
that alias:
https://github.com/cockpit-project/bots/commit/3bf1b20f3fa5fe202b9710b3fe78d2133ba03f5d
We dropped it because it broke image builds due to some bugs in openssh's 
postinst, but it was a bad one anyway: actual users don't have that hack, and 
it hides bugs like this.

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

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

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

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

Title:
  Joining IPA domain does not restart ssh -- 'sshd.service' alias is not
  set up by default

Status in freeipa package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New

Bug description:
  Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
  authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
  tries to restart sshd, but that fails as "sshd.service" is not a thing
  on Ubuntu:

  2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl', 'is-active', 
'sshd.service']
  2024-04-12T03:10:57Z DEBUG Process finished, return code=4

  (in /var/log/ipaclient-install.log)

  While that could be changed in freeipa, I'd argue that this is really
  a bug in Ubuntu's openssh package. Many upstream software, Ansible
  scripts etc. assume that the service is "sshd.service". In
  Debian/Ubuntu the primary unit is "ssh.service", but it has an
  `[Install] Alias=sshd.service`. That works in Debian because there
  sshd.service *actually* gets enabled by default, and ssh.socket isn't.

  But Ubuntu moved to socket activation (which is good!), so that
  ssh.socket is running by default. But that means that ssh.service
  never gets "systemctl enable"d, and hence the alias never gets set up:

  # systemctl status sshd.service
  Unit sshd.service could not be found.

  So if ssh.service is already running, it never gets restarted by "ipa-
  client-install".

  It would be really good to make that alias work by default -- if
  nothing else, just create the symlink manually in the postinst?

  freeipa-client 4.10.2-2ubuntu3
  openssh-server 1:9.6p1-3ubuntu12

  
  Note: we have tested this functionality in Cockpit on Ubuntu for a long time 
already. But until very recently we had a workaround to force the creation of 
that alias:
  
https://github.com/cockpit-project/bots/commit/3bf1b20f3fa5fe202b9710b3fe78d2133ba03f5d
  We dropped it because it broke image builds due to some bugs in openssh's 
postinst, but it was a bad one anyway: actual users don't have that hack, and 
it hides bugs like this.

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


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

[Touch-packages] [Bug 2060615] Re: [noble] two versions of perl-modules are published, breaking pbuilder/debootstrap

[Martin Pitt]

Yay, today this is finally fixed, pbuilder creation and building a noble
VM image finally works again \o/ Thanks!

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

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

Title:
  [noble] two versions of perl-modules are published, breaking
  pbuilder/debootstrap

Status in perl package in Ubuntu:
  Fix Released
Status in perl source package in Noble:
  Fix Released

Bug description:
  For the last two weeks, building noble VM images for our CI has been
  broken. Most of it was uninstallability due to the xz reset, but for
  the last three days, `pbuilder --create` has failed [2] because it
  gets perl and perl-modules-5.38 in two different versions:

  2024-04-08 08:47:08 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-base_5.38.2-3.2build2_amd64.deb
 [1822564/1822564] -> 
"/var/cache/pbuilder/aptcache//perl-base_5.38.2-3.2build2_amd64.deb" [1]
  2024-04-08 08:47:09 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-modules-5.38_5.38.2-3_all.deb
 [3110080/3110080] -> 
"/var/cache/pbuilder/aptcache//perl-modules-5.38_5.38.2-3_all.deb" [1]

  and then trying to configure the packages blows up. The root cause is
  that perl-modules has *two* versions published:


  # curl -s 
http://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.xz|xzgrep
 -A5 'Package: perl-modules-'
  Package: perl-modules-5.38
  Architecture: all
  Version: 5.38.2-3.2build2
  Multi-Arch: foreign
  Priority: optional
  Build-Essential: yes
  --
  Package: perl-modules-5.38
  Architecture: all
  Version: 5.38.2-3
  Multi-Arch: foreign
  Priority: optional
  Build-Essential: yes

  While apt is clever enough to pick the right one, debootstrap isn't.
  Can you please remove the old perl-modules-5.38 5.38.2-3 from noble?

  Thanks!

  
  [1] https://github.com/cockpit-project/bots/issues/6147
  [2] 
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-ubuntu-stable-02cafde3-20240407-074108/log.html

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


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

[Touch-packages] [Bug 2060615] Re: [noble] two versions of perl-modules are published, breaking debootstrap

[Martin Pitt]

Aside from curl this can be reproduced most quickly with

  sudo /usr/sbin/debootstrap --include=build-essential noble /tmp/n
http://archive.ubuntu.com/ubuntu

Errors were encountered while processing:
 perl
 libdpkg-perl
 libperl5.38t64:amd64
 dpkg-dev
 build-essential

These are all ultimately due to

dpkg: dependency problems prevent configuration of perl:
 perl depends on perl-modules-5.38 (>= 5.38.2-3.2build2); however:
  Version of perl-modules-5.38 on system is 5.38.2-3.

dpkg: error processing package perl (--configure):
 dependency problems - leaving unconfigured


** Tags added: debootstrap noble

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

Title:
  [noble] two versions of perl-modules are published, breaking
  pbuilder/debootstrap

Status in perl package in Ubuntu:
  New
Status in perl source package in Noble:
  New

Bug description:
  For the last two weeks, building noble VM images for our CI has been
  broken. Most of it was uninstallability due to the xz reset, but for
  the last three days, `pbuilder --create` has failed [2] because it
  gets perl and perl-modules-5.38 in two different versions:

  2024-04-08 08:47:08 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-base_5.38.2-3.2build2_amd64.deb
 [1822564/1822564] -> 
"/var/cache/pbuilder/aptcache//perl-base_5.38.2-3.2build2_amd64.deb" [1]
  2024-04-08 08:47:09 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-modules-5.38_5.38.2-3_all.deb
 [3110080/3110080] -> 
"/var/cache/pbuilder/aptcache//perl-modules-5.38_5.38.2-3_all.deb" [1]

  and then trying to configure the packages blows up. The root cause is
  that perl-modules has *two* versions published:


  # curl -s 
http://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.xz|xzgrep
 -A5 'Package: perl-modules-'
  Package: perl-modules-5.38
  Architecture: all
  Version: 5.38.2-3.2build2
  Multi-Arch: foreign
  Priority: optional
  Build-Essential: yes
  --
  Package: perl-modules-5.38
  Architecture: all
  Version: 5.38.2-3
  Multi-Arch: foreign
  Priority: optional
  Build-Essential: yes

  While apt is clever enough to pick the right one, debootstrap isn't.
  Can you please remove the old perl-modules-5.38 5.38.2-3 from noble?

  Thanks!

  
  [1] https://github.com/cockpit-project/bots/issues/6147
  [2] 
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-ubuntu-stable-02cafde3-20240407-074108/log.html

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


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

[Touch-packages] [Bug 2060615] Re: [noble] two versions of perl-modules are published, breaking debootstrap

[Martin Pitt]

I wonder where that comes from --
https://launchpad.net/ubuntu/+source/perl/+publishinghistory says that
5.38.2-3 was deleted, but only from noble-updates. In noble proper it is
merely "superseded". https://launchpad.net/ubuntu/+source/perl/5.38.2-3
doesn't show it being published anyway, and it's not in https://ubuntu-
archive-team.ubuntu.com/nbs.html either.

** Summary changed:

- [noble] two versions of perl-modules are published, breaking debootstrap
+ [noble] two versions of perl-modules are published, breaking 
pbuilder/debootstrap

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

Title:
  [noble] two versions of perl-modules are published, breaking
  pbuilder/debootstrap

Status in perl package in Ubuntu:
  New
Status in perl source package in Noble:
  New

Bug description:
  For the last two weeks, building noble VM images for our CI has been
  broken. Most of it was uninstallability due to the xz reset, but for
  the last three days, `pbuilder --create` has failed [2] because it
  gets perl and perl-modules-5.38 in two different versions:

  2024-04-08 08:47:08 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-base_5.38.2-3.2build2_amd64.deb
 [1822564/1822564] -> 
"/var/cache/pbuilder/aptcache//perl-base_5.38.2-3.2build2_amd64.deb" [1]
  2024-04-08 08:47:09 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-modules-5.38_5.38.2-3_all.deb
 [3110080/3110080] -> 
"/var/cache/pbuilder/aptcache//perl-modules-5.38_5.38.2-3_all.deb" [1]

  and then trying to configure the packages blows up. The root cause is
  that perl-modules has *two* versions published:


  # curl -s 
http://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.xz|xzgrep
 -A5 'Package: perl-modules-'
  Package: perl-modules-5.38
  Architecture: all
  Version: 5.38.2-3.2build2
  Multi-Arch: foreign
  Priority: optional
  Build-Essential: yes
  --
  Package: perl-modules-5.38
  Architecture: all
  Version: 5.38.2-3
  Multi-Arch: foreign
  Priority: optional
  Build-Essential: yes

  While apt is clever enough to pick the right one, debootstrap isn't.
  Can you please remove the old perl-modules-5.38 5.38.2-3 from noble?

  Thanks!

  
  [1] https://github.com/cockpit-project/bots/issues/6147
  [2] 
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-ubuntu-stable-02cafde3-20240407-074108/log.html

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


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

[Touch-packages] [Bug 2060615] [NEW] [noble] two versions of perl-modules are published, breaking pbuilder/debootstrap

[Martin Pitt]

Public bug reported:

For the last two weeks, building noble VM images for our CI has been
broken. Most of it was uninstallability due to the xz reset, but for the
last three days, `pbuilder --create` has failed [2] because it gets perl
and perl-modules-5.38 in two different versions:

2024-04-08 08:47:08 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-base_5.38.2-3.2build2_amd64.deb
 [1822564/1822564] -> 
"/var/cache/pbuilder/aptcache//perl-base_5.38.2-3.2build2_amd64.deb" [1]
2024-04-08 08:47:09 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-modules-5.38_5.38.2-3_all.deb
 [3110080/3110080] -> 
"/var/cache/pbuilder/aptcache//perl-modules-5.38_5.38.2-3_all.deb" [1]

and then trying to configure the packages blows up. The root cause is
that perl-modules has *two* versions published:


# curl -s 
http://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.xz|xzgrep
 -A5 'Package: perl-modules-'
Package: perl-modules-5.38
Architecture: all
Version: 5.38.2-3.2build2
Multi-Arch: foreign
Priority: optional
Build-Essential: yes
--
Package: perl-modules-5.38
Architecture: all
Version: 5.38.2-3
Multi-Arch: foreign
Priority: optional
Build-Essential: yes

While apt is clever enough to pick the right one, debootstrap isn't. Can
you please remove the old perl-modules-5.38 5.38.2-3 from noble?

Thanks!


[1] https://github.com/cockpit-project/bots/issues/6147
[2] 
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-ubuntu-stable-02cafde3-20240407-074108/log.html

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

** Affects: perl (Ubuntu Noble)
 Importance: Undecided
 Status: New


** Tags: debootstrap noble

** Also affects: perl (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

Title:
  [noble] two versions of perl-modules are published, breaking
  pbuilder/debootstrap

Status in perl package in Ubuntu:
  New
Status in perl source package in Noble:
  New

Bug description:
  For the last two weeks, building noble VM images for our CI has been
  broken. Most of it was uninstallability due to the xz reset, but for
  the last three days, `pbuilder --create` has failed [2] because it
  gets perl and perl-modules-5.38 in two different versions:

  2024-04-08 08:47:08 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-base_5.38.2-3.2build2_amd64.deb
 [1822564/1822564] -> 
"/var/cache/pbuilder/aptcache//perl-base_5.38.2-3.2build2_amd64.deb" [1]
  2024-04-08 08:47:09 
URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-modules-5.38_5.38.2-3_all.deb
 [3110080/3110080] -> 
"/var/cache/pbuilder/aptcache//perl-modules-5.38_5.38.2-3_all.deb" [1]

  and then trying to configure the packages blows up. The root cause is
  that perl-modules has *two* versions published:


  # curl -s 
http://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.xz|xzgrep
 -A5 'Package: perl-modules-'
  Package: perl-modules-5.38
  Architecture: all
  Version: 5.38.2-3.2build2
  Multi-Arch: foreign
  Priority: optional
  Build-Essential: yes
  --
  Package: perl-modules-5.38
  Architecture: all
  Version: 5.38.2-3
  Multi-Arch: foreign
  Priority: optional
  Build-Essential: yes

  While apt is clever enough to pick the right one, debootstrap isn't.
  Can you please remove the old perl-modules-5.38 5.38.2-3 from noble?

  Thanks!

  
  [1] https://github.com/cockpit-project/bots/issues/6147
  [2] 
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-ubuntu-stable-02cafde3-20240407-074108/log.html

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


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

[Touch-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

[Martin Wimpress ]

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => Won't Fix

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in edubuntu-meta package in Ubuntu:
  Won't Fix
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Won't Fix
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  Won't Fix
Status in xubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

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


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

[Touch-packages] [Bug 2056739] Re: apparmor="DENIED" operation="open" class="file" profile="virt-aa-helper" name="/etc/gnutls/config"

[Martin Pitt]

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

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

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

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

Title:
  apparmor="DENIED" operation="open" class="file" profile="virt-aa-
  helper" name="/etc/gnutls/config"

Status in apparmor package in Ubuntu:
  In Progress
Status in chrony package in Ubuntu:
  Won't Fix
Status in gnutls28 package in Ubuntu:
  Won't Fix
Status in libvirt package in Ubuntu:
  Won't Fix
Status in apparmor source package in Noble:
  In Progress
Status in chrony source package in Noble:
  Won't Fix
Status in gnutls28 source package in Noble:
  Won't Fix
Status in libvirt source package in Noble:
  Won't Fix

Bug description:
  Christian summarizes this after the great reports by Martin:

  gnutls started to ship forceful disables in pkg/import/3.8.1-4ubuntu3
  and added more later.

  Due to that anything linked against gnutls while being apparmor
  isolated now hits similar denials, preventing the desired effect of
  the config change BTW.

  I think for safety we WANT to always allow this access, otherwise
  people will subtly not have crypto control about the more important
  (those isolated) software. Because after the denial I'd expect this to
  not really disable it in the program linked to gnutls (details might
  vary depending what they really use gnutls for).

  I do not nkow of a gnutls abstraction to use, but TBH I'm afraid now
  fixing a few but leaving this open in some others not spotted.

  I'd therefore suggest, but we need to discuss, to therefore change it
  in /etc/apparmor.d/abstractions/base.

  Therefore I'm adding gnutls (and Adrien) as well as apparmor to the
  bug tasks.

  
  --- --- --- --- --- --- --- --- --- --- --- ---
  --- --- --- --- --- --- --- --- --- --- --- ---

  
  Merely booting current noble cloud image with "chrony" installed causes this:

  audit: type=1400 audit(1710152842.540:107): apparmor="DENIED"
  operation="open" class="file" profile="/usr/sbin/chronyd"
  name="/etc/gnutls/config" pid=878 comm="chronyd" requested_mask="r"
  denied_mask="r" fsuid=0 ouid=0

  
  --- --- --- --- --- --- --- --- --- --- --- ---
  --- --- --- --- --- --- --- --- --- --- --- ---

  
  Running any VM in libvirt causes a new AppArmor violation in current noble. 
This is a regression, this didn't happen in any previous release.

  Reproducer:

    virt-install --memory 50 --pxe --virt-type qemu --os-variant
  alpinelinux3.8 --disk none --wait 0 --name test1

  (This is the simplest way to create a test VM. But it's form or shape
  doesn't matter at all).

  Results in lots of

  audit: type=1400 audit(1710146677.570:108): apparmor="DENIED"
  operation="open" class="file" profile="virt-aa-helper"
  name="/etc/gnutls/config" pid=1480 comm="virt-aa-helper"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  libvirt-daemon 10.0.0-2ubuntu1
  apparmor 4.0.0~alpha4-0ubuntu1
  libgnutls30:amd64 3.8.3-1ubuntu1

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


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

[Touch-packages] [Bug 2046477] Re: Enable unprivileged user namespace restrictions by default

[Martin Pitt]

Just to make sure that we really talk about the same thing: This bug
sounds like it is *intended* that

unshare --user --map-root-user /bin/bash -c whoami

(as unpriv user) now fails in current Ubuntu 24.04 noble. That still
worked in released 23.10.

I am starting to test Cockpit on the current noble dailies [1] to make
sure everything is ready for 24.04 LTS (as 23.10 was a bit of a
disaster..), and aside from some non-fatal AppAmor noise this is the
most important issue. This breaks /usr/lib/cockpit/cockpit-desktop ,
which uses an user namespace to isolate cockpit's web server + a
browser, and that isolation is absolutely crucial for its security.

I can update cockpit-ws.deb to ship a new file /etc/apparmor.d/cockpit-
desktop with

-- 8< ---
abi ,

include 

profile cockpit-desktop /usr/lib/cockpit/cockpit-desktop flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists 
}
-- 8< ---

I confirmed that this works fine. I just wanted to check that this is
intended, and not circumventing your intentions here?

Thanks!


[1] https://github.com/cockpit-project/bots/pull/6048

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

Title:
  Enable unprivileged user namespace restrictions by default

Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  As per https://discourse.ubuntu.com/t/spec-unprivileged-user-
  namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626,
  unprivileged user namespace restrictions for Ubuntu 23.10 are to be
  enabled by default via a sysctl.d conf file in apparmor, and for that
  to happen, the restrictions need to be enabled for 24.04

  When the unprivileged user namespace restrictions are enabled, various
  applications within and outside the Ubuntu archive fail to function,
  as they use unprivileged user namespaces as part of their normal
  operation.

  A search of the Ubuntu archive for the 23.10 release was performed
  looking for all applications that make legitimate use of the
  CLONE_NEWUSER argument, the details of which can be seen in
  
https://docs.google.com/spreadsheets/d/1MOPVoTW0BROF1TxYqoWeJ3c6w2xKElI4w-VjdCG0m9s/edit#gid=2102562502

  For each package identified in that list, an investigation was made to
  determine if the application actually used this as an unprivileged
  user, and if so which of the binaries within the package were
  affected.

  The full investigation can be seen in
  https://warthogs.atlassian.net/browse/SEC-1898 (which is unfortunately
  private) but is summarised to the following list of Ubuntu source
  packages, as well as some out-of-archive applications that are known
  to use unprivileged user namespaces.

  For each of these binaries, an apparmor profile is required so that
  the binary can be granted use of unprivileged user namespaces - an
  example profile for the ch-run binary within the charliecloud package
  is shown:

  $ cat /etc/apparmor.d/ch-run
  abi ,

  include 

  profile ch-run /usr/bin/ch-run flags=(unconfined) {
userns,

# Site-specific additions and overrides. See local/README for details.
include if exists 
  }

  However, in a few select cases, it has been decided not to ship an apparmor 
profile, since this would effectively allow this mitigation to be bypassed. In 
particular, the unshare and setns binaries within the util-linux package are 
installed on every Ubuntu system, and allow an unprivileged user the ability to 
launch an arbitrary application within a new user namespace. Any malicious 
application then that wished to exploit an unprivileged user namespace to 
conduct an attack on the kernel would simply need to spawn itself via `unshare 
-U` or similar to be granted this permission. Therefore, due to the ubiquitous 
nature of the unshare (and setns) binaries, profiles are not planned to be 
provided for these by default. 
  Similarly, the bwrap binary within bubblewrap is also installed by default on 
Ubuntu Desktop 24.04 and can also be used to launch arbitrary binaries within a 
new user namespace and so no profile is planned to be provided for this either.

  In Bug 2035315 new apparmor profiles were added to the apparmor
  package for various applications which require unprivileged user
  namespaces, using a new unconfined profile mode. They were also added
  in the AppArmor upstream project.

  As well as enabling the sysctl via the sysctl.d conf file, it is
  proposed to add logic into the apparmor.service systemd unit to check
  that the kernel supports the unconfined profile mode and that it is
  enabled - and if not then to force disable the userns restrictions
  sysctl via the following logic:

  userns_restricted=$(sysctl -n kernel.apparmor_restrict_unprivileged_userns)
  unconfined_userns=$([ -f 
/sys/kernel/security/apparmor/features/policy

[Touch-packages] [Bug 2056768] [NEW] apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/"

[Martin Pitt]

Public bug reported:

There is an AppArmor regression in current noble. In cockpit we recently
started to test on noble (to prevent the "major regressions after
release" fiasco from 23.10 again).

For some weird reason, rsyslog is installed *by default* [1] in the
cloud images. That is a rather pointless waste of CPU and disk space, as
it's an unnecessary running daemon and duplicates all the written logs.

But more specifically, we noticed [2] an AppArmor rejection. Reproducer
is simple:

logger -p user.emerg --tag check-journal EMERGENCY_MESSAGE

this causes

type=1400 audit(1710168739.345:108): apparmor="DENIED"
operation="open" class="file" profile="rsyslogd"
name="/run/systemd/sessions/" pid=714 comm=72733A6D61696E20513A526567
requested_mask="r" denied_mask="r" fsuid=102 ouid=0

Note that it doesn't actually fail, the "EMERGENCY_MESSAGE" does appear
in the journal and also in /var/log/syslog. But it's some noise that
triggers our (and presumbly other admin's) log detectors.


rsyslog 8.2312.0-3ubuntu3
apparmor 4.0.0~alpha4-0ubuntu1


[1] 
https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.manifest
[2] 
https://cockpit-logs.us-east-1.linodeobjects.com/pull-6048-20240311-125838-b465e9b2-ubuntu-stable-other-cockpit-project-cockpit/log.html#118

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

** Affects: rsyslog (Ubuntu Noble)
 Importance: Undecided
 Status: New


** Tags: apparmor cockpit-test noble regression-release

** Also affects: rsyslog (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

Title:
  apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
  name="/run/systemd/sessions/"

Status in rsyslog package in Ubuntu:
  New
Status in rsyslog source package in Noble:
  New

Bug description:
  There is an AppArmor regression in current noble. In cockpit we
  recently started to test on noble (to prevent the "major regressions
  after release" fiasco from 23.10 again).

  For some weird reason, rsyslog is installed *by default* [1] in the
  cloud images. That is a rather pointless waste of CPU and disk space,
  as it's an unnecessary running daemon and duplicates all the written
  logs.

  But more specifically, we noticed [2] an AppArmor rejection.
  Reproducer is simple:

  logger -p user.emerg --tag check-journal EMERGENCY_MESSAGE

  this causes

  type=1400 audit(1710168739.345:108): apparmor="DENIED"
  operation="open" class="file" profile="rsyslogd"
  name="/run/systemd/sessions/" pid=714 comm=72733A6D61696E20513A526567
  requested_mask="r" denied_mask="r" fsuid=102 ouid=0

  Note that it doesn't actually fail, the "EMERGENCY_MESSAGE" does
  appear in the journal and also in /var/log/syslog. But it's some noise
  that triggers our (and presumbly other admin's) log detectors.

  
  rsyslog 8.2312.0-3ubuntu3
  apparmor 4.0.0~alpha4-0ubuntu1


  [1] 
https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.manifest
  [2] 
https://cockpit-logs.us-east-1.linodeobjects.com/pull-6048-20240311-125838-b465e9b2-ubuntu-stable-other-cockpit-project-cockpit/log.html#118

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


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

[Touch-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble

[Martin Malec]

Having the same issue as in #7 (id: ‘polkitd’: no such user,  chown:
invalid group: ‘root:polkitd’). Managed to apply workaround to move with
the test upgrade from this stuck place by creating polkitd system group
using `groupadd -r polkitd`.

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

Title:
  System installed from jammy point release iso cannot upgrade to noble

Status in gnome-shell package in Ubuntu:
  Invalid
Status in policykit-1 package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  We have different crashes being encountered. In our auto-upgrade-
  testing, we see gnome-shell crash, however, when testing locally, I
  didn't experience this. @hyask did experience the gnome-shell crash
  though.

  When running an upgrade from jammy to noble in a virsh vm, about
  halfway through the upgrade process my gui dies. I then ran the
  upgrade from a console, to which it revealed that just the gui dies -
  the upgrade process, for me, continues and then laterally fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-release-upgrader-core 1:24.04.7
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 
14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
   600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 
14:34:19.370597600 +:/var/crash/polkitd.0.crash
  Date: Mon Feb 19 14:53:39 2024
  InstallationDate: Installed on 2024-02-19 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44

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


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

[Touch-packages] [Bug 2047082] Re: upgrading openssh-server failed: rescue-ssh.target is a disabled or a static unit not running, not starting it.

[Martin Pitt]

Fun, this isn't even reliable. The first atttempt failed:

   https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-
logs/ubuntu-stable-20231219-223939.log

I retried the build now, no package or environment changes. Only daytime
and timing (race conditions). Perhaps some interaction with cloud-init?

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

Title:
  upgrading openssh-server always shows error: rescue-ssh.target is a
  disabled or a static unit not running, not starting it.

Status in openssh package in Ubuntu:
  New

Bug description:
  In our project we regularly build Ubuntu VM images for current 23.10
  (stable). In https://github.com/cockpit-project/bots/issues/5691 we
  ran into an upgrade failure of openssh-server. It starts with the
  current cloud image and then apt upgrades it, with
  "DEBIAN_FRONTEND=noninteractive". openssh was updated a few days ago
  indeed:

Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
Creating SSH2 ECDSA key; this may take some time ...
256 SHA256:UqrRSpQNM7SIixVivYP/WwZRjt7Sv89P31W/Gxaf+Z8 root@ubuntu (ECDSA)
Creating SSH2 ED25519 key; this may take some time ...
256 SHA256:hy9AEDydfnZeY9nf9P4Sb90kx39Oqr101A6tz5j4RQw root@ubuntu (ED25519)
rescue-ssh.target is a disabled or a static unit not running, not starting 
it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess 
returned error exit status 1

  I.e. of course that security update itself [1] didn't introduce the
  regression, but earlier VM builds just didn't have a pending openssh
  update -- looks like this has been a luring upgrade trap in the
  release already.

  As a first naïve reproducer I tried

apt update
DEBIAN_FRONTEND=noninteractive apt update openssh-server

  on our current VM (with the release version 1:9.3p1-1ubuntu3), and
  that worked fine. Same with installing all 9 available packages.
  rescue.target is loaded/inactive/static, as it should be. Updating
  without DEBIAN_FRONTEND does show me a conffile prompt about
  /etc/ssh/sshd_config, which is justified as we do modify the config:

# Allow root login with password
sed -i 's/^[# ]*PermitRootLogin .*/PermitRootLogin yes/' 
/etc/ssh/sshd_config
# Prevent SSH from hanging for a long time when no external network access
echo 'UseDNS no' >> /etc/ssh/sshd_config

  this also leads to a merge conflict. However, I suppose all of that is
  tangential to the rescue-ssh.target issue. In all my interactive
  upgrades, it seemed to handle that just fine:

Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
rescue-ssh.target is a disabled or a static unit not running, not starting 
it.

  So this seems to be related to the first-time installation of openssh-
  server -- it is part of the cloud image, but it does the host key
  generation during our image builds.

  So reproducing this is a bit tricky, but aside from that: Why does it
  even do this in the first place?

  # Automatically added by dh_installsystemd/13.11.6ubuntu1
  if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
  if [ -d /run/systemd/system ]; then
  systemctl --system daemon-reload >/dev/null || true
  if [ -n "$2" ]; then
  _dh_action=restart
  else
  _dh_action=start
  fi
  deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null 
|| true
  fi
  fi

  It feels like the postinst should *never* try to start rescue-
  ssh.target. That's an alternative boot mode, and should never run un
  multi-user.target, isn't it?

  [1] https://launchpad.net/ubuntu/+source/openssh/1:9.3p1-1ubuntu3.1

  DistroRelease: Ubuntu 23.10
  PackageVersion: openssh-server 1:9.3p1-1ubuntu3.1

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


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

[Touch-packages] [Bug 2047082] Re: upgrading openssh-server failed: rescue-ssh.target is a disabled or a static unit not running, not starting it.

[Martin Pitt]

Argh -- I missed the alternative truth in that rescue-ssh.target shell
code. So this message should pretty much *always* appear -- it's
nonsense to actually try and restart rescue-ssh.target in the postinst,
*always*.

But it is a red herring due to the || true. The upgrade failed on
something else but didn't print any error message. So there is no
remaining evidence what happens. So let's dedicate this bug report to
dropping that  deb-system-invoke for rescue-ssh.target.

** Summary changed:

- upgrading openssh-server failed: rescue-ssh.target is a disabled or a static 
unit not running, not starting it.
+ upgrading openssh-server always shows error: rescue-ssh.target is a disabled 
or a static unit not running, not starting it.

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

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

Title:
  upgrading openssh-server always shows error: rescue-ssh.target is a
  disabled or a static unit not running, not starting it.

Status in openssh package in Ubuntu:
  New

Bug description:
  In our project we regularly build Ubuntu VM images for current 23.10
  (stable). In https://github.com/cockpit-project/bots/issues/5691 we
  ran into an upgrade failure of openssh-server. It starts with the
  current cloud image and then apt upgrades it, with
  "DEBIAN_FRONTEND=noninteractive". openssh was updated a few days ago
  indeed:

Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
Creating SSH2 ECDSA key; this may take some time ...
256 SHA256:UqrRSpQNM7SIixVivYP/WwZRjt7Sv89P31W/Gxaf+Z8 root@ubuntu (ECDSA)
Creating SSH2 ED25519 key; this may take some time ...
256 SHA256:hy9AEDydfnZeY9nf9P4Sb90kx39Oqr101A6tz5j4RQw root@ubuntu (ED25519)
rescue-ssh.target is a disabled or a static unit not running, not starting 
it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess 
returned error exit status 1

  I.e. of course that security update itself [1] didn't introduce the
  regression, but earlier VM builds just didn't have a pending openssh
  update -- looks like this has been a luring upgrade trap in the
  release already.

  As a first naïve reproducer I tried

apt update
DEBIAN_FRONTEND=noninteractive apt update openssh-server

  on our current VM (with the release version 1:9.3p1-1ubuntu3), and
  that worked fine. Same with installing all 9 available packages.
  rescue.target is loaded/inactive/static, as it should be. Updating
  without DEBIAN_FRONTEND does show me a conffile prompt about
  /etc/ssh/sshd_config, which is justified as we do modify the config:

# Allow root login with password
sed -i 's/^[# ]*PermitRootLogin .*/PermitRootLogin yes/' 
/etc/ssh/sshd_config
# Prevent SSH from hanging for a long time when no external network access
echo 'UseDNS no' >> /etc/ssh/sshd_config

  this also leads to a merge conflict. However, I suppose all of that is
  tangential to the rescue-ssh.target issue. In all my interactive
  upgrades, it seemed to handle that just fine:

Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
rescue-ssh.target is a disabled or a static unit not running, not starting 
it.

  So this seems to be related to the first-time installation of openssh-
  server -- it is part of the cloud image, but it does the host key
  generation during our image builds.

  So reproducing this is a bit tricky, but aside from that: Why does it
  even do this in the first place?

  # Automatically added by dh_installsystemd/13.11.6ubuntu1
  if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
  if [ -d /run/systemd/system ]; then
  systemctl --system daemon-reload >/dev/null || true
  if [ -n "$2" ]; then
  _dh_action=restart
  else
  _dh_action=start
  fi
  deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null 
|| true
  fi
  fi

  It feels like the postinst should *never* try to start rescue-
  ssh.target. That's an alternative boot mode, and should never run un
  multi-user.target, isn't it?

  [1] https://launchpad.net/ubuntu/+source/openssh/1:9.3p1-1ubuntu3.1

  DistroRelease: Ubuntu 23.10
  PackageVersion: openssh-server 1:9.3p1-1ubuntu3.1

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


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

[Touch-packages] [Bug 2047082] [NEW] upgrading openssh-server always shows error: rescue-ssh.target is a disabled or a static unit not running, not starting it.

[Martin Pitt]

Public bug reported:

In our project we regularly build Ubuntu VM images for current 23.10
(stable). In https://github.com/cockpit-project/bots/issues/5691 we ran
into an upgrade failure of openssh-server. It starts with the current
cloud image and then apt upgrades it, with
"DEBIAN_FRONTEND=noninteractive". openssh was updated a few days ago
indeed:

  Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
  Creating SSH2 ECDSA key; this may take some time ...
  256 SHA256:UqrRSpQNM7SIixVivYP/WwZRjt7Sv89P31W/Gxaf+Z8 root@ubuntu (ECDSA)
  Creating SSH2 ED25519 key; this may take some time ...
  256 SHA256:hy9AEDydfnZeY9nf9P4Sb90kx39Oqr101A6tz5j4RQw root@ubuntu (ED25519)
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1

I.e. of course that security update itself [1] didn't introduce the
regression, but earlier VM builds just didn't have a pending openssh
update -- looks like this has been a luring upgrade trap in the release
already.

As a first naïve reproducer I tried

  apt update
  DEBIAN_FRONTEND=noninteractive apt update openssh-server

on our current VM (with the release version 1:9.3p1-1ubuntu3), and that
worked fine. Same with installing all 9 available packages.
rescue.target is loaded/inactive/static, as it should be. Updating
without DEBIAN_FRONTEND does show me a conffile prompt about
/etc/ssh/sshd_config, which is justified as we do modify the config:

  # Allow root login with password
  sed -i 's/^[# ]*PermitRootLogin .*/PermitRootLogin yes/' /etc/ssh/sshd_config
  # Prevent SSH from hanging for a long time when no external network access
  echo 'UseDNS no' >> /etc/ssh/sshd_config

this also leads to a merge conflict. However, I suppose all of that is
tangential to the rescue-ssh.target issue. In all my interactive
upgrades, it seemed to handle that just fine:

  Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.

So this seems to be related to the first-time installation of openssh-
server -- it is part of the cloud image, but it does the host key
generation during our image builds.

So reproducing this is a bit tricky, but aside from that: Why does it
even do this in the first place?

# Automatically added by dh_installsystemd/13.11.6ubuntu1
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null 
|| true
fi
fi

It feels like the postinst should *never* try to start rescue-
ssh.target. That's an alternative boot mode, and should never run un
multi-user.target, isn't it?

[1] https://launchpad.net/ubuntu/+source/openssh/1:9.3p1-1ubuntu3.1

DistroRelease: Ubuntu 23.10
PackageVersion: openssh-server 1:9.3p1-1ubuntu3.1

** Affects: openssh (Ubuntu)
 Importance: Low
 Status: New


** Tags: mantic

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

Title:
  upgrading openssh-server always shows error: rescue-ssh.target is a
  disabled or a static unit not running, not starting it.

Status in openssh package in Ubuntu:
  New

Bug description:
  In our project we regularly build Ubuntu VM images for current 23.10
  (stable). In https://github.com/cockpit-project/bots/issues/5691 we
  ran into an upgrade failure of openssh-server. It starts with the
  current cloud image and then apt upgrades it, with
  "DEBIAN_FRONTEND=noninteractive". openssh was updated a few days ago
  indeed:

Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
Creating SSH2 ECDSA key; this may take some time ...
256 SHA256:UqrRSpQNM7SIixVivYP/WwZRjt7Sv89P31W/Gxaf+Z8 root@ubuntu (ECDSA)
Creating SSH2 ED25519 key; this may take some time ...
256 SHA256:hy9AEDydfnZeY9nf9P4Sb90kx39Oqr101A6tz5j4RQw root@ubuntu (ED25519)
rescue-ssh.target is a disabled or a static unit not running, not starting 
it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess 
returned error exit status 1

  I.e. of course that security update itself [1] didn't introduce the
  regression, but earlier VM builds just didn't have a pending openssh
  update -- looks like this has b

[Touch-packages] [Bug 2037703] Re: dpkg-reconfigure openssh-server doesn't ask questions again

[Martin Pitt]

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

Title:
  dpkg-reconfigure openssh-server doesn't ask questions again

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server does provide a couple of configuration options:

  [~]$ sudo debconf-get-selections |grep openssh-server
  openssh-serveropenssh-server/listenstream-may-failerror   
  openssh-serveropenssh-server/password-authentication  boolean true
  openssh-serveropenssh-server/permit-root-loginboolean true

  
  I want to change those options now interactively but nothing I tried worked 
and showed a dialog:

  [~]$ sudo dpkg-reconfigure -p low openssh-server  
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.

  [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.


  But the documentation (https://manpages.debian.org/testing/debconf-
  doc/debconf.7.en.html#Reconfiguring_packages) does state that those
  commands should ask those questions again.

  
  p.s. also tried with a lxc debian-sid container and had the same problem 
there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.3p1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 10:35:33 2023
  InstallationDate: Installed on 2023-05-10 (142 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago)

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


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

[Touch-packages] [Bug 2037703] Re: dpkg-reconfigure openssh-server doesn't ask questions again

[Martin Pitt]

We just ran into this in https://github.com/cockpit-
project/bots/issues/5691 when trying to refresh our Ubuntu 23.10 mantic
VM image. It starts with the current cloud image and then apt upgrades
it, with "DEBIAN_FRONTEND=noninteractive". openssh was updated a few
days ago indeed:

  Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
  Creating SSH2 ECDSA key; this may take some time ...
  256 SHA256:UqrRSpQNM7SIixVivYP/WwZRjt7Sv89P31W/Gxaf+Z8 root@ubuntu (ECDSA)
  Creating SSH2 ED25519 key; this may take some time ...
  256 SHA256:hy9AEDydfnZeY9nf9P4Sb90kx39Oqr101A6tz5j4RQw root@ubuntu (ED25519)
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1


I.e. of course that security update itself didn't introduce the regression, but 
earlier VM builds just didn't have a pending openssh update -- looks like this 
has been a luring upgrade trap in the release already.


However, as a first naïve reproducer I tried

  apt update
  DEBIAN_FRONTEND=noninteractive apt update openssh-server

on our current VM (with the release version 1:9.3p1-1ubuntu3), and that
worked fine. Same with installing all 9 available packages.
rescue.target is loaded/inactive/static, as it should be. Updating
without DEBIAN_FRONTEND does show me a conffile prompt about
/etc/ssh/sshd_config, which is justified as we do modify the config:

  # Allow root login with password
  sed -i 's/^[# ]*PermitRootLogin .*/PermitRootLogin yes/' /etc/ssh/sshd_config
  # Prevent SSH from hanging for a long time when no external network access
  echo 'UseDNS no' >> /etc/ssh/sshd_config

this also leads to a merge conflict. However, I suppose all of that is
tangential to the rescue-ssh.target  issue. In all my interactive
upgrades, it seemed to handle that just fine:

  Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.

So this seems to be related to the first-time installation of openssh-
server -- it is part of the cloud image, but it does the host key
generation during our image builds.


So reproducing this is a bit tricky, but aside from that: Why does it even do 
this in the first place?

# Automatically added by dh_installsystemd/13.11.6ubuntu1
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null 
|| true
fi
fi

It feels like the postinst should *never* try to start rescue-
ssh.target. That's an alternative boot mode, and should never run un
multi-user.target, isn't it?

[1] https://launchpad.net/ubuntu/+source/openssh/1:9.3p1-1ubuntu3.1

** Bug watch added: github.com/cockpit-project/bots/issues #5691
   https://github.com/cockpit-project/bots/issues/5691

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

Title:
  dpkg-reconfigure openssh-server doesn't ask questions again

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server does provide a couple of configuration options:

  [~]$ sudo debconf-get-selections |grep openssh-server
  openssh-serveropenssh-server/listenstream-may-failerror   
  openssh-serveropenssh-server/password-authentication  boolean true
  openssh-serveropenssh-server/permit-root-loginboolean true

  
  I want to change those options now interactively but nothing I tried worked 
and showed a dialog:

  [~]$ sudo dpkg-reconfigure -p low openssh-server  
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.

  [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.


  But the documentation (https://manpages.debian.org/testing/debconf-
  doc/debconf.7.en.html#Reconfiguring_packages) does state that those
  commands should ask those questions again.

  
  p.s. also tried with a lxc debian-sid container and had the same problem 
there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.3p1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Lin

[Touch-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses

[Martin Pitt]

Excellent, thanks Danilo for the super fast fix! ⭐

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

Title:
  Updating wireguard-peer.allowed-ips gets wrong default netmask for
  IPv6 addresses

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  In https://cockpit-project.org/ we have an integration test for
  NM+wireguard integration. That test starts with an IPv4-only
  connection:

  # cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
  network:
    version: 2
    tunnels:
  wg0:
    renderer: NetworkManager
    addresses:
    - "10.0.0.2/24"
    mode: "wireguard"
    port: 51820
    keys:
  private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
    peers:
    - keys:
    public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
  allowed-ips:
  - "10.0.0.1/32"
    networkmanager:
  uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
  name: "con-wg0"
  passthrough:
    ipv6.addr-gen-mode: "default"
    ipv6.method: "disabled"
    ipv6.ip6-privacy: "-1"
    proxy._: ""

  which gets rendered as

  # cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
  [connection]
  id=con-wg0
  type=wireguard
  uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
  interface-name=wg0

  [wireguard]
  private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
  listen-port=51820

  [wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
  allowed-ips=10.0.0.1/32;

  [ipv4]
  method=manual
  address1=10.0.0.2/24

  [ipv6]
  #Netplan: passthrough override
  method=disabled
  #Netplan: passthrough setting
  addr-gen-mode=default

  [proxy]

  Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
  "2001::1"]. Notably the addresses do *not* have a netmask, neither in
  the original config nor that update. Unfortunately that update cannot
  be done on the CLI:

  # nmcli con modify con-wg0 
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips" 
"2001::1"
  Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not 
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].

  So it has to happen via D-Bus:

  
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
  wg0","t":"s"},"interface-
  
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
  slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
  port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
  key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
  ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
  
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
  
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
  
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
  data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
  data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
  auto-dns":{"v":false,"t":"b"},"ignore-auto-
  routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]

  But this generates a wrong "/32" default netmask in the netplan config
  for the IPv6 address:

  allowed-ips:
  - "10.0.0.1/32"
  - "2001::1/32"

  On Fedora, with NM's default .nmconnection files, such a netmask is
  not added on this call. The netplan backend should do that (not
  second-guessing NM) or at least default to /128 for an IPv6 address.

  Doing this D-Bus call with `busctl` is a nuisance. If you need a
  reproducer at this level, I can spend an hour or so trying to stitch
  it together, but I hope your unit tests make this easier somehow.

  This was fine until 22.10, but with NM's new "netplan by default"
  backend this regressed.

  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2

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


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

[Touch-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses

[Martin Pitt]

** Description changed:

  In https://cockpit-project.org/ we have an integration test for
  NM+wireguard integration. That test starts with an IPv4-only connection:
  
  # cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
  network:
-   version: 2
-   tunnels:
- wg0:
-   renderer: NetworkManager
-   addresses:
-   - "10.0.0.2/24"
-   mode: "wireguard"
-   port: 51820
-   keys:
- private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
-   peers:
-   - keys:
-   public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
- allowed-ips:
- - "10.0.0.1/32"
-   networkmanager:
- uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
- name: "con-wg0"
- passthrough:
-   ipv6.addr-gen-mode: "default"
-   ipv6.method: "disabled"
-   ipv6.ip6-privacy: "-1"
-   proxy._: ""
- 
+   version: 2
+   tunnels:
+ wg0:
+   renderer: NetworkManager
+   addresses:
+   - "10.0.0.2/24"
+   mode: "wireguard"
+   port: 51820
+   keys:
+ private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
+   peers:
+   - keys:
+   public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
+ allowed-ips:
+ - "10.0.0.1/32"
+   networkmanager:
+ uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
+ name: "con-wg0"
+ passthrough:
+   ipv6.addr-gen-mode: "default"
+   ipv6.method: "disabled"
+   ipv6.ip6-privacy: "-1"
+   proxy._: ""
  
  which gets rendered as
  
  # cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
  [connection]
  id=con-wg0
  type=wireguard
  uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
  interface-name=wg0
  
  [wireguard]
  private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
  listen-port=51820
  
  [wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
  allowed-ips=10.0.0.1/32;
  
  [ipv4]
  method=manual
  address1=10.0.0.2/24
  
  [ipv6]
  #Netplan: passthrough override
  method=disabled
  #Netplan: passthrough setting
  addr-gen-mode=default
  
  [proxy]
  
- 
- Now the UI modifies the "allowed-ips" setting to ["10.0.0.1", "2001::1"]. 
Notably the addresses do *not* have a netmask, neither in the original config 
nor that update. Unfortunately that update cannot be done on the CLI:
+ Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
+ "2001::1"]. Notably the addresses do *not* have a netmask, neither in
+ the original config nor that update. Unfortunately that update cannot be
+ done on the CLI:
  
  # nmcli con modify con-wg0 
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips" 
"2001::1"
  Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not 
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
- 
  
  So it has to happen via D-Bus:
  
  
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
  wg0","t":"s"},"interface-
  
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
  slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
  port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
  key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
  ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
  
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
  
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
  
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
  data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
  data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
  auto-dns":{"v":false,"t":"b"},"ignore-auto-
  routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
  
+ But this generates a wrong "/32" default netmask in the netplan config
+ for the IPv6 address:
  
- But this generates a wrong "/32" default netmask in the netplan config for 
the IPv6 address:
- 
- allowed-ips:
- - "10.0.0.1/32"
- - "2001::1/32"
+ allowed-ips:
+ - "10.0.0.1/32"
+ - "2001::1/32"
  
  On Fedora, with NM's default .nmconnection files, such a netmask is not
  added on this call. The netplan backend should do that (not second-
  guessing NM) or at least default to /128 for an IPv6 address.
  
  Doing this D-Bus call with `busctl` is a nuisance. If you need a
  reproducer at this level, I can spend an hour o

[Touch-packages] [Bug 2046158] [NEW] Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses

[Martin Pitt]

Public bug reported:

In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:

# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
  version: 2
  tunnels:
wg0:
  renderer: NetworkManager
  addresses:
  - "10.0.0.2/24"
  mode: "wireguard"
  port: 51820
  keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
  peers:
  - keys:
  public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
  networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
  ipv6.addr-gen-mode: "default"
  ipv6.method: "disabled"
  ipv6.ip6-privacy: "-1"
  proxy._: ""


which gets rendered as

# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0

[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820

[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;

[ipv4]
method=manual
address1=10.0.0.2/24

[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default

[proxy]


Now the UI modifies the "allowed-ips" setting to ["10.0.0.1", "2001::1"]. 
Notably the addresses do *not* have a netmask, neither in the original config 
nor that update. Unfortunately that update cannot be done on the CLI:

# nmcli con modify con-wg0 
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips" 
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not 
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].


So it has to happen via D-Bus:

"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]


But this generates a wrong "/32" default netmask in the netplan config for the 
IPv6 address:

allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"

On Fedora, with NM's default .nmconnection files, such a netmask is not
added on this call. The netplan backend should do that (not second-
guessing NM) or at least default to /128 for an IPv6 address.

Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch it
together, but I hope your unit tests make this easier somehow.

This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.

DistroRelease: Ubuntu 23.04
Package: network-manager 1.44.2-1ubuntu1.2

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


** Tags: mantic regression-release

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

Title:
  Updating wireguard-peer.allowed-ips gets wrong default netmask for
  IPv6 addresses

Status in network-manager package in Ubuntu:
  New

Bug description:
  In https://cockpit-project.org/ we have an integration test for
  NM+wireguard integration. That test starts with an IPv4-only
  connection:

  # cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
  network:
version: 2
tunnels:
  wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
  private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/

[Touch-packages] [Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Martin Pitt]

I also tried

  aa-disable usr.bin.crun

but that doesn't work either. I guess it's not really crun, but
profile="containers-default-0.50.1", but that is created dynamically --
it's not anywhere in /etc/apparmor.d/. I grepped the whole file system
for that:

  grep: /usr/lib/podman/rootlessport: binary file matches
  grep: /usr/bin/podman: binary file matches
  grep: /usr/bin/buildah: binary file matches

Running an individual container with --security-opt=label=disable also
doesn't work, same DENIED and failure.

"man containers.conf" points at apparmor_profile="container‐default",
but not how to disable it. I naively tried apparmor_profile="none" but

  Error: AppArmor profile "none" specified but not loaded

But curiously an empty string works. 🎉 So, my official workaround:

  mkdir -p /etc/containers/containers.conf.d
  printf '[CONTAINERS]\napparmor_profile=""\n' > 
/etc/containers/containers.conf.d/disable-apparmor.conf

** No longer affects: apparmor (Ubuntu)

** No longer affects: apparmor (Ubuntu Mantic)

** No longer affects: apparmor (Ubuntu Noble)

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

Title:
  AppArmor denies crun sending signals to containers (stop, kill)

Status in libpod package in Ubuntu:
  Confirmed
Status in libpod source package in Mantic:
  New
Status in libpod source package in Noble:
  Confirmed

Bug description:
  Mantic's system podman containers are completely broken due to bug
  2040082. However, after fixing that (rebuilding with the patch, or a
  *shht don't try this at home* hack [1]), the AppArmor policy still
  causes bugs:

    podman run -it --rm docker.io/busybox

  Then

    podman stop -l

  fails with

     2023-10-25T11:06:33.873998Z: send signal to pidfd: Permission
  denied

  and journal shows

    audit: type=1400 audit(1698231993.870:92): apparmor="DENIED"
  operation="signal" class="signal" profile="containers-default-0.50.1"
  pid=4713 comm="3" requested_mask="receive" denied_mask="receive"
  signal=term peer="/usr/bin/crun"

  This leaves the container in a broken state:

    # podman ps -a
    CONTAINER ID  IMAGE COMMAND CREATED 
STATUS  PORTS   NAMES
    61749260f9c4  docker.io/library/busybox:latest  sh  40 seconds ago  
Exited (-1) 29 seconds ago  confident_bouman

    # podman rm --all
    2023-10-25T11:07:21.428701Z: send signal to pidfd: Permission denied
    Error: cleaning up container 
61749260f9c4c96a51dc27fdd9cb8a86d80e4f2aa14eb7ed5b271791ff8008ae: removing 
container 61749260f9c4c96a51dc27fdd9cb8a86d80e4f2aa14eb7ed5b271791ff8008ae from 
runtime: `/usr/bin/crun delete --force 
61749260f9c4c96a51dc27fdd9cb8a86d80e4f2aa14eb7ed5b271791ff8008ae` failed: exit 
status 1

    audit: type=1400 audit(1698232041.422:93): apparmor="DENIED"
  operation="signal" class="signal" profile="containers-default-0.50.1"
  pid=4839 comm="3" requested_mask="receive" denied_mask="receive"
  signal=kill peer="/usr/bin/crun"

  [1] sed -i 's/~alpha2/000/' /usr/sbin/apparmor_parser

  Ubuntu 23.10

  ii  apparmor4.0.0~alpha2-0ubuntu5 amd64
user-space parser utility for AppArmor
  ii  golang-github-containers-common 0.50.1+ds1-4  all  Common 
files for github.com/containers repositories
  ii  podman  4.3.1+ds1-8   amd64engine 
to run OCI-based containers in Pods

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


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

[Touch-packages] [Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Martin Pitt]

I tried a more targeted workaround, with

  aa-complain /etc/apparmor.d/usr.bin.crun

or alternatively (without apparmor-utils, which isn't on the default
cloud image):

  sed -i '/flags=/ s/unconfined/complain/' /etc/apparmor.d/usr.bin.crun

but for some reason that breaks podman entirely:

# podman run -it --rm docker.io/busybox
Failed to re-execute libcrun via memory file descriptor
   ERRO[] Removing 
container 7c3c938f8e356a9834de6a114ad8b8353ffac7508c8aac131d588e1358ba2f30 from 
runtime after creation failed 
Error: OCI runtime error: crun: Failed to re-execute libcrun via memory file 
descriptor


I just noticed that neither podman nor crun ship their own AppArmor profiles, 
/etc/apparmor.d/usr.bin.crun is shipped by apparmor. So adding a package task, 
but leaving libpod as "affected", so that it is easier to find.

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
   Status: 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/2040483

Title:
  AppArmor denies crun sending signals to containers (stop, kill)

Status in apparmor package in Ubuntu:
  New
Status in libpod package in Ubuntu:
  Confirmed
Status in apparmor source package in Mantic:
  New
Status in libpod source package in Mantic:
  New
Status in apparmor source package in Noble:
  New
Status in libpod source package in Noble:
  Confirmed

Bug description:
  Mantic's system podman containers are completely broken due to bug
  2040082. However, after fixing that (rebuilding with the patch, or a
  *shht don't try this at home* hack [1]), the AppArmor policy still
  causes bugs:

    podman run -it --rm docker.io/busybox

  Then

    podman stop -l

  fails with

     2023-10-25T11:06:33.873998Z: send signal to pidfd: Permission
  denied

  and journal shows

    audit: type=1400 audit(1698231993.870:92): apparmor="DENIED"
  operation="signal" class="signal" profile="containers-default-0.50.1"
  pid=4713 comm="3" requested_mask="receive" denied_mask="receive"
  signal=term peer="/usr/bin/crun"

  This leaves the container in a broken state:

    # podman ps -a
    CONTAINER ID  IMAGE COMMAND CREATED 
STATUS  PORTS   NAMES
    61749260f9c4  docker.io/library/busybox:latest  sh  40 seconds ago  
Exited (-1) 29 seconds ago  confident_bouman

    # podman rm --all
    2023-10-25T11:07:21.428701Z: send signal to pidfd: Permission denied
    Error: cleaning up container 
61749260f9c4c96a51dc27fdd9cb8a86d80e4f2aa14eb7ed5b271791ff8008ae: removing 
container 61749260f9c4c96a51dc27fdd9cb8a86d80e4f2aa14eb7ed5b271791ff8008ae from 
runtime: `/usr/bin/crun delete --force 
61749260f9c4c96a51dc27fdd9cb8a86d80e4f2aa14eb7ed5b271791ff8008ae` failed: exit 
status 1

    audit: type=1400 audit(1698232041.422:93): apparmor="DENIED"
  operation="signal" class="signal" profile="containers-default-0.50.1"
  pid=4839 comm="3" requested_mask="receive" denied_mask="receive"
  signal=kill peer="/usr/bin/crun"

  [1] sed -i 's/~alpha2/000/' /usr/sbin/apparmor_parser

  Ubuntu 23.10

  ii  apparmor4.0.0~alpha2-0ubuntu5 amd64
user-space parser utility for AppArmor
  ii  golang-github-containers-common 0.50.1+ds1-4  all  Common 
files for github.com/containers repositories
  ii  podman  4.3.1+ds1-8   amd64engine 
to run OCI-based containers in Pods

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


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

[Touch-packages] [Bug 2045907] [NEW] GtkFileChooserDialog hangs on large folder with 300000 files

[Martin M]

Public bug reported:

when I paste filename into the location bar (Ctrl+L) the file chooser
hangs.

The file happens to be in a folder with 30 other files and 
GtkFileChooserDialog
tries to offer a filename typing suggestion dropdown which is slow and 
eventually crashes.

When I then kill chrome or firefox then wayland session gets logouted.

Ubuntu version is 23.10

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
   GtkFileChooserDialog hangs on large folder with 30 files

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  when I paste filename into the location bar (Ctrl+L) the file chooser
  hangs.

  The file happens to be in a folder with 30 other files and 
GtkFileChooserDialog
  tries to offer a filename typing suggestion dropdown which is slow and 
eventually crashes.

  When I then kill chrome or firefox then wayland session gets logouted.

  Ubuntu version is 23.10

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


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

[Touch-packages] [Bug 2045494] [NEW] did not upgrade to 23.10

[Lars Martin Hambro]

Public bug reported:

root@localhost:/home/larsmartin# sudo apt update && sudo apt upgrade
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
  exo-utils libopenexr25 libpostproc55 libavcodec58 libavutil56 libswscale5
  xrdp libexo-2-0 libswresample3 libavformat58 libexo-common libavfilter7
Learn more about Ubuntu Pro at https://ubuntu.com/pro
The following packages have been kept back:
  libayatana-appindicator3-1
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@localhost:/home/larsmartin# sudo do-release-upgrade 
Checking for a new Ubuntu release
Please install all available updates for your release before upgra

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apt 2.4.11
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
Uname: Linux 5.15.0-89-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sun Dec  3 09:21:14 2023
InstallationDate: Installed on 2020-07-05 (1245 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apt
UpgradeStatus: Upgraded to jammy on 2022-03-24 (618 days ago)

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


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  did not upgrade to 23.10

Status in apt package in Ubuntu:
  New

Bug description:
  root@localhost:/home/larsmartin# sudo apt update && sudo apt upgrade
  Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  1 package can be upgraded. Run 'apt list --upgradable' to see it.
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
exo-utils libopenexr25 libpostproc55 libavcodec58 libavutil56 libswscale5
xrdp libexo-2-0 libswresample3 libavformat58 libexo-common libavfilter7
  Learn more about Ubuntu Pro at https://ubuntu.com/pro
  The following packages have been kept back:
libayatana-appindicator3-1
  0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
  root@localhost:/home/larsmartin# sudo do-release-upgrade 
  Checking for a new Ubuntu release
  Please install all available updates for your release before upgra

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.11
  ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
  Uname: Linux 5.15.0-89-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Dec  3 09:21:14 2023
  InstallationDate: Installed on 2020-07-05 (1245 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-03-24 (618 days ago)

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


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

[Touch-packages] [Bug 2044602] Re: did not works to upgrade to 23.10

[Lars Martin Hambro]

works to error when manage this file:
 libgpod-common

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

Title:
  did not works to upgrade to 23.10

Status in apt package in Ubuntu:
  New

Bug description:
  I have issue after upgrade its did not works

  apt --fix-broken install

   vil kanskje kjøre «apt --fix-broken install» for å rette på dette.
  Følgende pakker har uinnfridde avhengighetsforhold:
   libgpod-common : Avhenger av: libsgutils2-1.46-2 (>= 1.27) men er ikke 
installert
  E: Uinnfridde avhengighetsforhold. Prøv «apt --fix-broken install» uten 
pakker (eller angi en løsning).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.3
  ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat Nov 25 12:58:59 2023
  InstallationDate: Installed on 2019-05-07 (1663 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: Upgraded to mantic on 2023-11-25 (0 days ago)

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


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

[Touch-packages] [Bug 2044602] Re: did not works to upgrade to 23.10

[Lars Martin Hambro]

look like sudo dpkg --configure -a works to get it install? None
information about it?

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

Title:
  did not works to upgrade to 23.10

Status in apt package in Ubuntu:
  New

Bug description:
  I have issue after upgrade its did not works

  apt --fix-broken install

   vil kanskje kjøre «apt --fix-broken install» for å rette på dette.
  Følgende pakker har uinnfridde avhengighetsforhold:
   libgpod-common : Avhenger av: libsgutils2-1.46-2 (>= 1.27) men er ikke 
installert
  E: Uinnfridde avhengighetsforhold. Prøv «apt --fix-broken install» uten 
pakker (eller angi en løsning).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.3
  ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat Nov 25 12:58:59 2023
  InstallationDate: Installed on 2019-05-07 (1663 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: Upgraded to mantic on 2023-11-25 (0 days ago)

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


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

[Touch-packages] [Bug 2044602] Re: did not works to upgrade to 23.10

[Lars Martin Hambro]

Also issue when select LightDM or gmd3 computer get black screen most reboot.
Nvidia grapic card GTX 1080 TI.

when i remove ubuntu-desktop  libgpod-common need  libsgutils2-1.46-2 (>= 1.27)
use «apt --fix-broken install

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

Title:
  did not works to upgrade to 23.10

Status in apt package in Ubuntu:
  New

Bug description:
  I have issue after upgrade its did not works

  apt --fix-broken install

   vil kanskje kjøre «apt --fix-broken install» for å rette på dette.
  Følgende pakker har uinnfridde avhengighetsforhold:
   libgpod-common : Avhenger av: libsgutils2-1.46-2 (>= 1.27) men er ikke 
installert
  E: Uinnfridde avhengighetsforhold. Prøv «apt --fix-broken install» uten 
pakker (eller angi en løsning).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.3
  ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat Nov 25 12:58:59 2023
  InstallationDate: Installed on 2019-05-07 (1663 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: Upgraded to mantic on 2023-11-25 (0 days ago)

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


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

[Touch-packages] [Bug 2044602] Re: did not works to upgrade to 23.10

[Lars Martin Hambro]

** Attachment added: "issue.png"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2044602/+attachment/5723408/+files/issue.png

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

Title:
  did not works to upgrade to 23.10

Status in apt package in Ubuntu:
  New

Bug description:
  I have issue after upgrade its did not works

  apt --fix-broken install

   vil kanskje kjøre «apt --fix-broken install» for å rette på dette.
  Følgende pakker har uinnfridde avhengighetsforhold:
   libgpod-common : Avhenger av: libsgutils2-1.46-2 (>= 1.27) men er ikke 
installert
  E: Uinnfridde avhengighetsforhold. Prøv «apt --fix-broken install» uten 
pakker (eller angi en løsning).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.3
  ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat Nov 25 12:58:59 2023
  InstallationDate: Installed on 2019-05-07 (1663 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: Upgraded to mantic on 2023-11-25 (0 days ago)

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


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

[Touch-packages] [Bug 2044602] [NEW] did not works to upgrade to 23.10

[Lars Martin Hambro]

Public bug reported:

I have issue after upgrade its did not works

apt --fix-broken install

 vil kanskje kjøre «apt --fix-broken install» for å rette på dette.
Følgende pakker har uinnfridde avhengighetsforhold:
 libgpod-common : Avhenger av: libsgutils2-1.46-2 (>= 1.27) men er ikke 
installert
E: Uinnfridde avhengighetsforhold. Prøv «apt --fix-broken install» uten pakker 
(eller angi en løsning).

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: apt 2.7.3
ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Sat Nov 25 12:58:59 2023
InstallationDate: Installed on 2019-05-07 (1663 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apt
UpgradeStatus: Upgraded to mantic on 2023-11-25 (0 days ago)

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


** Tags: amd64 apport-bug mantic

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

Title:
  did not works to upgrade to 23.10

Status in apt package in Ubuntu:
  New

Bug description:
  I have issue after upgrade its did not works

  apt --fix-broken install

   vil kanskje kjøre «apt --fix-broken install» for å rette på dette.
  Følgende pakker har uinnfridde avhengighetsforhold:
   libgpod-common : Avhenger av: libsgutils2-1.46-2 (>= 1.27) men er ikke 
installert
  E: Uinnfridde avhengighetsforhold. Prøv «apt --fix-broken install» uten 
pakker (eller angi en løsning).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.3
  ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat Nov 25 12:58:59 2023
  InstallationDate: Installed on 2019-05-07 (1663 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: Upgraded to mantic on 2023-11-25 (0 days ago)

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


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

[Touch-packages] [Bug 1989073] Re: AppArmor DENIES reading of /sys/devices/system/cpu/possible

[Martin Pitt]

Similar issue: https://gitlab.com/libvirt/libvirt/-/issues/548 . These
two may want a common fix with "allow qemu to read sysfs"?

** Bug watch added: gitlab.com/libvirt/libvirt/-/issues #548
   https://gitlab.com/libvirt/libvirt/-/issues/548

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

Title:
  AppArmor DENIES reading of /sys/devices/system/cpu/possible

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Kinetic:
  Won't Fix

Bug description:
  libvirt 8.6.0-0ubuntu1
  apparmor 3.0.7-1ubuntu1

  Creating a VM with virt-install produces this AppAmore denial:

  AVC apparmor="DENIED" operation="open"
  profile="libvirt-974c9859-e682-4f5d-b0cb-dcf3d60185fc"
  name="/sys/devices/system/cpu/possible" pid=2522 comm="qemu-
  system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0

  Creation of the VM is successful.  This is with nested virtualization.

  This did not happen with libvirt 8.0.0-1ubuntu8 and apparmor
  3.0.7-1ubuntu1.

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


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

[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault

[Martin Vysny]

The process is Intellij IDEA, running on Java 17 in Xwayland.

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

Title:
  amdgpu: [gfxhub0] no-retry page fault

Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Whenever I use Intellij IDEA, after a couple of minutes the screen
  locks up and pretty much renders the machine unusable. I can still ssh
  to it, but the UI is pretty much gone and doesn't respond to
  Ctrl+Alt+F* keys.

  The setup: the machine is connected to an external monitor via USB-C.
  Running kernel 6.5 on Ubuntu 23.10.

  There's the following in kern.log:

  ```
  2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [  422.206433] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663)
  2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [  422.206450] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xb15852923000 
from IH client 0x1b (UTCL2)
  2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [  422.206460] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431
  2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [  422.206466] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
  2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [  422.206471] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x1
  2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [  422.206476] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
  2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [  422.206481] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [  422.206485] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
  2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [  422.206490] 
amdgpu :06:00.0: amdgpu:  RW: 0x0
  2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [  422.206497] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663)
  2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [  422.206506] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xb07248096000 
from IH client 0x1b (UTCL2)
  2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [  422.206514] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431
  2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [  422.206519] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
  2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [  422.206524] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x1
  2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [  422.206528] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
  2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [  422.206533] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [  422.206538] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
  2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [  422.206542] 
amdgpu :06:00.0: amdgpu:  RW: 0x0
  2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [  422.206549] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663)
  2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [  422.206556] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xaf8c3d808000 
from IH client 0x1b (UTCL2)
  2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [  422.206564] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431
  2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [  422.206569] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
  2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [  422.206574] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x1
  2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [  422.206578] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
  2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [  422.206583] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [  422.206588] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
  2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [  422.206592] 
amdgpu :06:00.0: amdgpu:  RW: 0x0
  2023-09-28T13:58:23.077726+03:00 mavi-ThinkPad-T14s kernel: [  422.

[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault

[Martin Vysny]

Unfortunately the problem is still reproducible even with the newest
mesa, even though it looks like it's much less frequent. Yesterday
evening I got another crash, with mesa 23.2.1-1ubuntu2:

```
2023-10-04T22:33:15.415854+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119146] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015)
2023-10-04T22:33:15.415871+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119168] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xe5ea2326e000 
from IH client 0x1b (UTCL2)
2023-10-04T22:33:15.415873+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119180] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430
2023-10-04T22:33:15.415874+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119187] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
2023-10-04T22:33:15.415875+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119194] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x0
2023-10-04T22:33:15.415876+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119200] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119206] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119212] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
2023-10-04T22:33:15.415879+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119218] 
amdgpu :06:00.0: amdgpu:  RW: 0x0
2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119750] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015)
2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119768] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xe5ea2326f000 
from IH client 0x1b (UTCL2)
2023-10-04T22:33:15.415883+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119780] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430
2023-10-04T22:33:15.415884+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119787] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119793] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x0
2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119800] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
2023-10-04T22:33:15.415886+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119806] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
2023-10-04T22:33:15.415887+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119812] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
2023-10-04T22:33:15.415888+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119818] 
amdgpu :06:00.0: amdgpu:  RW: 0x0
2023-10-04T22:33:25.115577+03:00 mavi-ThinkPad-T14s kernel: [ 1085.820288] 
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_low timeout, signaled 
seq=75561, emitted seq=75563
2023-10-04T22:33:25.115600+03:00 mavi-ThinkPad-T14s kernel: [ 1085.821169] 
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
Xwayland pid 4940 thread Xwayland:cs0 pid 5015
2023-10-04T22:33:25.115602+03:00 mavi-ThinkPad-T14s kernel: [ 1085.822031] 
amdgpu :06:00.0: amdgpu: GPU reset begin!
2023-10-04T22:33:25.347547+03:00 mavi-ThinkPad-T14s kernel: [ 1086.052065] 
[drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117)
2023-10-04T22:33:25.375820+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078048] 
amdgpu :06:00.0: amdgpu: MODE2 reset
2023-10-04T22:33:25.375835+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078296] 
amdgpu :06:00.0: amdgpu: GPU reset succeeded, trying to resume
2023-10-04T22:33:25.375837+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078498] 
[drm] PCIE GART of 1024M enabled.
2023-10-04T22:33:25.375838+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078503] 
[drm] PTB located at 0x00F43FC0
2023-10-04T22:33:25.375839+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078625] 
[drm] PSP is resuming...
2023-10-04T22:33:26.075542+03:00 mavi-ThinkPad-T14s kernel: [ 1086.780162] 
[drm] reserve 0x40 from 0xf43f80 for PSP TMR
2023-10-04T22:33:26.363527+03:00 mavi-ThinkPad-T14s kernel: [ 1087.066834] 
amdgpu :06:00.0: amdgpu: RAS: optional ras ta ucode is not available
2023-10-04T22:33:26.375796+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078189] 
amdgpu :06:00.0: amdgpu: RAP: optional rap ta ucode is not available
2023-10-04T22:33:26.375806+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078196] 
amdgpu :06:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not 
available
2023-10-04T22:33:26.375808+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078204] 
amdgpu :06:00.0: amdgpu: SMU is resuming...
2023-10-04T22:33:26.375809+03:00 mavi-ThinkPad-T14s kernel: [ 1087.079063] 
amdgpu :06:00.0: amdgpu: SMU is resumed succ

[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault

[Martin Vysny]

Thanks Mario! I checked, and I have the newest mesa:

```
$ apt search mesa-vdpau
Sorting... Done
Full Text Search... Done
mesa-vdpau-drivers/mantic,now 23.2.1-1ubuntu2 amd64 [installed,automatic]
  Mesa VDPAU video acceleration drivers
```

Funny thing is that the bug is no longer reproducible - everything is
working properly, yay! Could it be that mesa was upgraded a couple of
days ago, resolving the issue?

Anyways, the issue looks to be fixed now. Thanks again!

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

Title:
  amdgpu: [gfxhub0] no-retry page fault

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

Bug description:
  Whenever I use Intellij IDEA, after a couple of minutes the screen
  locks up and pretty much renders the machine unusable. I can still ssh
  to it, but the UI is pretty much gone and doesn't respond to
  Ctrl+Alt+F* keys.

  The setup: the machine is connected to an external monitor via USB-C.
  Running kernel 6.5 on Ubuntu 23.10.

  There's the following in kern.log:

  ```
  2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [  422.206433] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663)
  2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [  422.206450] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xb15852923000 
from IH client 0x1b (UTCL2)
  2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [  422.206460] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431
  2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [  422.206466] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
  2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [  422.206471] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x1
  2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [  422.206476] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
  2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [  422.206481] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [  422.206485] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
  2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [  422.206490] 
amdgpu :06:00.0: amdgpu:  RW: 0x0
  2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [  422.206497] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663)
  2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [  422.206506] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xb07248096000 
from IH client 0x1b (UTCL2)
  2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [  422.206514] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431
  2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [  422.206519] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
  2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [  422.206524] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x1
  2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [  422.206528] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
  2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [  422.206533] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [  422.206538] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
  2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [  422.206542] 
amdgpu :06:00.0: amdgpu:  RW: 0x0
  2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [  422.206549] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663)
  2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [  422.206556] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xaf8c3d808000 
from IH client 0x1b (UTCL2)
  2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [  422.206564] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431
  2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [  422.206569] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
  2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [  422.206574] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x1
  2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [  422.206578] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
  2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [  4

[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools

[Eilidh Martin]

There's a difference between "this package is required to allow people
to use our paid services" and "this package spams everyone who doesn't
pay for our paid services". This flies in the face of the whole ethos of
free software imo.

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

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

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


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

[Touch-packages] [Bug 2024985] [NEW] Bluetooth doesn't enable

[Martin Packwood]

Public bug reported:

martin@studio-as6:~$ sudo dmesg | egrep -i 'blue|firm' 
[0.119642] Spectre V2 : Enabling Restricted Speculation for firmware calls
[0.278739] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[2.462372] [drm] Loading DMUB firmware via PSP: version=0x0422
[2.463264] [drm] Found VCN firmware Version ENC: 1.21 DEC: 2 VEP: 0 
Revision: 10
[2.463267] amdgpu :e6:00.0: amdgpu: Will use PSP to load VCN firmware
[4.073508] Bluetooth: Core ver 2.22
[4.074051] NET: Registered PF_BLUETOOTH protocol family
[4.074053] Bluetooth: HCI device and connection manager initialized
[4.074057] Bluetooth: HCI socket layer initialized
[4.074059] Bluetooth: L2CAP socket layer initialized
[4.074064] Bluetooth: SCO socket layer initialized
[4.257367] mt7921e :03:00.0: WM Firmware Version: 00, Build 
Time: 20220908203253
[6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110
[7.328550] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[7.328553] Bluetooth: BNEP filters: protocol multicast
[7.328556] Bluetooth: BNEP socket layer initialized


Note the line:
[6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110

UI carries on, but the error is fatal and no devices can be found.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.19.0-1017.18~22.04.1-lowlatency 5.19.17
Uname: Linux 5.19.0-1017-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Jun 25 14:25:34 2023
InstallationDate: Installed on 2023-06-25 (0 days ago)
InstallationMedia: Ubuntu-Studio 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230221)
InterestingModules: bnep bluetooth
MachineType: ASUSTeK COMPUTER INC. MINIPC PN53
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-1017-lowlatency 
root=UUID=933611e5-18b7-4290-98f3-d60eb962bdad ro threadirqs quiet splash 
vt.handoff=1
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2023
dmi.bios.release: 2.3
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 20300
dmi.board.asset.tag: Default string
dmi.board.name: PN53
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 35
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr20300:bd02/02/2023:br2.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN53:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPN53:rvrRev1.xx:cvnDefaultstring:ct35:cvrDefaultstring:skuSKU:
dmi.product.family: Vivo PC
dmi.product.name: MINIPC PN53
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 
rfkill:
 1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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


** Tags: amd64 apport-bug jammy

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

Title:
  Bluetooth doesn't enable

Status in bluez package in Ubuntu:
  New

Bug description:
  martin@studio-as6:~$ sudo dmesg | egrep -i 'blue|firm' 
  [0.119642] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.278739] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.462372] [drm] Loading DMUB firmware via PSP: version=0x0422
  [2.463264] [drm] Found VCN firmware Version ENC: 1.21 DEC: 2 VEP: 0 
Revision: 10
  [2.463267] amdgpu :e6:00.0: amdgpu: Will use PSP to load VCN firmware
  [4.073508] Bluetooth: Core ver 2.22
  [4.074051] NET: Registered PF_BLUETOOTH protocol family
  [4.074053] Bluetooth: HCI device and connection manager initialized
  [4.074057] Bluetooth: HCI socket layer initialized
  [4.074059] Bluetooth: L2CAP socket layer initialized
  [4.074064] Bluetooth: SCO socket layer initialized
  [4.257367] mt7921e :03:00.0: WM Firmware Version: 00, Build 
Time: 20220908203253
  [6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110
  [7.328550] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.328553] Bluetooth: BNEP filters: protocol multicast
  [7.328556] Bluetooth: BNEP socket layer initialized

  
  Note the line:
  [6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110

  UI carries on, but the error is fatal and no devices can be found.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-1017.18~22.04.1-lowlatency 5.19.17
  Uname: Linux 5.19.0-1017-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: K

[Touch-packages] [Bug 2024558] [NEW] package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Martin Nedelkoski]

Public bug reported:

sdo do-release-upgrade

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-75-generic 5.15.0-75.82
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jun 21 10:56 seq
 crw-rw 1 root audio 116, 33 Jun 21 10:56 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Wed Jun 21 10:58:36 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /sys/bus/usb/devices/usb1/rx_lanes: No such file or directory
 /sys/bus/usb/devices/usb1/tx_lanes: No such file or directory
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: DigitalOcean Droplet
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz boot=live skipconfig 
fromiso=live/rescue_rootfs.squashfs net.ifnames=0 ---
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to jammy on 2023-06-21 (0 days ago)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: DigitalOcean
dmi.bios.version: 20171212
dmi.board.asset.tag: 360900599
dmi.board.name: Droplet
dmi.board.vendor: DigitalOcean
dmi.board.version: 20171212
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-6.1
dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:rvnDigitalOcean:rnDroplet:rvr20171212:cvnQEMU:ct1:cvrpc-i440fx-6.1:
dmi.product.family: DigitalOcean_Droplet
dmi.product.name: Droplet
dmi.product.version: 20171212
dmi.sys.vendor: DigitalOcean

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


** Tags: amd64 apport-package jammy uec-images

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

Title:
  package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  sdo do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-75-generic 5.15.0-75.82
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 21 10:56 seq
   crw-rw 1 root audio 116, 33 Jun 21 10:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Wed Jun 21 10:58:36 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /sys/bus/usb/devices/usb1/rx_lanes: No such file or directory
   /sys/bus/usb/devices/usb1/tx_lanes: No such file or directory
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: DigitalOcean Droplet
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz boot=live skipconfig 
fromiso=live/rescue_rootfs.squashfs net.ifnames=0 ---
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Up

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Martin Pecka]

There is downstream software depending on python3-packaging to work
correctly. That library is affected, too, because it checks for strict
compliance to PEP 440. And, obviously, it can't be fixed by fixing the
packaging library, as it does its work correctly.

Example downstream usage: https://github.com/ros-
infrastructure/rosdep/pull/909 .

Would this be enough to support an SRU for all projects with wrong
version strings in bionic and the other releases?

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python 

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Martin Pecka]

> Setuptools is not in bionic

I don't understand. I clearly see it there:
https://webcache.googleusercontent.com/search?q=cache:fZGhFT_sSb8J:https://packages.ubuntu.com/bionic/python-
setuptools . Or am I missing something?

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that ver

[Touch-packages] [Bug 2019722] Re: ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client

[Martin-Éric Racine]

1) isc-dhcp-client doesn't do IPv6 well and cannot handle a dual-stack
case at all.

2) isc-dhcp-client is EOL upstream.

3) https://bugs.launchpad.net/ubuntu/+source/dhcpcd5/+bug/2019191

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

Title:
  ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-
  client

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
  there is a compelling reason to depend on a specific DHCP
  implementation, this should be changed to "isc-dhcp-client | dhcp-
  client" instead.

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


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

[Touch-packages] [Bug 2019722] Re: ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client

[Martin-Éric Racine]

Could it Depends on dhcp-client and let APT decide which package
providing this has the highest priority?

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

Title:
  ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-
  client

Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
  there is a compelling reason to depend on a specific DHCP
  implementation, this should be changed to "isc-dhcp-client | dhcp-
  client" instead.

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


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

[Touch-packages] [Bug 2019722] [NEW] ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client

[Martin-Éric Racine]

Public bug reported:

ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
there is a compelling reason to depend on a specific DHCP
implementation, this should be changed to "isc-dhcp-client | dhcp-
client" instead.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-
  client

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
  there is a compelling reason to depend on a specific DHCP
  implementation, this should be changed to "isc-dhcp-client | dhcp-
  client" instead.

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


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

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Martin Pecka]

>  We ship setuptools in Ubuntu, and the version of setuptools shipped
in these releases does not trigger the issue.

It does for me (on Bionic).

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example:

[Touch-packages] [Bug 2019122] Re: Autopkgtest failure

[Martin Pitt]

https://github.com/martinpitt/umockdev/issues/208

Thanks Heinrich!

** Bug watch added: github.com/martinpitt/umockdev/issues #208
   https://github.com/martinpitt/umockdev/issues/208

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

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

Title:
  Autopkgtest failure

Status in umockdev package in Ubuntu:
  In Progress

Bug description:
  Autopkgtests fail when trying to delete a missing file.

  tests/test-umockdev-run.vala:596:
  checked_remove ("/tmp/.X11-unix/X5");

  Upstream has a patch for a similar problem:
  a2953b1122f4 ("test: Allow missing /tmp/.X5-lock files”)

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


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

[Touch-packages] [Bug 1685484] Re: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work

[Martin]

Hello,

On Ubuntu desktop 22.04 LTS, it seems that the hook is not executed. I'm
not sure how to verify that but sure thing is the DHCP is well
announcing the ntp server.

DHCP4.OPTION[8]:ntp_servers = X.X.X.X
DHCP4.OPTION[18]:   requested_ntp_servers = 1

Could someone help ?

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

Title:
  DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd package in Debian:
  Fix Released

Bug description:
  I think it's regression for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1578663 in
  zesty.

  1. NTP servers are send via DHCP and seen by NM:

  $ nmcli con show connection1 | grep ntp
  DHCP4.OPTION[30]:   requested_ntp_servers = 1
  DHCP4.OPTION[31]:   ntp_servers = 80.50.231.226 
217.96.29.26 212.160.106.226

  2. timesyncd is using hardcoded default NTP server:

  $ systemctl -n 200 status systemd-timesyncd.service
  * systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
    Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
     `-disable-with-time-daemon.conf
     Active: active (running) since Sat 2017-04-22 13:12:23 CEST; 16min ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 576 (systemd-timesyn)
     Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
  Tasks: 2 (limit: 4915)
     Memory: 1.5M
    CPU: 20ms
     CGroup: /system.slice/systemd-timesyncd.service
     `-576 /lib/systemd/systemd-timesyncd

  Apr 22 13:12:23 slodki systemd[1]: Starting Network Time Synchronization...
  Apr 22 13:12:23 slodki systemd[1]: Started Network Time Synchronization.
  Apr 22 13:12:53 slodki systemd-timesyncd[576]: Synchronized to time server 
91.189.89.199:123 (ntp.ubuntu.com).

  3. There are not other time sync deamons installed:

  $ cat 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  [Unit]
  # don't run timesyncd if we have another NTP daemon installed
  ConditionFileIsExecutable=!/usr/sbin/ntpd
  ConditionFileIsExecutable=!/usr/sbin/openntpd
  ConditionFileIsExecutable=!/usr/sbin/chronyd
  ConditionFileIsExecutable=!/usr/sbin/VBoxService

  $ ls -l /usr/sbin/{ntpd,openntpd,chronyd,VBoxService}
  ls: cannot access '/usr/sbin/ntpd': No such file or directory
  ls: cannot access '/usr/sbin/openntpd': No such file or directory
  ls: cannot access '/usr/sbin/chronyd': No such file or directory
  ls: cannot access '/usr/sbin/VBoxService': No such file or directory

  4. There is only one default timesyncd.conf file with default values:

  $ sudo find / -iname \*timesync\*
  /etc/systemd/timesyncd.conf
  /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
  /etc/dhcp/dhclient-exit-hooks.d/timesyncd
  /usr/share/man/man5/timesyncd.conf.d.5.gz
  /usr/share/man/man5/timesyncd.conf.5.gz
  /usr/share/man/man8/systemd-timesyncd.8.gz
  /usr/share/man/man8/systemd-timesyncd.service.8.gz
  
/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-6NwdRT
  /lib/systemd/systemd-timesyncd
  /lib/systemd/system/systemd-timesyncd.service
  /lib/systemd/system/systemd-timesyncd.service.d
  
/var/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-jz0q47

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

  [Time]
  #NTP=
  #FallbackNTP=ntp.ubuntu.com

  5. DHCP hook installed as /etc/dhcp/dhclient-exit-hooks.d/timesyncd is
  not working,
  TIMESYNCD_CONF=/run/systemd/timesyncd.conf.d/01-dhclient.conf is not
  created.

  6. After manually executing steps from hook all works as expected:

  $ sudo mkdir -p /run/systemd/timesyncd.conf.d/
  $ sudo cat  [Time]
  > NTP=80.50.231.226 217.96.29.26 212.160.106.226
  > EOF
  $ sudo systemctl try-restart systemd-timesyncd.service
  $ sudo systemctl status systemd-timesyncd.service
  * systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
    Drop-In: /lib/systemd/system/system

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Martin Pecka]

Ah, now I get it, thanks.

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

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Committed
Status in python-debian package in Ubuntu:
  Fix Committed
Status in reportbug package in Ubuntu:
  Fix Committed
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Committed
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

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


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

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Martin Pecka]

> Changed in python-debian (Ubuntu Bionic):
> status:   New → Invalid 

Can I ask about this change? How is it invalid for bionic? The name of
the package is wrong there, too... (for both python-distro-info an
python3-distro-info).

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

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Committed
Status in python-debian package in Ubuntu:
  Fix Committed
Status in reportbug package in Ubuntu:
  Fix Committed
Status in ubuntu-dev-tools package in Ubuntu:
  New
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

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


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

[Touch-packages] [Bug 1830914] Re: software-properties-gtk does not run at all!

[Martin Spacek]

** Changed in: software-properties (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  software-properties-gtk does not run at all!

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  software-properties-gtk does not even start!

  
  $ software-properties-gtk --debug

  ENABLED COMPS: {'universe', 'main'}
  INTERNET COMPS: {'universe', 'main'}
  MAIN SOURCES
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: http://archive.ubuntu.com/ubuntu

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: http://archive.ubuntu.com/ubuntu

  
  CHILD SOURCES
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: None

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: None

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
   BaseURI: http://security.ubuntu.com/ubuntu/

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
   BaseURI: http://security.ubuntu.com/ubuntu/

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe', 'main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: None

  
  CDROM SOURCES
  SOURCE CODE SOURCES
  DISABLED SOURCES
  ISV
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 200, in __init__
  self.init_livepatch()
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1482, in init_livepatch
  self.livepatch_page = LivepatchPage(self)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line 
51, in __init__
  self._lps = LivepatchService()
File 
"/usr/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 
93, in __init__
  self._session = requests_unixsocket.Session()
  NameError: name 'requests_unixsocket' is not defined

  {Exited with code 1.}

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.04
  Release:  19.04
  Codename: disco

  
  $ dpkg-query -l software-properties-gtk python3-requests-unixsocket

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion  Architecture Description
  
+++-===---===
  ii  python3-requests-unixsocket 0.1.5-3  all  Use requests to 
talk HTTP via a UNIX domain socket - Python 3.x
  ii  software-properties-gtk 0.97.11  all  manage the 
repositories that you install software from (gtk)

  
  $ sudo apt-get update
  {Works.}

  $ sudo apt-get dist-upgrade
  {Works.}

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


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

[Touch-packages] [Bug 1830914] Re: software-properties-gtk does not run at all!

[Martin Spacek]

@dexter in #1, I also tried moving the `import requests_unixsocket` line
up out of the try-except block, and also found that it worked. (None of
the other proposed solutions, including reinstalling all of the proposed
packages, had any effect). Strangely, afer *undoing* those change, i.e.
moving the `import requests_unixsocket` line back into the try-except
block, software-properties-gtk was *still* able to start!

Not sure how to explain this, other than perhaps some race condition
(interprocess comms via DBus?), or perhaps some old .pyc file that was
regenerated after the source .py file as updated. Who knows. Either way,
this is still a huge issue. This was a fresh install of Xubuntu 20.04.5.
Issue started happening a couple of weeks after installing the OS. No
idea what triggered it.

Note that `import dateutil.parser` works fine. Everything in that try-
except block imports fine when I try it in a separate python3 session.
Also, if I try pasting `print(requests_unixsocket)` anywhere outside
that block, it works fine. It was only when I tried pasting it in
`LivepatchService.__init__` that it failed, almost as if some other
module was internally deleting the name from the namespace. Very
mysterious.

Also note that I completely uninstalled snap (which I absolutely detest)
on this system, but software-properties-gtk was working fine for a
couple of weeks after uninstalling snap. I haven't had this problem on
another fully update Xubuntu 20.04 system, where I also uninstalled snap
long ago.

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

Title:
  software-properties-gtk does not run at all!

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  software-properties-gtk does not even start!

  
  $ software-properties-gtk --debug

  ENABLED COMPS: {'universe', 'main'}
  INTERNET COMPS: {'universe', 'main'}
  MAIN SOURCES
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: http://archive.ubuntu.com/ubuntu

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: http://archive.ubuntu.com/ubuntu

  
  CHILD SOURCES
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: None

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: None

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
   BaseURI: http://security.ubuntu.com/ubuntu/

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
   BaseURI: http://security.ubuntu.com/ubuntu/

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe', 'main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: None

  
  CDROM SOURCES
  SOURCE CODE SOURCES
  DISABLED SOURCES
  ISV
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 200, in __init__
  self.init_livepatch()
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1482, in init_livepatch
  self.livepatch_page = LivepatchPage(self)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line 
51, in __init__
  self._lps = LivepatchService()
File 
"/usr/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 
93, in __init__
  self._session = requests_unixsocket.Session()
  NameError: name 'requests_unixsocket' is not defined

  {Exited with code 1.}

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.04
  Release:  19.04
  Codename: disco

  
  $ dpkg-query -l software-properties-gtk python3-requests-unixsocket

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion  Architecture Description
  
+++-===---===
  ii  python3-requests-unixsocket 0.1.5-3  all  Use requests to 
talk HTTP via a UNIX domain socket - Python 3.x
  ii  software-properties-gtk 

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

[Tony Martin Berbel]

I think this might be related:

journalctl -p 3 -xb
nov 15 12:53:55 cinnamon systemd-udevd[643]: event6: Failed to call 
EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument


sudo cat /proc/bus/input/devices | grep -C 5 event6
I: Bus=0019 Vendor= Product= Version=
N: Name="Eee PC WMI hotkeys"
P: Phys=eeepc-wmi/input0
S: Sysfs=/devices/platform/eeepc-wmi/input/input6
U: Uniq=
H: Handlers=rfkill kbd event6 
B: PROP=0
B: EV=100013
B: KEY=7e0 0 8000 0 0 1400b0010 8300180001100800 e 2
B: MSC=10

I'm using Ubuntu 22.10 5.19.0-23-generic Kernel Cinnamon 5.4.12

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

Title:
  Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103:
  Invalid argument

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel
  5.4.0-42-generic on Dell Latitude E6440.  Upon examining the output of
  journalctl -b, I see this:

  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Show Plymouth Boot Screen being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Forward Password Requests to Plymouth Directory Watch being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Set Up Additional Binary Formats being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
File System Check on Root Device being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Rebuild Hardware Database being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Platform Persistent Storage Archival being skipped.
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 
524288, num gpu pages 524288
  Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn 
acpi driver for receiving events
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to 
call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to 
call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument

  "Invalid argument" means that something goes wrong there, and I don't know 
what it is.
  On my laptop, event8 seems to be keyboard-related:

  $ sudo cat /proc/bus/input/devices | grep -C 5 event8
  I: Bus=0003 Vendor=045e Product=00db Version=0111
  N: Name="Microsoft Natural® Ergonomic Keyboard 4000"
  P: Phys=usb-:00:14.0-13.1/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9
  U: Uniq=
  H: Handlers=sysrq kbd event8 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=107

  The issue report
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is
  probably related but marked as a duplicate of a no longer existing
  issue report (#1750855).

  The report
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415
  describes a similar issue for older kernels; the differences pertain
  to error message, error code, input..., and, opposed to #19 there, I
  have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine
  is not a dual-boot machine.

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


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

[Touch-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)

[Tony Martin Berbel]

Same for me on Ubuntu Mate 22.04 5.15.0-52-generic and Cinnamon 5.2.7
/etc/X11/Xsession.d/30x11-common_xresources: ligne 16: has_option : commande 
introuvable
/etc/X11/Xsession.d/75dbus_dbus-launch: ligne 9: has_option : commande 
introuvable

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in Light Display Manager:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Touch-packages] [Bug 1995105] Re: add-apt-repository fails if it encounters immutable sources.list.d entry

[Martin Schmitt]

** Summary changed:

- apt-add-repository fails if it encounters immutable sources.list.d entry
+ add-apt-repository fails if it encounters immutable sources.list.d entry

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

Title:
  add-apt-repository fails if it encounters immutable sources.list.d
  entry

Status in software-properties package in Ubuntu:
  New

Bug description:
  Reason:

  We're trying to protect an internal APT source from trivial accidental
  modification by users (who do have sudo as root).

  Steps to reproduce:

  echo '# dummy' > /etc/apt/sources.list.d/dummy.list
  chattr +i /etc/apt/sources.list.d/dummy.list
  add-apt-repository -y ppa:longsleep/golang-backports

  Expected behaviour:

  New sources.list for the PPA gets created.

  Observed behaviour:

  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/add-apt-repository", line 357, in main
  shortcut.add()
File 
"/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 
221, in add
  self.add_source()
File 
"/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 
307, in add_source
  sourceslist.save()
File 
"/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", 
line 391, in save
  with open(filename, "w") as f:
  PermissionError: [Errno 1] Operation not permitted: 
'/etc/apt/sources.list.d/dummy.list'

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


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

[Touch-packages] [Bug 1995105] [NEW] add-apt-repository fails if it encounters immutable sources.list.d entry

[Martin Schmitt]

Public bug reported:

Reason:

We're trying to protect an internal APT source from trivial accidental
modification by users (who do have sudo as root).

Steps to reproduce:

echo '# dummy' > /etc/apt/sources.list.d/dummy.list
chattr +i /etc/apt/sources.list.d/dummy.list
add-apt-repository -y ppa:longsleep/golang-backports

Expected behaviour:

New sources.list for the PPA gets created.

Observed behaviour:

Traceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 364, in 
sys.exit(0 if addaptrepo.main() else 1)
  File "/usr/bin/add-apt-repository", line 357, in main
shortcut.add()
  File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", 
line 221, in add
self.add_source()
  File "/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", 
line 307, in add_source
sourceslist.save()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", 
line 391, in save
with open(filename, "w") as f:
PermissionError: [Errno 1] Operation not permitted: 
'/etc/apt/sources.list.d/dummy.list'

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

Title:
  add-apt-repository fails if it encounters immutable sources.list.d
  entry

Status in software-properties package in Ubuntu:
  New

Bug description:
  Reason:

  We're trying to protect an internal APT source from trivial accidental
  modification by users (who do have sudo as root).

  Steps to reproduce:

  echo '# dummy' > /etc/apt/sources.list.d/dummy.list
  chattr +i /etc/apt/sources.list.d/dummy.list
  add-apt-repository -y ppa:longsleep/golang-backports

  Expected behaviour:

  New sources.list for the PPA gets created.

  Observed behaviour:

  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/add-apt-repository", line 357, in main
  shortcut.add()
File 
"/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 
221, in add
  self.add_source()
File 
"/usr/lib/python3/dist-packages/softwareproperties/shortcuthandler.py", line 
307, in add_source
  sourceslist.save()
File 
"/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", 
line 391, in save
  with open(filename, "w") as f:
  PermissionError: [Errno 1] Operation not permitted: 
'/etc/apt/sources.list.d/dummy.list'

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


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

[Touch-packages] [Bug 1993991] [NEW] package linux-image-5.15.0-52-generic 5.15.0-52.58 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Martin Andersson]

Public bug reported:

s

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-52-generic 5.15.0-52.58
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lucrece1826 F pulseaudio
 /dev/snd/controlC1:  lucrece1826 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Oct 23 09:59:11 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-10-15 (8 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
IwConfig:
 lono wireless extensions.
 
 enp8s0no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic 
root=UUID=55ba579c-246e-43a7-a4fc-eb1591e7cc04 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu7
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-52-generic 5.15.0-52.58 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2016
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: 990FX Extreme9
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd03/29/2016:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme9:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

Title:
  package linux-image-5.15.0-52-generic 5.15.0-52.58 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  s

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lucrece1826 F pulseaudio
   /dev/snd/controlC1:  lucrece1826 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sun Oct 23 09:59:11 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-10-15 (8 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp8s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic 
root=UUID=55ba579c-246e-43a7-a4fc-eb1591e7cc04 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-52-generic 5.15.0-52.58 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2016
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 990FX Extreme9
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Touch-packages] [Bug 1993067] [NEW] Missing dependency of network-manager to iwd

[Martin Schreiber]

Public bug reported:

It seems that the current network-manager in Ubuntu 22.10 would like to
use iwd per default after the upgrade.

However, there's no dependency to the iwd package resulting in a lack of
wifi support after the upgrade.

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

** Project changed: launchpad => network-manager (Ubuntu)

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

Title:
  Missing dependency of network-manager to iwd

Status in network-manager package in Ubuntu:
  New

Bug description:
  It seems that the current network-manager in Ubuntu 22.10 would like
  to use iwd per default after the upgrade.

  However, there's no dependency to the iwd package resulting in a lack
  of wifi support after the upgrade.

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


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

[Touch-packages] [Bug 1960737] Re: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flags

[Martin Stjernholm]

I hit this too in my upgrade from 20.04 to 22.04.

I think it's because I had old commercial amdgpu drivers installed:

$ cat /etc/apt/sources.list.d/amdgpu.list 
deb https://repo.radeon.com/amdgpu/22.10.2/ubuntu focal main
#deb-src https://repo.radeon.com/amdgpu/22.10.2/ubuntu focal main

I changed "22.10.2" there to "latest" and upgraded the various AMD
packages. Now the symbols in /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
resolve fine with the command in comment #1. I also see that
wl_proxy_marshal_flags is present in one of the AMD libraries:

$ readelf -sW /opt/amdgpu/lib/x86_64-linux-gnu/libwayland-client.so.0 | grep 
wl_proxy_marshal_flags
73: 7910   284 FUNCGLOBAL DEFAULT   14 
wl_proxy_marshal_flags

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

Title:
  /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol
  lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined
  symbol: wl_proxy_marshal_flags

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol
  lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined
  symbol: wl_proxy_marshal_flags

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


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

[Touch-packages] [Bug 1982482] Re: SSH password login not attempted/denied

[Martin Pitt]

D'oh!

# cat /etc/ssh/sshd_config.d/10-cloudimg-settings.conf 
PasswordAuthentication no

rm + restart sshd, everything is hunky-dory. Sorry for the noise!

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

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

Title:
  SSH password login not attempted/denied

Status in openssh package in Ubuntu:
  Invalid
Status in openssh source package in Kinetic:
  Invalid

Bug description:
  I am in the process of updating our CI for Cockpit to kinetic [1]. I
  get a lot of test failures because SSH password login is broken.

  This can be replicated with a clean cloud instance, so it's not
  something that our VM build scripts do:

    curl -L -O 
https://cloud-images.ubuntu.com/daily/server/kinetic/current/kinetic-server-cloudimg-amd64.img
    # nothing fancy, just admin:foobar and root:foobar
    curl -L -O 
https://github.com/cockpit-project/bots/raw/main/machine/cloud-init.iso

  Boot the image:
    qemu-system-x86_64 -cpu host -enable-kvm -nographic -m 2048 -drive 
file=kinetic-server-cloudimg-amd64.img,if=virtio -snapshot -cdrom 
cloud-init.iso -net nic,model=virtio -net user,hostfwd=tcp::22001-:22

  For some reason that doesn't create an "admin" user. So log into VT as
  root:foobar and create a user:

    adduser test1

  Now, inside the VM VT:

    root@ubuntu:~# ssh  user1@localhost
    user1@localhost: Permission denied (publickey).

  The same happens when trying to ssh from outside:

    ❱❱❱ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost
    user1@localhost: Permission denied (publickey).

  It does not seem to even *attempt* password auth:

    ❱❱❱ ssh -vv -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost 2>&1|grep -i method
    debug1: Next authentication method: publickey
    debug2: we did not send a packet, disable method
    debug1: No more authentication methods to try.

  ... like it would to other OSes:

    debug1: Next authentication method: keyboard-interactive

  Password authentication is enabled by default:

    $ grep -i password /etc/ssh/sshd_config

    #PermitRootLogin prohibit-password
    # To disable tunneled clear text passwords, change to no here!
    #PasswordAuthentication yes
    #PermitEmptyPasswords no
    # Change to yes to enable challenge-response passwords (beware issues with
    # PasswordAuthentication.  Depending on your PAM configuration,
    # the setting of "PermitRootLogin without-password".
    # PAM authentication, then enable this but set PasswordAuthentication
    PasswordAuthentication yes

  [1] https://github.com/cockpit-project/bots/pull/3641 and
  https://github.com/cockpit-project/cockpit/pull/17582

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1

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


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

[Touch-packages] [Bug 1982482] Re: SSH password login not attempted/denied

[Martin Pitt]

I set LogLevel=DEBUG in /etc/ssh/sshd_config, systemctl restart sshd,
and I'm none the wiser:

debug1: Forked child 1652.
debug1: Set /proc/self/oom_score_adj to 0
debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8
debug1: inetd sockets after dupping: 4, 4
Connection from 127.0.0.1 port 45396 on 127.0.0.1 port 22 rdomain ""
debug1: Local version string SSH-2.0-OpenSSH_9.0p1 Ubuntu-1
debug1: Remote protocol version 2.0, remote software version OpenSSH_9.0p1 
Ubuntu-1
debug1: compat_banner: match: OpenSSH_9.0p1 Ubuntu-1 pat OpenSSH* compat 
0x0400
debug1: permanently_set_uid: 109/65534 [preauth]
debug1: list_hostkey_types: rsa-sha2-512,rsa-sha2-256 [preauth]
debug1: SSH2_MSG_KEXINIT sent [preauth]
debug1: SSH2_MSG_KEXINIT received [preauth]
debug1: kex: algorithm: sntrup761x25519-sha...@openssh.com [preauth]
debug1: kex: host key algorithm: rsa-sha2-512 [preauth]
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none [preauth]
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none [preauth]
debug1: expecting SSH2_MSG_KEX_ECDH_INIT [preauth]
debug1: SSH2_MSG_KEX_ECDH_INIT received [preauth]
debug1: rekey out after 134217728 blocks [preauth]
debug1: SSH2_MSG_NEWKEYS sent [preauth]
debug1: Sending SSH2_MSG_EXT_INFO [preauth]
debug1: expecting SSH2_MSG_NEWKEYS [preauth]
debug1: SSH2_MSG_NEWKEYS received [preauth]
debug1: rekey in after 134217728 blocks [preauth]
debug1: KEX done [preauth]
debug1: userauth-request for user user1 service ssh-connection method none 
[preauth]
debug1: attempt 0 failures 0 [preauth]
debug1: PAM: initializing for "user1"
debug1: PAM: setting PAM_RHOST to "127.0.0.1"
debug1: PAM: setting PAM_TTY to "ssh"
Connection closed by authenticating user user1 127.0.0.1 port 45396 [preauth]
debug1: do_cleanup [preauth]
debug1: monitor_read_log: child log fd closed
debug1: do_cleanup
debug1: PAM: cleanup
debug1: Killing privsep child 1653
debug1: audit_event: unhandled event 12


again, no trace of password/keyboard authentication.

Note that this is the same openssh package version that we've had in
Debian testing for three months, and that works just fine. So possibly
some broken PAM config?

** Description changed:

  I am in the process of updating our CI for Cockpit to kinetic [1]. I get
  a lot of test failures because SSH password login is broken.
  
  This can be replicated with a clean cloud instance, so it's not
  something that our VM build scripts do:
  
-   curl -L -O 
https://cloud-images.ubuntu.com/daily/server/kinetic/current/kinetic-server-cloudimg-amd64.img
-   # nothing fancy, just admin:foobar and root:foobar
-   curl -L -O 
https://github.com/cockpit-project/bots/raw/main/machine/cloud-init.iso
+   curl -L -O 
https://cloud-images.ubuntu.com/daily/server/kinetic/current/kinetic-server-cloudimg-amd64.img
+   # nothing fancy, just admin:foobar and root:foobar
+   curl -L -O 
https://github.com/cockpit-project/bots/raw/main/machine/cloud-init.iso
  
  Boot the image:
-   qemu-system-x86_64 -cpu host -enable-kvm -nographic -m 2048 -drive 
file=kinetic-server-cloudimg-amd64.img,if=virtio -snapshot -cdrom 
cloud-init.iso -net nic,model=virtio -net user,hostfwd=tcp::22001-:22
+   qemu-system-x86_64 -cpu host -enable-kvm -nographic -m 2048 -drive 
file=kinetic-server-cloudimg-amd64.img,if=virtio -snapshot -cdrom 
cloud-init.iso -net nic,model=virtio -net user,hostfwd=tcp::22001-:22
  
  For some reason that doesn't create an "admin" user. So log into VT as
  root:foobar and create a user:
  
-   adduser test1
+   adduser test1
  
  Now, inside the VM VT:
  
-   root@ubuntu:~# ssh  user1@localhost
-   user1@localhost: Permission denied (publickey).
+   root@ubuntu:~# ssh  user1@localhost
+   user1@localhost: Permission denied (publickey).
  
  The same happens when trying to ssh from outside:
  
-   ❱❱❱ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost
-   user1@localhost: Permission denied (publickey).
+   ❱❱❱ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost
+   user1@localhost: Permission denied (publickey).
  
  It does not seem to even *attempt* password auth:
  
-   ❱❱❱ ssh -vv -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost 2>&1|grep -i method
-   debug1: Next authentication method: publickey
-   debug2: we did not send a packet, disable method
-   debug1: No more authentication methods to try.
+   ❱❱❱ ssh -vv -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost 2>&1|grep -i method
+   debug1: Next authentication method: publickey
+   debug2: we did not send a packet, disable method
+   debug1: No more authentication methods to try.
  
  ... like it would to other OSes:
  
-   debug1: Next authentication method: keyboard-interactive
+   debug1: Next authentication method: keyboard

[Touch-packages] [Bug 1982482] [NEW] SSH password login not attempted/denied

[Martin Pitt]

Public bug reported:

I am in the process of updating our CI for Cockpit to kinetic [1]. I get
a lot of test failures because SSH password login is broken.

This can be replicated with a clean cloud instance, so it's not
something that our VM build scripts do:

  curl -L -O 
https://cloud-images.ubuntu.com/daily/server/kinetic/current/kinetic-server-cloudimg-amd64.img
  # nothing fancy, just admin:foobar and root:foobar
  curl -L -O 
https://github.com/cockpit-project/bots/raw/main/machine/cloud-init.iso

Boot the image:
  qemu-system-x86_64 -cpu host -enable-kvm -nographic -m 2048 -drive 
file=kinetic-server-cloudimg-amd64.img,if=virtio -snapshot -cdrom 
cloud-init.iso -net nic,model=virtio -net user,hostfwd=tcp::22001-:22

For some reason that doesn't create an "admin" user. So log into VT as
root:foobar and create a user:

  adduser test1

Now, inside the VM VT:

  root@ubuntu:~# ssh  user1@localhost
  user1@localhost: Permission denied (publickey).

The same happens when trying to ssh from outside:

  ❱❱❱ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost
  user1@localhost: Permission denied (publickey).

It does not seem to even *attempt* password auth:

  ❱❱❱ ssh -vv -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost 2>&1|grep -i method
  debug1: Next authentication method: publickey
  debug2: we did not send a packet, disable method
  debug1: No more authentication methods to try.

... like it would to other OSes:

  debug1: Next authentication method: keyboard-interactive

Password authentication is enabled by default:

  $ grep -i password /etc/ssh/sshd_config

  #PermitRootLogin prohibit-password
  # To disable tunneled clear text passwords, change to no here!
  #PasswordAuthentication yes
  #PermitEmptyPasswords no
  # Change to yes to enable challenge-response passwords (beware issues with
  # PasswordAuthentication.  Depending on your PAM configuration,
  # the setting of "PermitRootLogin without-password".
  # PAM authentication, then enable this but set PasswordAuthentication
  PasswordAuthentication yes

[1] https://github.com/cockpit-project/bots/pull/3641 and
https://github.com/cockpit-project/cockpit/pull/17582


ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: openssh-server 1:9.0p1-1

** Affects: openssh (Ubuntu)
 Importance: High
 Status: New

** Affects: openssh (Ubuntu Kinetic)
 Importance: High
 Status: New


** Tags: kinetic regression-release

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

Title:
  SSH password login not attempted/denied

Status in openssh package in Ubuntu:
  New
Status in openssh source package in Kinetic:
  New

Bug description:
  I am in the process of updating our CI for Cockpit to kinetic [1]. I
  get a lot of test failures because SSH password login is broken.

  This can be replicated with a clean cloud instance, so it's not
  something that our VM build scripts do:

    curl -L -O 
https://cloud-images.ubuntu.com/daily/server/kinetic/current/kinetic-server-cloudimg-amd64.img
    # nothing fancy, just admin:foobar and root:foobar
    curl -L -O 
https://github.com/cockpit-project/bots/raw/main/machine/cloud-init.iso

  Boot the image:
    qemu-system-x86_64 -cpu host -enable-kvm -nographic -m 2048 -drive 
file=kinetic-server-cloudimg-amd64.img,if=virtio -snapshot -cdrom 
cloud-init.iso -net nic,model=virtio -net user,hostfwd=tcp::22001-:22

  For some reason that doesn't create an "admin" user. So log into VT as
  root:foobar and create a user:

    adduser test1

  Now, inside the VM VT:

    root@ubuntu:~# ssh  user1@localhost
    user1@localhost: Permission denied (publickey).

  The same happens when trying to ssh from outside:

    ❱❱❱ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost
    user1@localhost: Permission denied (publickey).

  It does not seem to even *attempt* password auth:

    ❱❱❱ ssh -vv -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
CheckHostIP=no -p 22001 user1@localhost 2>&1|grep -i method
    debug1: Next authentication method: publickey
    debug2: we did not send a packet, disable method
    debug1: No more authentication methods to try.

  ... like it would to other OSes:

    debug1: Next authentication method: keyboard-interactive

  Password authentication is enabled by default:

    $ grep -i password /etc/ssh/sshd_config

    #PermitRootLogin prohibit-password
    # To disable tunneled clear text passwords, change to no here!
    #PasswordAuthentication yes
    #PermitEmptyPasswords no
    # Change to yes to enable challenge-response passwords (beware issues with
    # PasswordAuthentication.  Depending on your PAM configuration,
    # the setting of "PermitRootLogin without-passwo

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

[Martin-Éric Racine]

Does dhcpcd5 version 9.4.1-0.1 solve the issue for you?

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  Confirmed
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  Invalid
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  Triaged
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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


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

[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

[Martin Schmitt]

We're seeing this same issue. The postinst script in the 22.04 package
seems to be missing a few lines that were still there in 21.10, one of
which would be the one that executes systemctl enable pcscd.socket.

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

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


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

[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts

[Martin Wimpress ]

@bkanbach I can version marco Recommends ensuring both packages update
in lockstep. I have spoken to the Ubuntu Security team and they will
handle the CVE assignment.

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Fix Committed
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Fix Committed
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

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


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

[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts

[Martin Wimpress ]

** Changed in: arctica-greeter (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: marco (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Fix Committed
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Fix Committed
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

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


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

[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts

[Martin Wimpress ]

** Changed in: arctica-greeter (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  In Progress
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  In Progress
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

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


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

[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts

[Martin Wimpress ]

** Changed in: marco (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  In Progress
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

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


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

[Touch-packages] [Bug 1892299] Re: [20.04] Keyboard volume rendered useless because of root's userspace?

[Martin Wimpress ]

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

** No longer affects: ubuntu-mate

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

Title:
  [20.04] Keyboard volume rendered useless because of root's userspace?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is super minor. Yet it's super juicy:

  Running 20.04-latest and with the following audio hardware
  configuration:

  $ arecord -L
  default
  Playback/recording through the PulseAudio sound server
  surround21
  2.1 Surround output to Front and Subwoofer speakers
  surround40
  4.0 Surround output to Front and Rear speakers
  surround41
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50
  5.0 Surround output to Front, Center and Rear speakers
  surround51
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  null
  Discard all samples (playback) or generate zero samples (capture)
  samplerate
  Rate Converter Plugin Using Samplerate Library
  speexrate
  Rate Converter Plugin Using Speex Resampler
  jack
  JACK Audio Connection Kit
  oss
  Open Sound System
  pulse
  PulseAudio Sound Server
  upmix
  Plugin for channel upmix (4,6,8)
  vdownmix
  Plugin for channel downmix (stereo) with a simple spacialization
  usbstream:CARD=HDMI
  HDA ATI HDMI
  USB Stream Output
  sysdefault:CARD=Generic
  HD-Audio Generic, ALC887-VD Analog
  Default Audio Device
  front:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Front speakers
  dmix:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Direct sample mixing device
  dmix:CARD=Generic,DEV=2
  HD-Audio Generic, ALC887-VD Alt Analog
  Direct sample mixing device
  dsnoop:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Direct sample snooping device
  dsnoop:CARD=Generic,DEV=2
  HD-Audio Generic, ALC887-VD Alt Analog
  Direct sample snooping device
  hw:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Direct hardware device without any conversions
  hw:CARD=Generic,DEV=2
  HD-Audio Generic, ALC887-VD Alt Analog
  Direct hardware device without any conversions
  plughw:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Hardware device with all software conversions
  plughw:CARD=Generic,DEV=2
  HD-Audio Generic, ALC887-VD Alt Analog
  Hardware device with all software conversions
  usbstream:CARD=Generic
  HD-Audio Generic
  USB Stream Output
  $

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
    Subdevices: 0/1
    Subdevice #0: subdevice #0
  card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD 
Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  $

  I am using card 2 off this last paste.

  If I open a folder in caja containing videos and I play one of them
  using regular user and celluloid, volume knob on my keyboard works
  fine.

  But if I then open any other video from an "Open as administrator"
  caja window, it will not play any sound(based on my non-expert status
  I can only assume that this happens because root space and user space
  do not share the same default audio settings??)

  First question/problem/request: just like when applying monitor
  resolution changes into Control Center and applying them system wide,
  can you also please make it the same for the audio hardware output? As
  from a user perspective, it makes no sense at all to segregate the
  hardware values for sound when jumping in root in Ubuntu.

  Now my real problem is if/when I close my caja window that is in
  priviledge mode and I then re-open a video w/ celluloid with my
  regular user, sounds of course works fine, but my keyboard volume knob
  isn't responding anymore even though I see the volume on screen going
  up and down when I scroll it, the sound waves do not actually increase
  nor decrease.

  Some full moons ago, I posted something on UM forum which related of
  something similiar and here it is as a FYI: https://ubuntu-
  mate.community/t/19-10-problem-with-my-sound/20338/3

  Furthermore, and again only as a FYI, I have blacklisted "hdi" and
  "snd_hda_codec_hdmi" in /etc/modprobe.d/snd-blacklist.conf and have
  rebooted my system to take effect. Hence maybe when you will try
  reproducing this you will also need to blacklist those 2 modules to
  get this volume control on your keyboard not listening...

  And while you have your hands into the audio code, and as of why I had
 

[Touch-packages] [Bug 1837765] Re: mono, crackly audio, device not appearing raspberry pi 2B

[Martin Wimpress ]

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

** No longer affects: ubuntu-mate

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

Title:
  mono, crackly audio, device not appearing raspberry pi 2B

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I am using the 3.5 jack to speakers on a raspberry pi 2B

  As detailed here: https://ubuntu-mate.community/t/audio-output-mono-
  instead-of-stereo-ubuntu-18-04-1-rpi/18001

  Audio output is mono
  Audio output is delayed and crackly for desktop sounds, as well as sometimes 
simply silent

  I note that no sound device shows up in Sound Preferences / Hardware

  Some workarounds from that thread:

  Editing /etc/pulse/default.pa such that:

  load-module module-udev-detect tsched=0

  and commenting out:

  load-module module-suspend-on-idle

  Results in a device "Built-in Audio Analog mono output" showing up in Sound 
Preferences/Hardware,
  audio is mono, but does not crackle/miss and desktop sounds work seemingly as 
expected.

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


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

[Touch-packages] [Bug 1874689] Re: alsa force-reload needed to fix my sound after upgrade to 20.04

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

Title:
  alsa force-reload needed to fix my sound after upgrade to 20.04

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Mate 18.04 LTS to Ubuntu Mate 20.04 LTS
  "sudo alsa force-reload" is needed to fix my sound.

  I upgraded yesterday (23rd) before the official announcements of 20.04
  LTS. Using "do-release-upgrade -d".

  I'm not sure yet how often I have to run "sudo alsa force-reload".
  When I have no sound a reboot is not a guranteed fix although it
  worked once.

  Booting into a Ubuntu Desktop 20.04 LTS gets working sounds each time
  I tried.

  Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-26-generic

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


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

[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled via gnome-system-tools

[Martin Wimpress ]

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Lock screen can be bypassed when auto-login is enabled via gnome-
  system-tools

Status in arctica-greeter package in Ubuntu:
  Invalid
Status in gnome-system-tools package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in mate-screensaver package in Ubuntu:
  Invalid
Status in mate-session-manager package in Ubuntu:
  Invalid
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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


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

[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Martin Wimpress ]

This issue is caused by the Users and Groups utility which is part of
`gnome-system-tools`. When changing the password from "Asked on logon"
to "Not asked on logon" the user is added to the `nopasswdlogin` group
and this is what causes the switch-user screen to not ask for a
password.

If you select the option to not require a password to login during
installation, it is not possible to bypass authentication when switching
users. This is because `autologin-user` is set to your username in
`/etc/lightdm/lightdm.conf` and that works correctly.

`gnome-system-tools` was originally included in Ubuntu MATE because it
offers user and time management features. But it can now be removed from
the Ubuntu MATE default install because recent versions of MATE Control
Center provide user and time management.

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: Triaged => In Progress

** Summary changed:

- Lock screen can be bypassed when auto-login is enabled.
+ Lock screen can be bypassed when auto-login is enabled via gnome-system-tools

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

Title:
  Lock screen can be bypassed when auto-login is enabled via gnome-
  system-tools

Status in arctica-greeter package in Ubuntu:
  Invalid
Status in gnome-system-tools package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in mate-screensaver package in Ubuntu:
  Invalid
Status in mate-session-manager package in Ubuntu:
  Invalid
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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


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

[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Martin Wimpress ]

** Also affects: gnome-system-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: lightdm (Ubuntu)
   Status: Fix Committed => Invalid

** Changed in: arctica-greeter (Ubuntu)
   Status: New => Invalid

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

** Changed in: gnome-system-tools (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: mate-screensaver (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-mate-meta (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

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

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in arctica-greeter package in Ubuntu:
  Invalid
Status in gnome-system-tools package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in mate-screensaver package in Ubuntu:
  Invalid
Status in mate-session-manager package in Ubuntu:
  Invalid
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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


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

[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Martin Wimpress ]

** Also affects: mate-screensaver (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: arctica-greeter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in arctica-greeter package in Ubuntu:
  New
Status in gnome-system-tools package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Fix Committed
Status in mate-screensaver package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  Invalid

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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


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

[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Martin Wimpress ]

** No longer affects: ubuntu-mate

** Changed in: mate-session-manager (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in arctica-greeter package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Fix Committed
Status in mate-screensaver package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  Invalid

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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


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

[Touch-packages] [Bug 1769362] Re: with multiple monitors, lightDM does not appear on the display set as primary

[Martin Wimpress ]

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

** No longer affects: ubuntu-mate

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

Title:
  with multiple monitors, lightDM does not appear on the display set as
  primary

Status in lightdm package in Ubuntu:
  New

Bug description:
  TV hooked up to a laptop; laptop is marked as Primary Display.  With
  the TV turned off, the laptop went idle into the screensaver.  When
  woken, lightDM is rendered on the (off) TV not the laptop display.

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


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

[Touch-packages] [Bug 1893590] Re: [20.04.1] Uncooperative network center (more irritant than joy)

[Martin Wimpress ]

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

** No longer affects: ubuntu-mate

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

Title:
  [20.04.1] Uncooperative network center (more irritant than joy)

Status in network-manager package in Ubuntu:
  New

Bug description:
  A network center in GUI. So many reasons to love it. Here's a
  particularly basic one which surely would make my mom want NOT to use
  Linux:

  Network connections -> Wired connection -> IPv4 settings -> Method: from 
Automatic(DHCP) to Manual + add address/netmask/gateway+dns server+SAVE = OK
  ip a = specified IP address manually

  Network connections -> Wired connection -> IPv4 settings -> Method: from 
Manual to Automatic(DHCP)+SAVE = OK
  disconnect -> reconnect
  ip a = same specified IP address manually!! But I was expecting to be leased 
a DHCP IP??

  solution: Network connections -> Wired connection -> IPv4 settings ->
  delete manually added IP address + SAVE + disconnect + reconnect = ip
  a = DHCP IP, \o/

  Food for thought: Thankfully I didn't have 6 different IP
  configurations in place...

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


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

[Touch-packages] [Bug 1904796] Re: screensaver hijacks audio preferences

[Martin Wimpress ]

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

** No longer affects: ubuntu-mate

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

Title:
  screensaver hijacks audio preferences

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using 20.04.1-latest, on a laptop that is plugged via HDMI to a tv:
  if/when the audio is set to digital and the computer falls into sleep
  mode, upon waking up, the session's audio defaults back to analog
  audio output.

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


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

[Touch-packages] [Bug 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04

[Martin Wimpress ]

** No longer affects: ubuntu-mate

** No longer affects: mate-themes (Ubuntu)

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

Title:
  Indeterminate Qt progress bars don't display properly in 20.04

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar
  (meaning its minimum and maximum values have both been set to zero)
  does not display properly. It is supposed to animate in a way that
  shows that something is happening with an unknown time remaining.
  Instead, it sits still with its progress bar showing approximately 25
  to 30% progress.

  To test this, make a simple Qt program with a QProgressBar in the main
  window, and add these lines to the constructor of the main window:

  ui->progressBar->setMinimum(0);
  ui->progressBar->setMaximum(0);

  This problem is not present in standard Ubuntu 20.04. Standard Ubuntu
  correctly animates the indeterminate progress bar. It's unclear to me
  which package is at fault, but it seems to be something specific to
  Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem.

  Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it
  doesn't have this problem.

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


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

[Touch-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] device (p2p-dev-wlo1): supplicant management interface state: 
disconnected -> scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22

[Touch-packages] [Bug 1942694] Re: [21.04] Uncooperative WiFi manager on TTY7 for proper end user integration

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

Title:
  [21.04] Uncooperative WiFi manager on TTY7 for proper end user
  integration

Status in network-manager package in Ubuntu:
  New

Bug description:
  Desc.:
  Using 21.04-latest on a Dell XPS 13" laptop and working on TTY7, the wifi 
manager becomes uncooperative after, it seems, it gets tied up to 2 wifi 
profiles.

  Recreation steps:
  1. Install 21.04-latest + full patch it using your home LAN WiFi AP;
  2. Login newly installed system + test Internet = it works fine;
  3. Take same laptop and go to a hotel(for example): manually create a new 
profile for the new WiFi network from TTY7, login "hotel" wifi network profile 
+ test Internet = it works fine;
  4. Physically move back to where your "home" LAN WiFi profile is and boot 
system:

  Problem now happens::
  1. Internet doesn't work off WiFi;
  2. Click on the "Wi-Fi Network" icon at the top hand right side of the screen 
-> "no network devices available";
  3. Select "Edit connections" -> there will be your 2 profiles there: "home" 
and "hotel", delete "hotel" -> OK;
  4. "no network devices available" still shows under "Wi-Fi Network" at the 
top.
  MY USER EXPECTATIONS: Get a new list of close by AP and/or automatically 
reconnect to "profile 1: home".
  NOTA: Both profiles are set to priority 0 and also all set to "all uses may 
connect to this network". Could this be the problem?

  Solution:
  Reboot system.
  After reboot. TTY7 will have defaulted back to the "home" WiFi profile and 
Internet will work at the first user attempt.

  xo

  PS: I have been having this problem from way before hirsute.

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


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

[Touch-packages] [Bug 1920813] Re: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session required pam_loginuid.so" for compatibility with user applications

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

Title:
  /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have
  uncommented "session requiredpam_loginuid.so" for
  compatibility with user applications

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.04
  2. Launch MATE Terminal
  3. Execute `cat /proc/self/loginuid`

  Expected results:
  * above command returned 1000

  Actual results:
  * above command returned 4294967295

  
  Remediation:
  * edit /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin to uncomment

  session requiredpam_loginuid.so

  for compatibility with user applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Mar 22 22:41:05 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

Title:
  lightdm-guest-session ICEauthority error

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Focal:
  Fix Released
Status in lightdm source package in Groovy:
  Fix Released
Status in lightdm source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  If you enable the guest session feature on e.g. Ubuntu MATE, you are
  met by an error message when trying to enter a guest session:

  "Could not update file ICEauthority file /run/user/XXX/ICEauthority"

  Even if it's not always a fatal error (the login may succeed after a
  few minutes), the user experience is really bad, and you are inclined
  to conclude that you are completely blocked from using the feature.

  The proposed fix adds a rule to the lightdm-guest-session AppArmor
  profile and prevents the error from happening.

  [Test Plan]

  On an updated Ubuntu MATE installation:

  * Enable guest session

sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n"
  >/etc/lightdm/lightdm.conf.d/50-enable-guest.conf'

  * Install lightdm from {focal,groovy}-proposed

  * Reboot

  You should now be able to enter a guest session without being stopped
  by the ICEauthority error.

  [Where problems could occur]

  This one-liner is a harmless change.

  The guest session is run in an unconfined mode since Ubuntu 16.10.
  That's why the feature is disabled by default.

  So if the additional rule would be wrong somehow (which I have no
  reason to believe), it wouldn't break the AppArmor security layer for
  the simple reason that it's already broken to begin with.

  [Original description]

  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).

  ## How to reproduce:
   - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
   - enable guest user session
   - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
  ```
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log

  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log

  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log

  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
  Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this:
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
    owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have no clue about apparmor and I'm unsure where to post this but 
I hope this maybe helps some other people in the future.

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


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

[Touch-packages] [Bug 1894356] Re: could not acquire name on session bus by simultaneous login by XDMCP and keyboard

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

Title:
  could not acquire name on session bus by simultaneous login by XDMCP
  and keyboard

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  New
Status in lightdm package in Debian:
  Confirmed

Bug description:
  This symptom is observed with Ubuntu Mate 20.04.

  1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as

  [XDMCPServer]
  enabled=true

  and restart lightdm.

  2. Login as a normal user from keyboard.

  3. Login as the same user as 2 from XDMCP gives
  "Could not acquire name on session bus"
  and I cannot login from XDMCP.
  Without Step 2, XDMCP login succeeds.

  The same symptom is reported at
  https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001
  which recommends removal of "dbus-user-session" Ubuntu package.

  I worked around the above issue by putting
  "unset DBUS_SESSION_BUS_ADDRESS"
  in /etc/X11/Xsession.d/

  The same issue is also reported at
  https://bugs.launchpad.net/ubuntu-mate/+bug/1769353

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


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

[Touch-packages] [Bug 1898771] Re: suspend does not lock screen Fresh Ubuntu Mate 20.04.1

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

Title:
  suspend does not lock screen Fresh Ubuntu Mate 20.04.1

Status in lightdm package in Ubuntu:
  New

Bug description:
  When suspending my freshly installed 20.04.1 system I noticed that on waking 
a password is not required. lightdm does not have locking enabled on suspend. A 
workaround I found from pszafer
   on archlinux blog. 

  Quoted below:

  
  create lockscreen.sh file somewhere in your home directory with:

  #!/bin/sh
  XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" dm-tool lock
  - I've prefer just for sure creating dmlock.service file in home dir and 
create symlink to /etc/systemd/system.
  File has to be in /etc/systemd/system/dmlock.service

  [Unit]
  Description=DM Lock before sleep
  Before=sleep.target

  [Service]
  ExecStart=/home/user/dir/lockscreen.sh

  [Install]
  WantedBy=sleep.target
  For your needs, you probably need hibernate.target.

  Next run following commands:

  systemctl daemon-reload
  systemctl enable dmlock.service
  Just for sure it is working you could run:

  systemctl list-unit-files
  systemctl start dmlock.service
  Hope it helps you a little

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


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