[Touch-packages] [Bug 1959103] Re: polkitd crashes with segfault with specific config file
I also have this bug on Ubuntu 22.04 following this guide, aside from setting
it to my user.
https://code.luasoftware.com/tutorials/linux/ubuntu-prompt-system-policy-prevents-modification-of-network-settings-for-all-users
[Let all users modify system settings for network]
Identity=unix-user:ryan
Action=org.freedesktop.NetworkManager.settings.modify.system
ResultAny=no
ResultInactive=no
ResultActive=yes
Version: libpolkit-agent-1-0/jammy,now 0.105-33 amd64
[installed,automatic]
--
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/1959103
Title:
polkitd crashes with segfault with specific config file
Status in policykit-1 package in Ubuntu:
Confirmed
Bug description:
The following config file in
`/etc/polkit-1/localauthority.conf.d/02-allow-colord.conf` can cause a
segfault in `polkitd`.
```
polkit.addRule(function(action, subject) {
if ((action.id == "org.freedesktop.color-manager.create-device" ||
action.id == "org.freedesktop.color-manager.create-profile" ||
action.id == "org.freedesktop.color-manager.delete-device" ||
action.id == "org.freedesktop.color-manager.delete-profile" ||
action.id == "org.freedesktop.color-manager.modify-device" ||
action.id == "org.freedesktop.color-manager.modify-profile") &&
subject.isInGroup("{group}")) {
return polkit.Result.YES;
}
});
```
1. As normal user: `systemctl restart cron.service`
2. Error message `Failed to restart cron.service: Message recipient
disconnected from message bus without replying`
3. `dmesg` reports:
```
58.003893] polkitd[963]: segfault at 8 ip 558a96789856 sp
7ffda31e45f0 error 4 in polkitd[558a96784000+f000]
[ 58.003899] Code: 50 c7 ff ff 4d 89 e5 48 89 44 24 08 eb 53 66 0f 1f 44 00
00 48 8b 44 24 10 48 89 e9 be 10 00 00 00 31 ff 48 8d 15 0b af 00 00 <4c> 8b 40
08 31 c0 e8 af cb ff ff 48 8b 7c 24 10 e8 65 c9 ff ff 4c
``
If you remove the 02-allow-colord.conf the segfault goes away and you
are normally prompted for a password. You can also find a couple of
references in the internet, e.g http://c-nergy.be/blog/?p=12043.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1959103/+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 2033934] Re: Al abrir chrome
*** This bug is a duplicate of bug 2029049 *** https://bugs.launchpad.net/bugs/2029049 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2029049, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2033934/+attachment/5697245/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2033934/+attachment/5697247/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2033934/+attachment/5697248/+files/ProcStatus.txt ** This bug has been marked a duplicate of bug 2029049 NetworkManager crashed with SIGABRT in g_mutex_clear() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2033934 Title: Al abrir chrome Status in network-manager package in Ubuntu: New Bug description: REproduciendo vidéos en youtube ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.0-1ubuntu2 Uname: Linux 6.3.0-7-generic x86_64 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 2 00:36:16 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1693386590 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2033934/+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
Added an additional merge request containing man and help docs https://code.launchpad.net/~lvoytek/ubuntu/+source/rsync/+git/rsync/+merge/450497 -- 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 2028810] Re: rsync 3.1.3 performance regression
** Merge proposal linked: https://code.launchpad.net/~lvoytek/ubuntu/+source/rsync/+git/rsync/+merge/450497 -- 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 2033933] Re: Fallo cuando instalaba neofetch
*** This bug is a duplicate of bug 2029049 *** https://bugs.launchpad.net/bugs/2029049 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2029049, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Package changed: ubuntu => network-manager (Ubuntu) ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2033933/+attachment/5697239/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2033933/+attachment/5697241/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2033933/+attachment/5697242/+files/ProcStatus.txt ** This bug has been marked a duplicate of bug 2029049 NetworkManager crashed with SIGABRT in g_mutex_clear() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2033933 Title: Fallo cuando instalaba neofetch Status in network-manager package in Ubuntu: New Bug description: Mensaje de error al instalar neofetch desde la terminal ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.0-1ubuntu2 Uname: Linux 6.3.0-7-generic x86_64 Architecture: amd64 Date: Fri Sep 1 22:32:16 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1693386590 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2033933/+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 2033930] [NEW] unable to remap keybinding Left after upgrading to ubuntu 23.10
Public bug reported: Since upgrading to 23.10 my custom keybindings using Super, Super are not working (they keep using the default settings). For example: gsettings set org.gnome.desktop.wm.keybindings switch-windows "['Left']" Even when this is set the keybinding keeps doing the default behavior "View split on left" However using other keybindings works ok, e.g: gsettings set org.gnome.desktop.wm.keybindings switch-windows "['Left']" gsettings set org.gnome.desktop.wm.keybindings switch-windows "['']" both works as intended, only Left and Right are not working. Same behaviour using the graphical client to change the settings. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libglib2.0-bin 2.77.2-1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 23:35:11 2023 InstallationDate: Installed on 2023-08-11 (21 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: glib2.0 UpgradeStatus: Upgraded to mantic on 2023-08-30 (2 days ago) ** Affects: glib2.0 (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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2033930 Title: unable to remap keybinding Left after upgrading to ubuntu 23.10 Status in glib2.0 package in Ubuntu: New Bug description: Since upgrading to 23.10 my custom keybindings using Super, Super are not working (they keep using the default settings). For example: gsettings set org.gnome.desktop.wm.keybindings switch-windows "['Left']" Even when this is set the keybinding keeps doing the default behavior "View split on left" However using other keybindings works ok, e.g: gsettings set org.gnome.desktop.wm.keybindings switch-windows "['Left']" gsettings set org.gnome.desktop.wm.keybindings switch-windows "['']" both works as intended, only Left and Right are not working. Same behaviour using the graphical client to change the settings. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libglib2.0-bin 2.77.2-1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 23:35:11 2023 InstallationDate: Installed on 2023-08-11 (21 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: glib2.0 UpgradeStatus: Upgraded to mantic on 2023-08-30 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2033930/+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 1987336] Re: Multiple vulnerabilities in Focal
** Description changed: The version in Ubuntu 20.04 is vulnerable to CVE-2020-13962, - CVE-2020-17507 and CVE-2022-25255. + CVE-2020-17507, CVE-2022-25255, CVE-2023-24607, CVE-2023-32762, + CVE-2023-32763, CVE-2023-33285, CVE-2023-37369 and CVE-2023-38197. - I will provide a debdiff in this week. + The versions in Ubuntu 22.04 are vulnerable to CVE-2023-24607, + CVE-2023-32762 , CVE-2023-32763, CVE-2023-33285, CVE-2023-37369 and + CVE-2023-38197. + + I will provide debdiffs until 3 September. ** Also affects: qt6-base (Ubuntu) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-24607 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32762 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32763 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-33285 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-37369 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-38197 ** Summary changed: - Multiple vulnerabilities in Focal + Multiple vulnerabilities in Focal and Jammy ** Changed in: qt6-base (Ubuntu) Status: New => Confirmed ** Changed in: qt6-base (Ubuntu) Assignee: (unassigned) => Luís Infante da Câmara (luis220413) -- 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/1987336 Title: Multiple vulnerabilities in Focal and Jammy Status in qt6-base package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: The version in Ubuntu 20.04 is vulnerable to CVE-2020-13962, CVE-2020-17507, CVE-2022-25255, CVE-2023-24607, CVE-2023-32762, CVE-2023-32763, CVE-2023-33285, CVE-2023-37369 and CVE-2023-38197. The versions in Ubuntu 22.04 are vulnerable to CVE-2023-24607, CVE-2023-32762 , CVE-2023-32763, CVE-2023-33285, CVE-2023-37369 and CVE-2023-38197. I will provide debdiffs until 3 September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1987336/+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 1987336] Re: Multiple vulnerabilities in Focal
** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) => Luís Infante da Câmara (luis220413) -- 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/1987336 Title: Multiple vulnerabilities in Focal Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: The version in Ubuntu 20.04 is vulnerable to CVE-2020-13962, CVE-2020-17507 and CVE-2022-25255. I will provide a debdiff in this week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1987336/+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 2002819] Re: dh-python: Deps guarded by (python3 << 3.X) break python-3.(X-1) use
** Changed in: dh-python (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2002819 Title: dh-python: Deps guarded by (python3 << 3.X) break python-3.(X-1) use Status in dh-python package in Ubuntu: New Status in dh-python package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1028603: Package: dh-python Version: 5.20221001 Severity: normal X-Debbugs-Cc: scho...@ubuntu.com For instance, pylint has "tomli>=1.1.0;python_version<'3.11'" in its pyproject.toml, which is translated as "python3-tomli (>= 1.1.0) | python3 (>= 3.11)". This means that if we have python == 3.11 but still have python3.10 in the archive, any code that iterates over all supported archive risks failing simply due to the tomli module missing. This is currently happening in the distro-info autopkgtests for the python3-defaults migration from unstable to testing (and also in Ubuntu). I'll probably be adding tomli as a test dependency in Ubuntu as a stopgap, but I figured someone might think of a better long-term solution to the issue. -- System Information: Debian Release: bookworm/sid APT prefers kinetic-updates APT policy: (500, 'kinetic-updates'), (500, 'kinetic-security'), (500, 'kinetic'), (400, 'kinetic-proposed'), (100, 'kinetic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-29-generic (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dh-python depends on: ii python33.10.6-1 ii python3-distutils 3.10.7-1 dh-python recommends no packages. Versions of packages dh-python suggests: ii dpkg-dev 1.21.9ubuntu1 pn flit ii libdpkg-perl 1.21.9ubuntu1 pn python3-build pn python3-installer ii python3-tomli 2.0.1-1 -- no debconf information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2002819/+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 2033923] Re: latest xububtu jammy daily isos fail to install on asus, lenovo & msi
the zfs dependency in question is systemd-udev-settle. Sep 1 17:49:20 xubuntu udevadm[1064]: systemd-udev-settle.service is deprecated. Please fix zfs-load-module.service, zfs-import-cache.service not to pull it in. (heh) Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: start operation timed out. Terminating. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: State 'stop-sigterm' timed out. Killing. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Killing process 1064 (udevadm) with signal SIGKILL. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Processes still around after SIGKILL. Ignoring. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: State 'final-sigterm' timed out. Killing. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Killing process 1064 (udevadm) with signal SIGKILL. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Processes still around after final SIGKILL. Entering failed mode. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Failed with result 'timeout'. Opening tasks on systemd and zfsutils-linux, since these packages need to fight it out wrt the "deprecation". And opening a task on the kernel, because a udevadm process that doesn't die with SIGKILL means it's hung in the kernel. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-cdimage Status: New => Invalid ** Summary changed: - latest xububtu jammy daily isos fail to install on asus, lenovo & msi + latest xubuntu jammy daily isos fail to install on asus, lenovo & msi -- 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/2033923 Title: latest xubuntu jammy daily isos fail to install on asus, lenovo & msi Status in Ubuntu CD Images: Invalid Status in linux-hwe-6.2 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: Hi, I downloaded the latest xubuntu jammy images 20230901 (and previous ones, verified them) On a Mac all went well with a fresh install, however on a Lenovo, Asus, MSI the installer fails... udev startup job hangs and is restarted several times with 3 minutes increments I get several different errors: Dependency failed for Install ZFS kernel module Dependency failed for Import ZFS,... Failing start job without limit! Load Kernel Module efi_pstore Thank you for sorting this out Kind regards Otto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2033923/+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 513732] Re: [arm] needs porting to thumb2
** Changed in: gmp (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gmp in Ubuntu. https://bugs.launchpad.net/bugs/513732 Title: [arm] needs porting to thumb2 Status in gmp package in Ubuntu: Fix Released Status in gmp source package in Lucid: Fix Released Status in gmp package in Debian: Fix Released Bug description: https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList "uses mov; also "add" assumes arm" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gmp/+bug/513732/+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 2029465] Re: autopkgtest fails due to netcat-openbsd prints connection info on stderr
** Changed in: davmail (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/2029465 Title: autopkgtest fails due to netcat-openbsd prints connection info on stderr Status in davmail package in Ubuntu: Fix Released Status in ganglia package in Ubuntu: New Status in netcat-openbsd package in Ubuntu: New Status in davmail package in Debian: Fix Released Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/d/davmail/20230801_081825_da2e8@/log.gz 260s autopkgtest [08:18:03]: test binary-starts: [--- 261s 2023-08-01 08:18:03,408 DEBUG [main] davmail.DavGateway - Start DavMail in server mode 261s 2023-08-01 08:18:03,443 INFO [main] davmail - DavMail Gateway 6.1.0-trunk listening on SMTP port 1025 POP port 1110 IMAP port 1143 CALDAV port 1080 LDAP port 1389 270s Connection to localhost (::1) 1025 port [tcp/*] succeeded! 270s 2023-08-01 08:18:13,251 DEBUG [davmail.smtp.SmtpServer] davmail - Connection from /0:0:0:0:0:0:0:1 on port 1025 270s 2023-08-01 08:18:13,253 INFO [davmail.smtp.SmtpServer] davmail.connection - CONNECT - 0:0:0:0:0:0:0:1:39534 270s 2023-08-01 08:18:13,254 DEBUG [Shutdown] davmail - Stopping DavMail gateway 270s 2023-08-01 08:18:13,256 INFO [davmail.smtp.SmtpServer] davmail.connection - DISCONNECT - 0:0:0:0:0:0:0:1:39534 271s autopkgtest [08:18:14]: test binary-starts: ---] 271s autopkgtest [08:18:14]: test binary-starts: - - - - - - - - - - results - - - - - - - - - - 271s binary-startsFAIL stderr: Connection to localhost (::1) 1025 port [tcp/*] succeeded! 271s autopkgtest [08:18:14]: test binary-starts: - - - - - - - - - - stderr - - - - - - - - - - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/davmail/+bug/2029465/+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 2033560] Re: package ufw 0.36.1-4ubuntu0.1 failed to install/upgrade: o subprocesso instalado, do pacote ufw, o script post-installation retornou erro do status de saída 10
The DpkgHistoryLog.txt has lots of entries that aren't ufw specific: Start-Date: 2023-08-16 18:22:34 Commandline: aptdaemon role='role-commit-packages' sender=':1.134' Upgrade: libgpgmepp6:amd64 (1.16.0-1.2ubuntu4, 1.16.0-1.2ubuntu4.1), libgl1-amber-dri:amd64 (21.3.7-0ubuntu1, 21.3.9-0ubuntu1~22.04.1), libglx-mesa0:amd64 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), libglx-mesa0:i386 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), python3-distupgrade:amd64 (1:22.04.16, 1:22.04.17), language-pack-en-base:amd64 (1:22.04+20230209, 1:22.04+20230801), libgtk-4-common:amd64 (4.6.6+ds-0ubuntu1, 4.6.9+ds-0ubuntu0.22.04.1), libunwind8:amd64 (1.3.2-2build2, 1.3.2-2build2.1), libldap-common:amd64 (2.5.15+dfsg-0ubuntu0.22.04.1, 2.5.16+dfsg-0ubuntu0.22.04.1), ufw:amd64 (0.36.1-4build1, 0.36.1-4ubuntu0.1), libgbm1:amd64 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), libgbm1:i386 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.16, 1:22.04.17), libmutter-10-0:amd64 (42.9-0ubuntu1, 42.9-0ubuntu4), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.2, 2:4.15.13+dfsg-0ubuntu1.3), language-pack-en:amd64 (1:22.04+20230209, 1:22.04+ 20230801), language-pack-pt:amd64 (1:22.04+20230209, 1:22.04+20230801), language-pack-gnome-en-base:amd64 (1:22.04+20230209, 1:22.04+20230801), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.2, 2:4.15.13+dfsg-0ubuntu1.3), libxatracker2:amd64 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), gir1.2-gtk-4.0:amd64 (4.6.6+ds-0ubuntu1, 4.6.9+ds-0ubuntu0.22.04.1), mutter-common:amd64 (42.9-0ubuntu1, 42.9-0ubuntu4), python-apt-common:amd64 (2.4.0ubuntu1, 2.4.0ubuntu2), libgpgme11:amd64 (1.16.0-1.2ubuntu4, 1.16.0-1.2ubuntu4.1), language-pack-pt-base:amd64 (1:22.04+20230209, 1:22.04+20230801), libldap-2.5-0:amd64 (2.5.15+dfsg-0ubuntu0.22.04.1, 2.5.16+dfsg-0ubuntu0.22.04.1), mesa-va-drivers:i386 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), libgl1-mesa-dri:amd64 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), libgl1-mesa-dri:i386 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), terraform:amd64 (1.5.4-1, 1.5.5-1), gir1.2-mutter-10:amd64 (42.9-0ubuntu1, 42.9-0ubuntu4), mesa-vulkan-drivers:amd64 (22.2 .5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), mesa-vulkan-drivers:i386 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), base-files:amd64 (12ubuntu4.3, 12ubuntu4.4), python3-apt:amd64 (2.4.0ubuntu1, 2.4.0ubuntu2), python3-distro-info:amd64 (1.1build1, 1.1ubuntu0.1), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.14, 20220329.git681281e4-0ubuntu3.17), language-pack-gnome-pt-base:amd64 (1:22.04+20230209, 1:22.04+20230801), distro-info:amd64 (1.1build1, 1.1ubuntu0.1), libglapi-mesa:amd64 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), libglapi-mesa:i386 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), libgtk-4-1:amd64 (4.6.6+ds-0ubuntu1, 4.6.9+ds-0ubuntu0.22.04.1), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.2, 2:4.15.13+dfsg-0ubuntu1.3), language-pack-gnome-en:amd64 (1:22.04+20230209, 1:22.04+20230801), language-pack-gnome-pt:amd64 (1:22.04+20230209, 1:22.04+20230801), thermald:amd64 (2.4.9-1ubuntu0.2, 2.4.9-1ubuntu0.3), libegl-mesa0:amd64 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04. 1), libegl-mesa0:i386 (22.2.5-0ubuntu0.1~22.04.3, 23.0.4-0ubuntu1~22.04.1), libgtk-4-bin:amd64 (4.6.6+ds-0ubuntu1, 4.6.9+ds-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.16, 1:22.04.17) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2023-08-16 18:25:33 Start-Date: 2023-08-18 17:51:20 Commandline: /usr/bin/unattended-upgrade Upgrade: ghostscript-x:amd64 (9.55.0~dfsg1-0ubuntu5.3, 9.55.0~dfsg1-0ubuntu5.4), libgs9-common:amd64 (9.55.0~dfsg1-0ubuntu5.3, 9.55.0~dfsg1-0ubuntu5.4), ghostscript:amd64 (9.55.0~dfsg1-0ubuntu5.3, 9.55.0~dfsg1-0ubuntu5.4), libgs9:amd64 (9.55.0~dfsg1-0ubuntu5.3, 9.55.0~dfsg1-0ubuntu5.4) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2023-08-18 17:51:22 Start-Date: 2023-08-21 18:14:13 Commandline: apt-get install -y gnupg software-properties-common Requested-By: anderson (1000) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2023-08-21 18:14:14 Start-Date: 2023-08-21 18:23:11 Commandline: apt install terraform Requested-By: anderson (1000) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2023-08-21 18:23:12 Start-Date: 2023-08-21 18:24:55 Commandline: apt-get -f install Requested-By: anderson (1000) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2023-08-21 18:24:55 Start-Date: 2023-08-21 18:30:10 Commandline: apt -f install Requested-By: anderson (1000) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2023-08-21 18:30:10 Start-Date: 2023-08-21 18:38:25 Commandline: aptdaemon role='role-commit-packages' sender=':1.233' Upgrade: initramfs-tools-core:amd64 (0.140ubuntu13.2, 0.140ubuntu13.4),
[Touch-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
I've builtt a test kernel with the above patch: https://kernel.ubuntu.com/~juergh/lp2031352/ Can someone give it a try, please? Note that the kernel is not signed so you need to disable SecureBoot to be able to boot it. Install linux- image-unsigned, linux-modules and maybe linux-modules-extra. -- 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/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Lunar) ** No longer affects: linux-hwe-6.2 (Ubuntu Lunar) ** Changed in: linux (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
Without digging too deep, maybe this: https://lore.kernel.org/lkml/cacavsv6-aj4ehg7pnuwgsncn0cyro8gwd3nr8pu32a-wxso...@mail.gmail.com/T/ -- 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/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Bug description: After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen (nouveau driver crash)
** Summary changed: - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen + Ubuntu 22.04.3 LTS stuck on power-off/reboot screen (nouveau driver crash) ** Summary changed: - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen (nouveau driver crash) + Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen -- 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/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Bug description: After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
-- 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/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Bug description: After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
@steffel et al. I believe there are two different problems here. 1) A generic reboot/suspend/halt issue. When powering off or suspending, the machine doesn't fully turn off. The fan is still spinning and it can only be revived by pulling the plug. This is what this bug is about. 2) A similarly looking problem but caused (?) by a nouveau issue as seen in comment #18. I think this is a different issues. Please open a new ticket for that. -- 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/2031352 Title: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Bug description: After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2033747] Re: /usr/include/aarch64-linux-gnu/bits/math-vector.h:30: syntax error, unexpected identifier, expecting ',' or '; ' in 'typedef __Float32x4_t __f32x4_t; ' at '__f32x4_t
Possibly related to LP: #2032624 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/2033747 Title: /usr/include/aarch64-linux-gnu/bits/math-vector.h:30: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __Float32x4_t __f32x4_t;' at '__f32x4_t' Status in glibc package in Ubuntu: New Status in gobject-introspection package in Ubuntu: New Bug description: Building on Raspberry Pi mantic, these messages keep repeating: /usr/include/aarch64-linux-gnu/bits/math-vector.h:30: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __Float32x4_t __f32x4_t;' at '__f32x4_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:31: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __Float64x2_t __f64x2_t;' at '__f64x2_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:40: syntax error, unexpected identifier, expecting ',' or ';' in '# 40 "/usr/include/aarch64-linux-gnu/bits/math-vector.h" 3 4' at '__sv_f32_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:41: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __SVFloat64_t __sv_f64_t;' at '__sv_f64_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:42: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __SVBool_t __sv_bool_t;' at '__sv_bool_t' ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libc6-dev 2.38-1ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.27.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri Sep 1 15:38:51 2023 SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2033747/+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
** Description changed: [Impact] * User of openssh reported an issue that affects Lunar and Jammy. * This crash is caused by the wrong pointer manipulation in the if statement. The fix is to change the code to check if the value pointed to by the pointer 'charptr' is NULL. [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. -- 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: In Progress Status in openssh source package in Lunar: In Progress Status in openssh source package in Mantic: Fix Released Bug description: [Impact] * User of openssh reported an issue that affects Lunar and Jammy. * This crash is caused by the wrong pointer manipulation in the if statement. The fix is to change the code to check if the value pointed to by the pointer 'charptr' is NULL. [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
[Touch-packages] [Bug 2031942] Re: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set
** Description changed: [Impact] * User of openssh reported an issue that affects Lunar and Jammy. * This crash is caused by the wrong pointer manipulation in the if statement. The fix is to change the code to check if the value pointed to by the pointer 'charptr' is NULL. [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 + 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 + # 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 is 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. ** Description changed: [Impact] * User of openssh reported an issue that affects Lunar and Jammy. * This crash is caused by the wrong pointer manipulation in the if statement. The fix is to change the code to check if the value pointed to by the pointer 'charptr' is NULL. [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
[Touch-packages] [Bug 2031942] Re: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set
** Description changed: [Impact] * User of openssh reported an issue that affects Lunar and Jammy. * This crash is caused by the wrong pointer manipulation in the if statement. The fix is to change the code to check if the value pointed to by the pointer 'charptr' is NULL. [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 + # 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: + 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: + 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: + 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 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 is 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. ** Description changed: [Impact] * User of openssh reported an issue that affects Lunar and Jammy. * This crash is caused by the wrong pointer manipulation in the if statement. The fix is to change the code to check if the value pointed to by the pointer 'charptr' is NULL. [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 + Go to the /etc/ssh/sshd_config Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys
[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
This bug was fixed in the package systemd - 249.11-0ubuntu3.6
---
systemd (249.11-0ubuntu3.6) jammy; urgency=medium
* Deny-list TEST-58-REPART on ppc64el (LP: #1988994) cheap essay
https://trustanalytica.com/online/top-cheap-essay-writing-services
File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch
Installed 249.11-0ubuntu3.4
Candidate same
version tables has entries:
249.11-ubuntu3.4 500
249.11-ubuntu3
--
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/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Invalid
Status in systemd source package in Jammy:
Fix Released
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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
** Description changed: [Impact] * User of openssh reported an issue that affects Lunar and Jammy. * This crash is caused by the wrong pointer manipulation in the if statement. The fix is to change the code to check if the value pointed to by the pointer 'charptr' is NULL. [Test Plan] - Launch container: + 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 using ‘cd’ command and from there create 2 more dirs that reflect users: + Go to that directory: + # cd reproducer + + Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser - Go to the keyonlyuser and inside: + Go to the keyonlyuser: + # cd keyonlyuser + + Do: # ssh-keygen -t ed25519 -f key - Go to the certuser and inside: + 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 + #!/bin/sh + if [ "$1" = "otheruser" ]; then echo certuser fi - - Exit from the file and set the permission bits: - # chmod 755 authorized_principals - Stay in the same directory and create a user called otheruser: + 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 - Go back to the reproducer/ directory and create a new script called authorized_keys: - # nano authorized_keys - - Add inside: - #!/bin/sh - if [ "$1" = "keyonlyuser" ]; then + Create a script‘/root/reproducer/authorized_keys’ with permissions 755 as follows: + #!/bin/sh + if [ "$1" = "keyonlyuser" ]; then echo fi - - Exit from the file and set permission bits: - # chmod 755 authorized_keys Go to the etc/ssh/sshd_config Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u - AuthorizedKeysCommandUser root + 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 is 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. -- 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: In Progress Status in openssh source package in Lunar: In Progress Status in openssh source package in Mantic: Fix Released Bug description: [Impact] * User of openssh reported an issue that affects Lunar and Jammy. * This crash is caused by the wrong pointer manipulation in the if statement. The fix is to change the code to check if the value pointed to by the pointer 'charptr' is NULL. [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
[Touch-packages] [Bug 2033663] Re: iptables fails to parse "-i +" correctly
OK, great finding, when you file a bug on netfilter bugzilla report the link here, thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2033663 Title: iptables fails to parse "-i +" correctly Status in iptables package in Ubuntu: New Status in iptables-persistent package in Ubuntu: New Bug description: I recently started to use Ubuntu 22.04 LTS on a server and created a simple ipables firewall for it. (For Ubuntu 20.04 that I have used before, the below seems fine.) lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 # apt-cache policy iptables-persistent iptables-persistent: Installed: 1.0.16 Candidate: 1.0.16 Version table: *** 1.0.16 500 500 http://se.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status # apt-cache policy iptables iptables: Installed: 1.8.7-1ubuntu5.1 Candidate: 1.8.7-1ubuntu5.1 Version table: *** 1.8.7-1ubuntu5.1 500 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.8.7-1ubuntu5 500 500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages -- ISSUE: If I enter a simple iptables rule that uses the "-i +" input interface wildcard thing in it, but note that I don't give any interface namestring "prefix" before the "+" - for example: iptables -A INPUT -i + -d 192.168.1.10 -j DROP iptables -A INPUT -i + -d 192.168.1.11 -j DROP iptables -A INPUT -i + -d 192.168.1.12 -j DROP Then printouts of both iptables-save and iptables -L -n -v will show weird non-ascii/non-printable characters where the interfaces are supposed to be printed! The result for my rule example above shows as: -A INPUT -d 192.168.80.10/32 -i À¨P + -j DROP -A INPUT -d 192.168.80.11/32 -i À¨P�+ -j DROP -A INPUT -d 192.168.80.12/32 -i À¨P + -j DROP (The garbage chars are in hex \c0\a8\50\0a, \c0\a8\50\0b, \c0\a8\50\0c respectively. Note the \0a newline char breaking up the printout into two lines for the first rule.) The garbage characters makes "iptables-save > /etc/iptables/rules.v4" followed up with "iptables-restore < /etc/iptables/rules.v4" to fail! I discovered that if the rule also includes some "protocol" constraints like "-p tcp -m tcp --dport 123" then iptables parses/prints the rule seemingly ok, but for "simpler" rules iptables gets confused. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2033663/+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 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=2044981.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2022-01-25T12:22:21+00:00 rsable wrote:
Description of problem:
Autofs mounts with --ghost or browse_mode=yes enabled, triggers a mount
or shows error "ls: cannot access '': No such file or directory"
when ls -l is run
Either errors are seen for mount points which we know are inaccessible for this
client or
a mount is triggered for accessible mounts.
Version-Release number of selected component (if applicable):
autofs-5.1.4-74.el8.x86_64
coreutils-8.30-12.el8.x86_64
(however, I am starting the bug with autofs as affected component as
discussed with Ian)
How reproducible:
Always
Steps to Reproduce:
1. Upgrade to RHEL 8.5 (which should have autofs-5.1.4-74.el8.x86_64 and
coreutils-8.30-12.el8.x86_64)
2. Create an autofs map :
~~~
[root@rsablerhel85 mnt2]# grep -i mnt /etc/auto.master
/mnt2 /etc/auto.indirect
timeout=600,bg,tcp,hard,vers=3,rsize=32768,wsize=32768,timeo=600,retrans=6
[root@rsablerhel85 mnt2]# cat /etc/auto.indirect
testshare rsable76server:/testshare < testshare is a valid
export from server
testshare2 rsable76server:/testshare2 < testshare2 is not
available to this client or could be a bogus entry
~~~
3. Either use --ghost in auto.master as an option or set browse_mode=yes :
~~~
[root@rsablerhel85 mnt2]# grep -i browse /etc/autofs.conf
# browse_mode - maps are browsable by default.
browse_mode = yes
~~~
4. Cd to /mnt2 and run ls -l / ll.
Note : this issue occurs irrespective of direct or indirect maps.
Actual results:
Mount is triggered and ll throws ENOENT for testshare2
~~~
[root@rsablerhel85 mnt2]# ll
ls: cannot access 'testshare2': No such file or directory < Error
total 0
drwxrwxrwx. 3 1000 1000 15 Jan 17 12:08 testshare < mount is
triggerd for testshare
d?? ? ?? ?? testshare2< Path we
know that is inaccessible throws an error
[root@rsablerhel85 mnt2]# mount | grep -i test
rsable76server:/testshare on /mnt2/testshare type nfs
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=6,sec=sys,mountaddr=192.168.122.58,mountvers=3,mountport=20048,mountproto=tcp,local_lock=none,addr=192.168.122.58)
~~~
Expected results:
Mount should not be trigger and error "ls: cannot access 'testshare2': No such
file or directory"
should not be seen.
Additional info:
I think the issue is with a behavior change in coreutils-common-8.30-12.el8.
Reverting back to coreutils-common-8.30-8.el8 this issue goes away :
~~~
[root@rsablerhel85 mnt2]# ll
ls: cannot access 'testshare2': No such file or directory
total 0
drwxrwxrwx. 3 1000 1000 15 Jan 17 12:08 testshare
d?? ? ?? ?? testshare2
[root@rsablerhel85 mnt2]# dnf downgrade coreutils-8.30-8.el8.x86_64
Downgraded:
coreutils-8.30-8.el8.x86_64
coreutils-common-8.30-8.el8.x86_64
Complete!
[root@rsablerhel85 mnt2]# ll
total 0
drwxrwxrwx. 3 1000 1000 15 Jan 17 12:08 testshare
drwxr-xr-x. 2 root root 0 Jan 21 11:47 testshare2
~~~
I can see that coreutils-common-8.30-12.el8 calls statx while
coreutils-common-8.30-8.el8 calls lstat :
~~~
coreutils-8.30-12
3181 12:02:13.828462 getdents64(3, [{d_ino=27279, d_off=1, d_reclen=24,
d_type=DT_DIR, d_name="."}, {d_ino=27279, d_off=2, d_reclen=24, d_type=DT_DIR,
d_name=".."}, {d_ino=27281, d_off=3, d_reclen=32, d_type=DT_DIR,
d_name="testshare"}, {d_ino=27280, d_off=4, d_reclen=32, d_type=DT_DIR,
d_name="testshare2"}], 32768) = 112 <0.18>
3181 12:02:14.033318 statx(AT_FDCWD, "testshare2",
AT_STATX_SYNC_AS_STAT|AT_SYMLINK_NOFOLLOW,
STATX_MODE|STATX_NLINK|STATX_UID|STATX_GID|STATX_MTIME|STATX_SIZE,
0x7ffc0d6f1c60) = -1 ENOENT (No such file or directory) <0.035781>
~~~
~~~
coreutils-8.30-8
2854 12:01:11.302926 getdents64(3, [{d_ino=27279, d_off=1, d_reclen=24,
d_type=DT_DIR, d_name="."}, {d_ino=27279, d_off=2, d_reclen=24, d_type=DT_DIR,
d_name=".."}, {d_ino=27281, d_off=3, d_reclen=32, d_type=DT_DIR,
d_name="testshare"}, {d_ino=27280, d_off=4, d_reclen=32, d_type=DT_DIR,
d_name="testshare2"}], 32768) = 112 <0.27>
2854 12:01:11.311912 lstat("testshare2", {st_dev=makedev(0, 0x31),
st_ino=27280, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0,
st_blksize=1024, st_blocks=0, st_size=0, st_atime=1642783648 /*
2022-01-21T11:47:28.580732805-0500 */, st_atime_nsec=580732805,
st_mtime=1642783648 /* 2022-01-21T11:47:28.580732805-0500 */,
st_mtime_nsec=580732805, st_ctime=1642783648 /*
2022-01-21T11:47:28.580732805-0500 */,
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
** Bug watch added: Red Hat Bugzilla #2044981 https://bugzilla.redhat.com/show_bug.cgi?id=2044981 ** Also affects: coreutils (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2044981 Importance: Unknown Status: Unknown ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: New Status in coreutils package in Fedora: Unknown Bug description: Release: 22.04.3 LTS coreutils 8.32-4.1ubuntu1 ls triggers unwanted mounts of autofs filesystems cause: coreutils 8.32.4.1ubuntu1 uses statx which not pass the AT_NO_AUTOMOUNT flag This bug is also known (and fixed) at Redhat https://bugzilla.redhat.com/show_bug.cgi?id=2044981 upstream commits: https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-178-g92cb8427c53 fedora commit https://src.fedoraproject.org/rpms/coreutils/c/d736cafa20f13eeb037a3950bdbb4b63dc39b7e3?branch=f35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+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 2032824] Re: Veth pairs fail activation on Jammy
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/network-manager/+git/network-manager/+merge/450447 -- 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/2032824 Title: Veth pairs fail activation on Jammy Status in network-manager package in Ubuntu: New Status in network-manager source package in Jammy: New Bug description: Network Manager 1.36 has a bug that prevents it to activate veth pairs. The problem was found in the Netplan's CI with the new support for veths in Netplan (because we run the tests on Jammy). How to reproduce the problem: 1) Launch a Jammy VM and install network-manager lxc launch ubuntu:jammy jammy --vm lxc shell jammy apt -y install network-manager 2) Set the default Netplan's renderer to NetworkManager so NM can manage interfaces (it will make Netplan create the file /var/run/NetworkManager/conf.d/10-globally-managed-devices.conf) netplan set --origin-hint=50-cloud-init network.renderer=NetworkManager netplan apply 3) Create the veth pair nmcli con add type veth ifname veth0 peer veth1 ipv4.method disabled ipv6.method disabled nmcli con add type veth ifname veth1 peer veth0 ipv4.method disabled ipv6.method disabled 4) Reboot 5) Check with "nmcli con show" that the new connections were not activated, even though both interfaces were created in the system. Also, check the systemd journal and you should see this error message: [1692805758.9025] manager: (veth-veth0) couldn't create the device: Failed to create veth interface 'veth0' for 'veth-veth0': exists Try the very same steps on Lunar and you'll see that the connections will be activated just fine. This issue appears to be fixed by this commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 I created a PPA with the fix here https://launchpad.net/~danilogondolfo/+archive/ubuntu/network-manager If you run the same steps again on Jammy with this PPA you'll see it fixes this issue. In fact, Netplan's integration tests will work on Jammy using the PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2032824/+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 2033892] [NEW] ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Public bug reported: Release: 22.04.3 LTS coreutils 8.32-4.1ubuntu1 ls triggers unwanted mounts of autofs filesystems cause: coreutils 8.32.4.1ubuntu1 uses statx which not pass the AT_NO_AUTOMOUNT flag This bug is also known (and fixed) at Redhat https://bugzilla.redhat.com/show_bug.cgi?id=2044981 upstream commits: https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-178-g92cb8427c53 fedora commit https://src.fedoraproject.org/rpms/coreutils/c/d736cafa20f13eeb037a3950bdbb4b63dc39b7e3?branch=f35 ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: New Bug description: Release: 22.04.3 LTS coreutils 8.32-4.1ubuntu1 ls triggers unwanted mounts of autofs filesystems cause: coreutils 8.32.4.1ubuntu1 uses statx which not pass the AT_NO_AUTOMOUNT flag This bug is also known (and fixed) at Redhat https://bugzilla.redhat.com/show_bug.cgi?id=2044981 upstream commits: https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-178-g92cb8427c53 fedora commit https://src.fedoraproject.org/rpms/coreutils/c/d736cafa20f13eeb037a3950bdbb4b63dc39b7e3?branch=f35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+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 2028935] Re: Merge rsyslog 8.2306.0-2
** Changed in: rsyslog (Ubuntu) Assignee: Julian Andres Klode (juliank) => Heinrich Schuchardt (xypron) ** Changed in: rsyslog (Ubuntu) Status: Fix Committed => In Progress -- 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/2028935 Title: Merge rsyslog 8.2306.0-2 Status in rsyslog package in Ubuntu: In Progress Bug description: Debian has upgraded rsyslog to 8.2306.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2028935/+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 2033880] [NEW] An unresolvable problem occurred while initialising the package information. Please report this bug for the 'update-manager' package
Public bug reported: An unresolvable problem occurred while initialising the package information. Please report this bug for the 'update-manager' package and try to include the following error message: E:can not open /var/lib/apt/lists/gb.archive.ubuntu.com_ubuntu_dists_jammy-updates_InRelease - fopen (13: Permission denied), E:The package lists or status file could not be parsed or opened. ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2033880 Title: An unresolvable problem occurred while initialising the package information. Please report this bug for the 'update-manager' package Status in whoopsie package in Ubuntu: New Bug description: An unresolvable problem occurred while initialising the package information. Please report this bug for the 'update-manager' package and try to include the following error message: E:can not open /var/lib/apt/lists/gb.archive.ubuntu.com_ubuntu_dists_jammy-updates_InRelease - fopen (13: Permission denied), E:The package lists or status file could not be parsed or opened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2033880/+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 11675] Re: Sapphire Radeon 9200 Atlantis 128MB AGP is not supported by generic radeon driver
New players can enjoy additional benefits such as 10+3, 20+6, or 50+15 on their first deposits, along with first deposit all-in coupons and thank-you coupons. https://www.casino-hera.com/ -- 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/11675 Title: Sapphire Radeon 9200 Atlantis 128MB AGP is not supported by generic radeon driver Status in xorg package in Ubuntu: Invalid Bug description: XFree86 is not configured for any video card at first boot. The generic radeon driver does not work for the Sapphire Radeon 9200 Atlantis 128MB AGP. I got it working by installing the fglrx driver. KICKASS system otherwise :) keep up the good work! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/11675/+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 2033747] Re: /usr/include/aarch64-linux-gnu/bits/math-vector.h:30: syntax error, unexpected identifier, expecting ',' or '; ' in 'typedef __Float32x4_t __f32x4_t; ' at '__f32x4_t
Actually this might only be coming from GObject introspection builds, so not from the C compiler? ** Description changed: - Building on Raspberry Pi mantic, these warnings keep repeating: + Building on Raspberry Pi mantic, these messages keep repeating: /usr/include/aarch64-linux-gnu/bits/math-vector.h:30: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __Float32x4_t __f32x4_t;' at '__f32x4_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:31: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __Float64x2_t __f64x2_t;' at '__f64x2_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:40: syntax error, unexpected identifier, expecting ',' or ';' in '# 40 "/usr/include/aarch64-linux-gnu/bits/math-vector.h" 3 4' at '__sv_f32_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:41: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __SVFloat64_t __sv_f64_t;' at '__sv_f64_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:42: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __SVBool_t __sv_bool_t;' at '__sv_bool_t' ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libc6-dev 2.38-1ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.27.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri Sep 1 15:38:51 2023 SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: gobject-introspection (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/2033747 Title: /usr/include/aarch64-linux-gnu/bits/math-vector.h:30: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __Float32x4_t __f32x4_t;' at '__f32x4_t' Status in glibc package in Ubuntu: New Status in gobject-introspection package in Ubuntu: New Bug description: Building on Raspberry Pi mantic, these messages keep repeating: /usr/include/aarch64-linux-gnu/bits/math-vector.h:30: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __Float32x4_t __f32x4_t;' at '__f32x4_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:31: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __Float64x2_t __f64x2_t;' at '__f64x2_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:40: syntax error, unexpected identifier, expecting ',' or ';' in '# 40 "/usr/include/aarch64-linux-gnu/bits/math-vector.h" 3 4' at '__sv_f32_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:41: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __SVFloat64_t __sv_f64_t;' at '__sv_f64_t' /usr/include/aarch64-linux-gnu/bits/math-vector.h:42: syntax error, unexpected identifier, expecting ',' or ';' in 'typedef __SVBool_t __sv_bool_t;' at '__sv_bool_t' ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libc6-dev 2.38-1ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.27.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri Sep 1 15:38:51 2023 SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2033747/+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 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
A few of my colleagues are also affected with 6.2. This is really a bad situation. As workaround we stepped back to linux-oem-22.04c (6.1) which works without problems. [1.545289] VGA switcheroo: detected Optimus DSM method \_SB_.PC00.PEG1.PEGP handle [1.545290] nouveau: detected PR support, will not use DSM [1.545320] nouveau :01:00.0: enabling device (0006 -> 0007) [1.545649] nouveau :01:00.0: NVIDIA GA107 (b77000a1) [1.567694] ACPI Error: Cannot release Mutex [ECMX], not acquired (20221020/exmutex-357) [1.567699] fbcon: Taking over console [1.567703] No Local Variables are initialized for Method [_Q66] [1.567704] No Arguments are initialized for method [_Q66] [1.567705] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_MUTEX_NOT_ACQUIRED) (20221020/psparse-529) [1.629655] usb 3-3: New USB device found, idVendor=0c45, idProduct=6720, bcdDevice=82.68 [1.629660] usb 3-3: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [1.629661] usb 3-3: Product: Integrated_Webcam_HD [1.629662] usb 3-3: Manufacturer: CN0V976R8LG001C1A5ANA01 [1.655115] nouveau :01:00.0: bios: version 94.07.3b.00.e4 [1.655549] nouveau :01:00.0: acr: firmware unavailable [1.655693] nouveau :01:00.0: gr: firmware unavailable [1.655706] nouveau :01:00.0: sec2: firmware unavailable [1.655798] nouveau :01:00.0: fb: 4096 MiB GDDR6 [1.659174] nouveau :01:00.0: fb: VPR locked, but no scrubber binary! [1.661968] BUG: kernel NULL pointer dereference, address: [1.661970] #PF: supervisor instruction fetch in kernel mode [1.661972] #PF: error_code(0x0010) - not-present page [1.661973] PGD 0 P4D 0 [1.661975] Oops: 0010 [#1] PREEMPT SMP NOPTI [1.661977] CPU: 14 PID: 233 Comm: systemd-udevd Not tainted 6.2.0-26-generic #26~22.04.1-Ubuntu [1.661980] Hardware name: Dell Inc. Precision 7560/0186RY, BIOS 1.20.0 02/10/2023 [1.661981] RIP: 0010:0x0 [1.661984] Code: Unable to access opcode bytes at 0xffd6. [1.661985] RSP: 0018:aaf340e0b628 EFLAGS: 00010246 [1.661986] RAX: RBX: 906ce208dcb0 RCX: [1.661988] RDX: 906ce208dcd8 RSI: 906ce208dcc8 RDI: 906ce208dc00 [1.661989] RBP: aaf340e0b688 R08: 906ce208dcb0 R09: [1.661990] R10: R11: R12: 906ce208dcc8 [1.661991] R13: R14: 906ce208dcb0 R15: 906ce208dc08 [1.661992] FS: 7f2e66a658c0() GS:90742ff8() knlGS: [1.661994] CS: 0010 DS: ES: CR0: 80050033 [1.661995] CR2: ffd6 CR3: 0001015d4006 CR4: 00770ee0 [1.661997] PKRU: 5554 [1.661999] Call Trace: [1.662000] [1.662001] nvkm_acr_oneinit+0x502/0x710 [nouveau] [1.662057] nvkm_subdev_oneinit_+0x4d/0x120 [nouveau] [1.662103] nvkm_subdev_init_+0x3e/0x150 [nouveau] [1.662145] nvkm_subdev_init+0x55/0x80 [nouveau] [1.662186] nvkm_device_init+0x17b/0x300 [nouveau] [1.662259] nvkm_udevice_init+0x50/0x60 [nouveau] [1.662322] nvkm_object_init+0x40/0x210 [nouveau] [1.662363] nvkm_ioctl_new+0x196/0x2c0 [nouveau] [1.662403] ? __pfx_nvkm_client_child_new+0x10/0x10 [nouveau] [1.662442] ? __pfx_nvkm_udevice_new+0x10/0x10 [nouveau] [1.662504] nvkm_ioctl+0x12e/0x290 [nouveau] [1.662543] nvkm_client_ioctl+0xe/0x20 [nouveau] [1.662614] nvif_object_ctor+0x136/0x1a0 [nouveau] [1.662652] nvif_device_ctor+0x24/0x90 [nouveau] [1.662690] nouveau_cli_init+0x161/0x5e0 [nouveau] [1.662757] nouveau_drm_device_init+0x67/0x310 [nouveau] [1.662821] nouveau_drm_probe+0x131/0x280 [nouveau] [1.662882] local_pci_probe+0x48/0xb0 [1.662886] pci_call_probe+0x55/0x190 [1.662888] pci_device_probe+0x84/0x120 [1.662890] really_probe+0x1ea/0x450 [1.662893] __driver_probe_device+0x8a/0x1a0 [1.662895] driver_probe_device+0x23/0xd0 [1.662897] __driver_attach+0x10f/0x220 [1.662899] ? __pfx___driver_attach+0x10/0x10 [1.662901] bus_for_each_dev+0x80/0xe0 [1.662903] driver_attach+0x1e/0x30 [1.662905] bus_add_driver+0x152/0x250 [1.662907] driver_register+0x83/0x160 [1.662909] ? __pfx_init_module+0x10/0x10 [nouveau] [1.662949] __pci_register_driver+0x68/0x80 [1.662950] nouveau_drm_init+0x177/0xff0 [nouveau] [1.662988] do_one_initcall+0x46/0x240 [1.662991] ? kmalloc_trace+0x2a/0xb0 [1.662994] do_init_module+0x52/0x240 [1.662997] load_module+0xb96/0xd60 [1.662999] ? kernel_read_file+0x25c/0x2b0 [1.663002] __do_sys_finit_module+0xcc/0x150 [1.663004] ? __do_sys_finit_module+0xcc/0x150 [1.663006] __x64_sys_finit_module+0x18/0x30 [1.663008] do_syscall_64+0x59/0x90 [1.663012] ? ksys_mmap_pgoff+0x123/0x270 [1.663014] ?
