[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
Thanks for the fix Gunnar. The reason I didn't raise it with you earlier was because I figured a better solution would be to: 1. Patch to revert to a colon in the default US English translation. 2. Propose to upstream to not use RATIO in future because fonts don't often implement the Mathematical Operators block. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Won't Fix Status in language-pack-gnome-en package in Ubuntu: Won't Fix Status in language-pack-gnome-en-base package in Ubuntu: Won't Fix Status in language-selector package in Ubuntu: Fix Released Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
> (Daniel: I can't explain how you hid the issue by using en_AU.UTF-8, though.) Maybe en_AU inherits from en_GB? ** Changed in: gnome-desktop (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: language-pack-gnome-en (Ubuntu) Status: New => Won't Fix ** Changed in: language-pack-gnome-en-base (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 language-pack-gnome-en in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Won't Fix Status in language-pack-gnome-en package in Ubuntu: Won't Fix Status in language-pack-gnome-en-base package in Ubuntu: Won't Fix Status in language-selector package in Ubuntu: Fix Released Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2031942] Re: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set
All autopkgtests have been cleared after retries (both lunar and jammy ones). -- 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/2031942 Title: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: Fix Committed Status in openssh source package in Lunar: Fix Committed Status in openssh source package in Mantic: Fix Released Bug description: [Impact] User of openssh reported an issue that affects Lunar and Jammy. If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand configuration in sshd_config that comes after it is ignored. In this scenario, where AuthorizedPrincipalsCommand is needed and set, users relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals' with permissions 755 as follows: #!/bin/sh if [ "$1" = "otheruser" ]; then echo certuser fi Exit the file. Ensure you are in the /root/reproducer/ directory: # adduser --disabled-password otheruser (Enter multiple times, leave all fields blank) Then do the same for another user: # adduser --disabled-password keyonlyuser Create a script '/root/reproducer/authorized_keys' with permissions 755 as follows: #!/bin/sh if [ "$1" = "keyonlyuser" ]; then echo fi Go to the /etc/ssh/sshd_config file. Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u AuthorizedKeysCommandUser root AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u AuthorizedPrincipalsCommandUser root TrustedUserCAKeys /root/reproducer/certuser/ca.pub Exit from the file and restart the ssh service: # systemctl restart ssh Use these commands to manifest the bug: # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key # ssh otheruser@localhost -i /root/reproducer/certuser/key -o CertificateFile=/root/reproducer/certuser/key-cert.pub Expected results: both ssh commands should succeed. Actual results: the second ssh fails because the AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set. [Where problems could occur] * The patch itself modifies only the servconf.c, so regressions should be limited to the server configuration. * Since the fix touches pointers, there might be regression related to memory handling and fetching data. -original report-- Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code: if (*activep && options->authorized_keys_command == NULL) *charptr = xstrdup(str + len); However, this is executed for both authorized_keys_command and authorized_principals_command. As a result, if authorized_keys_command is set (for instance, if using ec2-instance-connect), any AuthorizedPrincipalsCommand configuration in sshd_config is ignored. This is fixed in 9.4p1 with the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2031942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033569] Re: suddenly choked on multiseat config in a way that survives reboots and even purging it
Found a solution. There were two separate issues: FIRST ISSUE Apparently systemd likes to start up lightdm early, so early that on a reasonably fast system the GPU driver won't be ready in time ... (I thought this was what systemd's dependency handling was for, but never mind.) This seems to be a long-standing issue; it's neither multiseat- nor GPU- driver-specific. And considering this is just a budget AMD box, albeit a new one, it's going to bite more and more people in future. My hypothesis re. why the first few boots with lightdm worked is that I was still in the middle of setting up the box, i.e. a lot changed from one boot to the next. Either one of those changes triggered the timing issue, or "clean" boots are faster per se. The workarounds detailed in the Arch Wiki (https://wiki.archlinux.org/title/LightDM#LightDM_does_not_appear_or_monitor_only_displays_TTY_output) both work, to wit: 1) Add [LightDM] logind-check-graphical=true in /etc/lightdm/lightdm.conf - OR - 2) Enable early KMS by adding your GPU driver module to /etc/initramfs- tools/modules and running update-initramfs -k all -u. SECOND ISSUE: At some point while trying to fix this I deleted /var/lib/lightdm as well, which is lightdm's home directory. Since purging lightdm does not remove the lightdm user, reinstalling it will not (re)create this directory. Unfortunately the symptoms are the same as above--lightdm goes into a restart loop, then gives up. Now, the second issue probably isn't a bug, though the postinst script could at least print a warning if the home directory isn't present and writeable, but the first one is, IMHO. -- 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/2033569 Title: suddenly choked on multiseat config in a way that survives reboots and even purging it Status in lightdm package in Ubuntu: New Bug description: I have a bog-standard loginctl multiseat setup, using lightdm because of #2033323. Except for the lack of session locking, it worked beautifully, across multiple reboots. Until it didn't. Box woke from suspend, and to be fair was acting strangely even then (Steam suddenly tried to launch using the iGPU), so suspend may well be broken on this box, but if so, that's a separate issue. Anyway, I rebooted, no lightdm greeter to be seen, the screen on seat1 was black. I did not have easy access to seat0 at the time. The journal has, looping: systemd[1]: Failed to start Detect the available GPUs and deal with any system changes. systemd[1]: lightdm.service: Start request repeated too quickly. token systemd[1]: lightdm.service: Failed with result 'exit-code'. token systemd[1]: Failed to start Light Display Manager. The first line is from gpu-manager.service, whose log contains Vendor/Device Id: 1002:164e BusID "PCI:110@0:0:0" Is boot vga? no Error: can't access /sys/bus/pci/devices/:6e:00.0/driver The device is not bound to any driver. Vendor/Device Id: 1002:73ff BusID "PCI:3@0:0:0" Is boot vga? yes Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri x-0 log has vesa: Ignoring device with a bound kernel driver vesa: Ignoring device with a bound kernel driver (EE) Fatal server error: (EE) no screens found(EE) Scary. Thing is, both the iGPU and the dGPU are claimed by amdgpu, their "driver" symlink is accessible just fine. Switch back to gdm via dpkg- reconfigure, it boots up fine again. It's just lightdm that's hosed. I tried purging lightdm and lightdm-gtk-greeter, along with and /var/lib/lightdm, and reinstalling the packages, but no dice. What does work is starting lightdm.service manually over ssh: It takes about 1-4 tries for both gpu-manager and lightdm to successfully launch and bring up both greeters. Reboot, and it fails again. Some kind of race condition due to too lax timing and/or dependencies in the lightdm service file? Something unrelated changed the order and or speed at which systemd executes the service files, i.e. it worked by accident before and now it doesn't? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 Uname: Linux 6.4.12-060412-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Aug 31 03:16:56 2023 InstallationDate: Installed on 2023-08-25 (5 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) 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/2033569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1617620] Re: Autorun files from Removable Media
This bug was fixed in the package gsettings-desktop-schemas - 45~rc-1ubuntu1 --- gsettings-desktop-schemas (45~rc-1ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add ubuntu_lock-on-suspend.patch - Add dark-theme migration script using dh-migrations * Drop Breaks: ukwm because ukwm still runs but fails to build from source for unrelated reasons gsettings-desktop-schemas (45~rc-1) unstable; urgency=medium * New upstream release - media-handling: Don't autostart software by default when media is inserted (LP: #1983778, LP: #1617620) * Add Breaks against packages that used dropped toggle-shaded * Drop obsolete Breaks gsettings-desktop-schemas (44.0-2) unstable; urgency=medium * Update standards version to 4.6.2, no changes needed * Release to unstable -- Jeremy Bícha Thu, 07 Sep 2023 13:24:00 -0400 ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1617620 Title: Autorun files from Removable Media Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Bug description: Ubuntu 16 is still automatically executing software that resides in an external resource (removable media), such as USB or CD. I don't need to tell you how bad this is.. --- You can see the default value that allows to autoplay / autorun files by doing the following steps: 1. In Ubuntu 16.04, go to Settings -> Details. 2. In the left pane choose "Removable Media". 3. On the right pane you'll see "Software", while the value in the drop-down menu is "Run Software". --- A fix suggestion: Instead of "Run Software", the default value should be "Do nothing". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1617620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu5
---
ifupdown (0.8.36+nmu1ubuntu5) mantic; urgency=medium
[ Uwe Kleine-König ]
* Fix if-up.d/resolved hook to properly work with nameservers and search
domains (LP: #1981103)
-- Heitor Alves de Siqueira Wed, 06 Sep 2023
13:23:34 +
** Changed in: ifupdown (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
Fix Released
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983778] Re: Major security issue in Ubuntu Desktop default config - Removable Media
This bug was fixed in the package gsettings-desktop-schemas - 45~rc-1ubuntu1 --- gsettings-desktop-schemas (45~rc-1ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add ubuntu_lock-on-suspend.patch - Add dark-theme migration script using dh-migrations * Drop Breaks: ukwm because ukwm still runs but fails to build from source for unrelated reasons gsettings-desktop-schemas (45~rc-1) unstable; urgency=medium * New upstream release - media-handling: Don't autostart software by default when media is inserted (LP: #1983778, LP: #1617620) * Add Breaks against packages that used dropped toggle-shaded * Drop obsolete Breaks gsettings-desktop-schemas (44.0-2) unstable; urgency=medium * Update standards version to 4.6.2, no changes needed * Release to unstable -- Jeremy Bícha Thu, 07 Sep 2023 13:24:00 -0400 ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1983778 Title: Major security issue in Ubuntu Desktop default config - Removable Media Status in GSettings Desktop Schemas: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Bug description: There is a MAJOR SECURITY VULNERABILITY in Ubuntu Desktop since release 18.04 ! Recently I used Ubuntu 22.04 LTS and noticed that the issue still exist! I don’t know the reason for it, but default values for “Removable Media” are VERY Risky! It will automatically run the software which is attached to the removable media. Why? Why has Ubuntu still didn’t disable that option? The following is the default configuration (the “bad” configuration): https://imgur.com/XXXQlV2 The following is the configuration which Ubuntu should be having (it is the fix to the problem): https://imgur.com/a/0JeM6ve Please change the default configurations for Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1983778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034765] Re: Update Systemd for v254
I checked and on Debian the package is already in testing. -- 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/2034765 Title: Update Systemd for v254 Status in systemd package in Ubuntu: New Bug description: Version 254 of Systemd was released in the end of July. Maybe we should update on Mantic so v254 can be the version for this release instead of keep on 253. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2034765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034765] [NEW] Update Systemd for v254
Public bug reported: Version 254 of Systemd was released in the end of July. Maybe we should update on Mantic so v254 can be the version for this release instead of keep on 253. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2034765 Title: Update Systemd for v254 Status in systemd package in Ubuntu: New Bug description: Version 254 of Systemd was released in the end of July. Maybe we should update on Mantic so v254 can be the version for this release instead of keep on 253. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2034765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034763] Re: Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2
** Package changed: ubuntu => glib2.0 (Ubuntu) ** Also affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Tags added: mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2034763 Title: Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2 Status in glib2.0 package in Ubuntu: New Status in xdg-desktop-portal package in Ubuntu: New Bug description: I use Plasma desktop in Mantic. With the latest versions of glib2.0 and xdg-desktop-portal all Flatpak applications ignore host settings like GTK theme, cursor theme and window controls position. I can get proper appearance only in the following state: > sudo apt list --upgradable Listing... Done libglib2.0-0/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1] libglib2.0-bin/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1] libglib2.0-data/mantic,mantic 2.77.3-1 all [upgradable from: 2.77.1-1] xdg-desktop-portal/mantic 1.17.2-1ubuntu1 amd64 [upgradable from: 1.16.0-3ubuntu1] Upgrading either glib2.0 or xdg-desktop-portal causes the problem, so I don't know exactly which package causes this incompatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2034763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034763] [NEW] Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2
You have been subscribed to a public bug: I use Plasma desktop in Mantic. With the latest versions of glib2.0 and xdg-desktop-portal all Flatpak applications ignore host settings like GTK theme, cursor theme and window controls position. I can get proper appearance only in the following state: > sudo apt list --upgradable Listing... Done libglib2.0-0/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1] libglib2.0-bin/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1] libglib2.0-data/mantic,mantic 2.77.3-1 all [upgradable from: 2.77.1-1] xdg-desktop-portal/mantic 1.17.2-1ubuntu1 amd64 [upgradable from: 1.16.0-3ubuntu1] Upgrading either glib2.0 or xdg-desktop-portal causes the problem, so I don't know exactly which package causes this incompatibility. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2 https://bugs.launchpad.net/bugs/2034763 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
I seem to be having the same trouble as the rest of you. Similar issues and messages were popping up during the attempted install. I am a fairly new user and have no idea how to fix this. If given instructions and a simple line of code I DO know how to open a terminal window and type in commands LOL. Will someone email me when a solution is found? Thanks a ton! -- 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/2032851 Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: Confirmed Bug description: package install error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: apparmor 2.12-4ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 24 02:35:35 2023 DuplicateSignature: package:apparmor:2.12-4ubuntu5.3 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): new apparmor package pre-installation script subprocess returned error exit status 1 ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-08-22 (1 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic root=UUID=c5495aa8-cf2c-4042-a2ea-4533e9343808 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: apparmor Syslog: Aug 24 02:04:25 adminn-Lenovo-V110-15ISK dbus-daemon[4678]: [session uid=1000 pid=4678] AppArmor D-Bus mediation is enabled Aug 24 02:05:26 adminn-Lenovo-V110-15ISK dbus-daemon[856]: [system] AppArmor D-Bus mediation is enabled Aug 24 02:05:31 adminn-Lenovo-V110-15ISK dbus-daemon[1021]: [session uid=124 pid=1021] AppArmor D-Bus mediation is enabled Aug 24 02:06:04 adminn-Lenovo-V110-15ISK dbus-daemon[1506]: [session uid=1000 pid=1506] AppArmor D-Bus mediation is enabled Aug 24 03:39:11 adminn-Lenovo-V110-15ISK dbus-daemon[9963]: [session uid=0 pid=9956] AppArmor D-Bus mediation is enabled Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2032851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
For the record: The different results depending on locale is a "translation" matter. While the default time separator is \u2236, it has been "translated" for e.g. en_GB in Ubuntu into \u003A: https://translations.launchpad.net/ubuntu/mantic/+source/gnome- desktop/+pots/gnome-desktop-3.0/en_GB/24 $ printf '\u2236\n' ∶ $ printf '\u003A\n' : So with the en_GB.UTF-8 locale it displays a regular colon character, which the Ubuntu font can render. (Daniel: I can't explain how you hid the issue by using en_AU.UTF-8, though.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Confirmed Status in language-pack-gnome-en package in Ubuntu: New Status in language-pack-gnome-en-base package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Released Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
This bug was fixed in the package language-selector - 0.224 --- language-selector (0.224) mantic; urgency=medium * data/pkg_depends: - Pull also fcitx5-frontend-qt6 for Chinese (non-GNOME) users. * Prefer Noto Sans Math - Makes that font used instead of DejaVu Sans Mono for rendering the Ratio character in the clock (LP: #2033377). -- Gunnar Hjalmarsson Thu, 07 Sep 2023 20:30:37 +0200 ** Changed in: language-selector (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Confirmed Status in language-pack-gnome-en package in Ubuntu: New Status in language-pack-gnome-en-base package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Released Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
Thanks Gunnar! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Confirmed Status in language-pack-gnome-en package in Ubuntu: New Status in language-pack-gnome-en-base package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Committed Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
Why do they mess with that math symbol in gnome-desktop? Anyway, the issue surfaced because of the font changes I made. Previously DejaVu Sans was used to render the Ratio character, and now, when the fonts-dejavu-core package is not present, DejaVu Sans Mono seems to be used instead. Hence the extra whitespace. I uploaded a language-selector change so it uses Noto Sans Math for rendering Ratio. https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/language- selector/commit/?id=fc7ec106 ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Changed in: language-selector (Ubuntu) Importance: Undecided => Medium ** Changed in: language-selector (Ubuntu) Status: New => Fix Committed ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Confirmed Status in language-pack-gnome-en package in Ubuntu: New Status in language-pack-gnome-en-base package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Committed Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] Re: Create the usbmux user in the preinst script
** Description changed: The installation of this package as part of the upgrade process from - Lunar to Mantic is triggering an issue in Netplan + Lunar to Mantic (it's already present in Desktop images so it's not a + problem there apparently) is triggering an issue in Netplan https://bugs.launchpad.net/netplan/+bug/1999178 This package will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/2034539 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: The installation of this package as part of the upgrade process from Lunar to Mantic (it's already present in Desktop images so it's not a problem there apparently) is triggering an issue in Netplan https://bugs.launchpad.net/netplan/+bug/1999178 This package will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028810] Re: rsync 3.1.3 performance regression
Re-verified with documentation: $ lxc launch ubuntu:focal test-rsync-receiver $ lxc exec test-rsync-receiver bash # apt update && apt dist-upgrade -y # apt install openssh-server rsync -y # passwd ubuntu New password: Retype new password: passwd: password updated successfully # sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config # systemctl restart sshd # exit - Check ip of receiver with lxc list $ lxc list +-+-+--+---+---+---+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | +-+-+--+---+---+---+ | test-rsync-receiver | RUNNING | 10.190.23.243 (eth0) | -- (eth0) | CONTAINER | 0 | +-+-+--+---+---+---+ $ lxc launch ubuntu:focal test-rsync-sender $ lxc exec test-rsync-sender bash # cat
[Touch-packages] [Bug 2017401] Re: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled
Dropping the rls-ff-incoming in favor of adding a task (and one for jammy) so it is out of view until nn cycle. ** Tags removed: rls-mm-incoming ** Tags added: rls-nn-incoming ** Also affects: unattended-upgrades (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Focal) Importance: Undecided Status: New ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2017401 Title: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled Status in unattended-upgrades package in Ubuntu: Confirmed Status in unattended-upgrades source package in Focal: New Status in unattended-upgrades source package in Jammy: New Bug description: Following the resolution for bug #1747499, after a kernel upgrade when Livepatch is enabled, the current behaviour in unattended-upgrades (2.3ubuntu0.2 and later) is not to touch /var/run/reboot-required so as not to confuse users with two separate messages calling for a restart in motd. This functionality is implemented in the script at /etc/kernel/postinst.d/unattended-upgrades. While this works as intended in terms of suppressing an extra message in motd, it defeats the ability of unattended-upgrades to restart automatically with the new kernel, which is reliant on /var/run/reboot-required being present. This is unexpected / unwanted behaviour in scenarios where a) Livepatch is being used to provide fast-response kernel patching; and b) Unattended-Upgrade::Automatic-Reboot is set to true, to enable automatic reboots during a regular maintenance window. In this case, without administrative intervention, the system could never boot into the new kernel even though it would be expected to, leaving Livepatch to do all the heavy lifting indefinitely, and unnecessarily. I believe this counts as a regression caused by the resolution to bug #1747499. It also has the potential to be a security threat if Livepatch doesn't work comprehensively for a particular kernel flaw, and an administrator is reliant on expected behaviour according to unattended-upgrades settings. Potential options for a fix that come to mind: 1. Revert to original behaviour in /etc/kernel/postinst.d/unattended-upgrades, and change the ***System restart required*** message to be less alarming or confusing when the cause is a kernel upgrade that's being patched by Livepatch. 2. Add an extra configuration setting (eg Unattended-Upgrade::Automatic-Reboot-After-Livepatch) that triggers a reboot when it's 'recommended' by Livepatch, not reliant on the presence of /var/run/reboot-required. 3. Add support in /etc/kernel/postinst.d/unattended-upgrades for an extra file somewhere. When present, /var/run/reboot-required is always touched, even if Livepatch is enabled. (This is my first time reporting a bug in this system, and I apologise if I haven't followed the usual descriptive format.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2017401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033949] Re: Does not work with sources in deb822 format
** Tags removed: rls-mm-incoming ** Tags added: foundations-todo -- 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/2033949 Title: Does not work with sources in deb822 format Status in software-properties package in Ubuntu: Confirmed Bug description: On my Mantic I have sources in new deb822 format. Starting software-properties-gtk seems my server is Main server, but from /etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I software-properties-gtk seems unable to change. corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic mantic-updates mantic-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg corrado@corrado-n16-mm-0901:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-gtk 0.99.39 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 2 10:33:12 2023 InstallationDate: Installed on 2023-09-01 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2033949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] Re: Create the usbmux user in the preinst script
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/usbmuxd/+git/usbmuxd/+merge/450906 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/2034539 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: The installation of this package as part of the upgrade process from Lunar to Mantic is triggering an issue in Netplan https://bugs.launchpad.net/netplan/+bug/1999178 This package will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] Re: Create the usbmux user in the preinst script
Running a "do-release-upgrade -d --allow-third-party" with this PPA (set to Mantic) [1] works around the issue when upgrading a clean Lunar to Mantic. [1] - https://launchpad.net/~danilogondolfo/+archive/ubuntu/usbmuxd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/2034539 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: The installation of this package as part of the upgrade process from Lunar to Mantic is triggering an issue in Netplan https://bugs.launchpad.net/netplan/+bug/1999178 This package will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2009498] Re: autopkg test failure
** Changed in: ganeti (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2009498 Title: autopkg test failure Status in ganeti package in Ubuntu: Fix Released Status in procps package in Ubuntu: Fix Released Status in ganeti package in Debian: Fix Released Bug description: pgrep -u '-1'; echo $? used to yield 1 but with procps 4.0.3 it yields 2. Negative uids don't exist in the Linux kernel. Function testRequestUnusedUid() is wrong in assuming that -1 will be considered an unused uid. See Debian bug#1031765: ganeti-testsuite: autopkgtest failure with procps 2:4.0.3-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ganeti/+bug/2009498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] Re: Create the usbmux user in the preinst script
** Description changed: - [placeholder] + The installation of this package as part of the upgrade process from + Lunar to Mantic is triggering an issue in Netplan + https://bugs.launchpad.net/netplan/+bug/1999178 + + This package will install a udev .rules file referring to a user that + will be created only in the final steps of the upgrade process. As + systemd daemon-reload is called a number of times during the process. + The issue is triggered many times and makes the upgrade take way longer + than it should. + + In resume, Netplan is calling udevadm reload from a systemd generator, + it will process .rules files. When it tries to check the users defined + in these files, if they don't exist in /etc/passwd, it will go to + systemd (thanks to our nsswitch.conf). But because we are in the middle + of a daemon-reload, the userdb is not ready yet and the process will + stuck until it times out (for like 2 minutes). + + The workaround would be to create the user sooner. But the problem will + continue to happen if another package does the same thing. + + While this is an issue with Netplan, the proper fix is complicated and + we are working on it https://github.com/canonical/netplan/pull/304 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/2034539 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: The installation of this package as part of the upgrade process from Lunar to Mantic is triggering an issue in Netplan https://bugs.launchpad.net/netplan/+bug/1999178 This package will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
Thanks. The 0.8.41 Debian package contains this fix already (so no
forwarding needed). So uploaded to mantic (included some trailing space
removals).
** Changed in: ifupdown (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 ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
Fix Committed
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922047]
I filed bug 1851258 as a follow-up for potentially rolling out this change to the release channel. Regressions from this change like bug 1849201 will need to be fixed before that happens. -- 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/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: Fix Released Status in GTK+: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted
This bug is awaiting verification that the linux/5.4.0-164.181 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux' to 'verification-done-focal-linux'. If the problem still exists, change the tag 'verification-needed-focal- linux' to 'verification-failed-focal-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux -- 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/1837227 Title: systemd mount units fail during boot, while file system is correctly mounted Status in systemd: New Status in Ubuntu Pro: In Progress Status in Ubuntu Pro 18.04 series: In Progress Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Focal: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] systemd mount units fail during boot, and the system boots into emergency mode [Test Plan] This issue seems to happen randomly, and doesn't seem related to a specific mount unit. We've used a test script with good results during investigation to reproduce similar mount failures in a running system, and have seen a strong correlation between the script failures and the boot time mount failures. The attached 'rep-tmpfs.sh' script should be used to validate that mount points are working correctly under stress. One can run through the different variants as below: # ./rep-tmpfs.sh --variant-0 # ./rep-tmpfs.sh --variant-1 # ./rep-tmpfs.sh --variant-2 # ./rep-tmpfs.sh --variant-3 # ./rep-tmpfs.sh --variant-4 All of these should run successfully without any reported errors. [Where problems could occur] The patches change the way systemd tracks and handles mount points in general, so potential regressions could affect other mount units. We should keep an eye out for any issues with mounting file systems, as well as rapid mount/unmount operations. Successful test runs with the reproducer script should increase reliability in having no new regressions. [Other Info] This has been tackled upstream with several attempts, which have resulted in the final patch from 2022: 01400460ae16 core/mount: adjust deserialized state based on /proc/self/mountinfo For Bionic, systemd requires several dependency patches as below: 6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a new unit cycle 7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the other way round 350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() results 1d086a6e5972 mount: mark an existing "mounting" unit from /proc/self/mountinfo as "just_mounted" Additionally, the kernel also requires the following patches: 28ca0d6d39ab list: introduce list_for_each_continue() 9f6c61f96f2d proc/mounts: add cursor [Original Description] In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode with a failed mount unit (ext4 file system), while the corresponding file system is in fact correctly mounted. It happens roughly once every 1000 reboots. It seems to be related with this bug : https://github.com/systemd/systemd/issues/10872 Is it possible to apply the fix (https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21) in Ubuntu 18.04 ? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028810] Re: rsync 3.1.3 performance regression
Hello Ye, or anyone else affected, Accepted rsync into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/rsync/3.1.3-8ubuntu0.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2028810 Title: rsync 3.1.3 performance regression Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Focal: Fix Committed Bug description: [Impact] Recent necessary security fixes to rsync have caused a slow down in transfer speeds due to additional authentication. In more recent versions of rsync this can be mitigated when the environment is trusted with the --trust-sender flag. In order to accomidate this use case, the flag should be backported to focal too. [Test Plan] $ lxc launch ubuntu:focal test-rsync-receiver $ lxc exec test-rsync-receiver bash # apt update && apt dist-upgrade -y # apt install openssh-server rsync -y # passwd ubuntu - set password for user # exit - Check ip of receiver with lxc list $ lxc list $ lxc launch ubuntu:focal test-rsync-sender $ lxc exec test-rsync-sender bash # apt update && apt dist-upgrade -y # apt install rsync -y - Create a random file to send over # dd if=/dev/urandom of=randomfile.bin bs=1M count=1000 - Send without --trust-sender # rsync -av randomfile.bin ubuntu@:~/file1.bin - Send with --trust-sender # rsync -av --trust-sender randomfile.bin ubuntu@:~/file2.bin With the fix in place, --trust-sender is a valid argument and the transfer is notably faster as reported back by rsync. [Where problems could occur] Since this change adds a new feature in the form of an input flag, problems could occour when using it. This could include issues from skipping security checks between the sending and receiving machine. Another possible problem would be issues with command line input parsing due to the additional valid argument. [Other Info] The --trust-sender option is already available in Jammy and later [Original Description] OS: Ubuntu 20.04 Focal Package: rsync 3.1.3-8ubuntu0.5 rsync's performance was regressed by ~7x amount after some security patch (debian/patches/CVE-2022-29154-*) was applied to the package, and introduced a list of filters that iterate on every file being transferred. We think that was where the performance regression came from. A Jammy version of the package (3.2.5) introduced a new flag "--trust- sender" that allowed user to avoid the expensive client-side filtering introduced by those security patches. After pulling this change (https://github.com/WayneD/rsync/commit/cff8f044776c5143a5b270969d4bb0f1fea8b017) from rsync ourselves and applied it to the Focal version, the performance regression went away. The patch we used to backport our Focal rsync is attached in this thread. Can you please backport it too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2028810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2014996] Re: [82SJ, Realtek ALC257, Mic, Internal] Recording problem
Try to install pulse-audio and go to record tab. That worked for me -- 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/2014996 Title: [82SJ, Realtek ALC257, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: my laptop built-in micro do not work in ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minhdinh 1684 F pulseaudio /dev/snd/controlC1: minhdinh 1684 F pulseaudio /dev/snd/controlC0: minhdinh 1684 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 2 16:56:32 2023 InstallationDate: Installed on 2023-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic_1 failed Symptom_Type: None of the above Title: [82SJ, Realtek ALC257, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: J8CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76501 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 Pro 14ARH7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrJ8CN27WW:bd06/16/2022:br1.27:efr1.27:svnLENOVO:pn82SJ:pvrIdeaPad5Pro14ARH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76501WIN:cvnLENOVO:ct10:cvrIdeaPad5Pro14ARH7:skuLENOVO_MT_82SJ_BU_idea_FM_IdeaPad5Pro14ARH7: dmi.product.family: IdeaPad 5 Pro 14ARH7 dmi.product.name: 82SJ dmi.product.sku: LENOVO_MT_82SJ_BU_idea_FM_IdeaPad 5 Pro 14ARH7 dmi.product.version: IdeaPad 5 Pro 14ARH7 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-04-02T13:11:37.605706 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2014996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
