[Touch-packages] [Bug 1972939] Re: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes
** Also affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1972939 Title: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes Status in Release Notes for Ubuntu: New Status in openssl package in Ubuntu: New Status in tinc package in Ubuntu: New Bug description: The tinc included in Jammy (1.0.36-2build1 linked with libssl3) cannot connect to tinc nodes running e.g. tinc from Xenial (1.0.26-1). (Tinc from Impish, which is also v1.0.36-2 but is linked to libssl1.1, can connect to these nodes without problems.) The symptom is a log message (on the system running Jammy) during the metadata channel negotiation (with debug level set to 5): Error during initialisation of cipher from tinc_xenial [...] error:0308010C:digital envelope routines::unsupported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1972939/+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 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
Yeah, ok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Impish: Fix Released Bug description: * Impact The clipboard copies from GTK based software sometime stop working under wayland * Test Case - in a wayland session try to copy text between software, from firefox to gedit for example, it should work in a consistent manner alternative testcase inspired from the gitlab ticket - install wl-clipboard - use evince to open a pdf - select and copy some content - on a cmdline do $ wl-paste -t TEXT - try to paste then in another software, gedit for example the copied text should be pasted * Regression potential The changes are in the wayland selection source so the impact should only be for wayland users and limited to clipboard interactions -- Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+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 1913775] Update Released
The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Impish: Fix Released Bug description: * Impact The clipboard copies from GTK based software sometime stop working under wayland * Test Case - in a wayland session try to copy text between software, from firefox to gedit for example, it should work in a consistent manner alternative testcase inspired from the gitlab ticket - install wl-clipboard - use evince to open a pdf - select and copy some content - on a cmdline do $ wl-paste -t TEXT - try to paste then in another software, gedit for example the copied text should be pasted * Regression potential The changes are in the wayland selection source so the impact should only be for wayland users and limited to clipboard interactions -- Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+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 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
This bug was fixed in the package gtk+3.0 - 3.24.30-1ubuntu1.1 --- gtk+3.0 (3.24.30-1ubuntu1.1) impish; urgency=medium * debian/patches/git_wayland_clipboard.patch: - wayland: Ensure clipboard handling doesn't lock up in certain corner cases, fix copy from firefox being unreliable (lp: #1913775) -- Sebastien Bacher Wed, 12 Jan 2022 12:44:47 +0100 ** Changed in: gtk+3.0 (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Impish: Fix Released Bug description: * Impact The clipboard copies from GTK based software sometime stop working under wayland * Test Case - in a wayland session try to copy text between software, from firefox to gedit for example, it should work in a consistent manner alternative testcase inspired from the gitlab ticket - install wl-clipboard - use evince to open a pdf - select and copy some content - on a cmdline do $ wl-paste -t TEXT - try to paste then in another software, gedit for example the copied text should be pasted * Regression potential The changes are in the wayland selection source so the impact should only be for wayland users and limited to clipboard interactions -- Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+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 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
Having the same error message"error reading events from display: Protocol error" when running wayland. However, extension manager having no issue opening in x11. Ubuntu 22.04 with Nividia driver 510 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1959047] Update Released
The verification of the Stable Release Update for lxd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1959047 Title: systemd ignores RootDirectory option in .service units Status in lxd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in lxd source package in Bionic: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Status in systemd source package in Impish: Confirmed Bug description: [Impact] Ubuntu carries a patch on top of systemd [a] to silence namespace set up failures. This is meant as a workaround for a bug in the LXD version shipped in Ubuntu 18.04. Masking namespace set up failures creates a false sense of security for the user/admin. As mentioned in comment #1, systemd upstream explains that silencing this kind of error is dangerous and should be avoided. Backporting the LXD fix [b] to Ubuntu 18.04 would allow namespaces to work inside containers. This is the goal of this SRU. Ultimately, once LXD in Ubuntu 18.04 includes the fix [b], it would be possible to drop the Ubuntu-specific patch for systemd [a]. This is however *not an immediate concern for this SRU*. [Test Plan] 1) Create a 18.04 VM: $ lxc launch images:ubuntu/18.04 lp1959047 --vm $ sleep 30 # give it time to boot 1.5) Enable bionic-proposed: $ echo "deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse" | lxc file push - lp1959047/etc/apt/sources.list.d/proposed.list 2) Install and initialize LXD in it: $ lxc exec lp1959047 -- apt-get update $ lxc exec lp1959047 -- apt-get install -y lxd $ lxc exec lp1959047 -- lxd init --auto 3) Create a Jammy container and enable systemd debugging: $ lxc exec lp1959047 -- lxc init images:ubuntu/22.04 c1 $ lxc exec lp1959047 -- lxc config set c1 raw.lxc 'lxc.init.cmd = /sbin/init systemd.log_level=debug' $ lxc exec lp1959047 -- lxc start c1 4) Check if namespace set up failures are logged: $ lxc exec lp1959047 -- lxc exec c1 -- journalctl -b0 --grep 'Failed to set up namespace' Mar 24 23:29:19 c1 systemd[99]: systemd-udevd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:19 c1 systemd[132]: systemd-networkd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:19 c1 systemd[131]: systemd-logind.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:20 c1 systemd[136]: systemd-resolved.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:20 c1 systemd[128]: e2scrub_reap.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:23 c1 systemd[243]: systemd-hostnamed.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied If LXD in Ubuntu 18.04 has the patch, the "Failed to set up namespace" messages wouldn't be there. [Where problems could occur] The LXD fix changes the Apparmor profile used for containers. This essentially loosen the mount restrictions applied to containers. Weakening the Apparmor profile could make it easier for a process in the container to do damage that would have otherwise been blocked. On the other hand, this allows making use of namespaces/sandboxing inside the container. Upstream LXD has the fix since 2019 which make it less likely to run into problems with the backport. The backported fix was also tested manually to ensure LXD still behaved normally and that it avoided the namespace set up failures in Jammy containers. [a]: https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch?h=ubuntu/jammy [b]: https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f [Initial bug description] The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the followin
[Touch-packages] [Bug 1959047] Re: systemd ignores RootDirectory option in .service units
This bug was fixed in the package lxd - 3.0.3-0ubuntu1~18.04.2 --- lxd (3.0.3-0ubuntu1~18.04.2) bionic; urgency=medium * Cherry-pick upstream bugfixes: - 0001-lxd-apparmor-Tweak-default-set-of-rules.patch (LP: #1959047) -- Stéphane Graber Thu, 24 Mar 2022 12:18:01 -0400 ** Changed in: lxd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units Status in lxd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in lxd source package in Bionic: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Status in systemd source package in Impish: Confirmed Bug description: [Impact] Ubuntu carries a patch on top of systemd [a] to silence namespace set up failures. This is meant as a workaround for a bug in the LXD version shipped in Ubuntu 18.04. Masking namespace set up failures creates a false sense of security for the user/admin. As mentioned in comment #1, systemd upstream explains that silencing this kind of error is dangerous and should be avoided. Backporting the LXD fix [b] to Ubuntu 18.04 would allow namespaces to work inside containers. This is the goal of this SRU. Ultimately, once LXD in Ubuntu 18.04 includes the fix [b], it would be possible to drop the Ubuntu-specific patch for systemd [a]. This is however *not an immediate concern for this SRU*. [Test Plan] 1) Create a 18.04 VM: $ lxc launch images:ubuntu/18.04 lp1959047 --vm $ sleep 30 # give it time to boot 1.5) Enable bionic-proposed: $ echo "deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse" | lxc file push - lp1959047/etc/apt/sources.list.d/proposed.list 2) Install and initialize LXD in it: $ lxc exec lp1959047 -- apt-get update $ lxc exec lp1959047 -- apt-get install -y lxd $ lxc exec lp1959047 -- lxd init --auto 3) Create a Jammy container and enable systemd debugging: $ lxc exec lp1959047 -- lxc init images:ubuntu/22.04 c1 $ lxc exec lp1959047 -- lxc config set c1 raw.lxc 'lxc.init.cmd = /sbin/init systemd.log_level=debug' $ lxc exec lp1959047 -- lxc start c1 4) Check if namespace set up failures are logged: $ lxc exec lp1959047 -- lxc exec c1 -- journalctl -b0 --grep 'Failed to set up namespace' Mar 24 23:29:19 c1 systemd[99]: systemd-udevd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:19 c1 systemd[132]: systemd-networkd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:19 c1 systemd[131]: systemd-logind.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:20 c1 systemd[136]: systemd-resolved.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:20 c1 systemd[128]: e2scrub_reap.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:23 c1 systemd[243]: systemd-hostnamed.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied If LXD in Ubuntu 18.04 has the patch, the "Failed to set up namespace" messages wouldn't be there. [Where problems could occur] The LXD fix changes the Apparmor profile used for containers. This essentially loosen the mount restrictions applied to containers. Weakening the Apparmor profile could make it easier for a process in the container to do damage that would have otherwise been blocked. On the other hand, this allows making use of namespaces/sandboxing inside the container. Upstream LXD has the fix since 2019 which make it less likely to run into problems with the backport. The backported fix was also tested manually to ensure LXD still behaved normally and that it avoided the namespace set up failures in Jammy containers. [a]: https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch?h=ubuntu/jammy [b]: https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f [Initial bug description] The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: # /etc/systemd/system/lsb-release.service [Unit] Description=L
[Touch-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
I'm not sure we even need switch-on-connect anymore. It was introduced as a patch in 2017 (bug 1702794) at the request of Will Cooke but I suspect later upstream changes within the module logic like module- switch-on-port-available might suffice now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: New Status in pulseaudio source package in Kinetic: Triaged Status in ubuntu-settings source package in Kinetic: New Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
This bug was fixed in the package shadow - 1:4.8.1-1ubuntu5.20.04.2 --- shadow (1:4.8.1-1ubuntu5.20.04.2) focal; urgency=medium [ Michael Vogt ] * debian/patches/1010_extrausers.patch: Add automatic detection of "extrausers" for usermod -G (LP: #1959375) -- Alberto Mardegan Mon, 14 Mar 2022 11:26:09 +0300 ** Changed in: shadow (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Bionic: Fix Committed Status in shadow source package in Focal: Fix Released Status in shadow source package in Impish: Won't Fix Status in shadow source package in Jammy: Fix Released Bug description: [Impact] * In order to use the microk8s snap in Ubuntu Core, one currently needs to be root. This is far from optimal, since normally (on desktop and server installations) this is not necessary. * This make it hard to provide consistent documentation on microk8s across all supported device, if we have to take the "sudo" command into account, and how file permissions for generated files might be affected. [Test Plan] The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps are as following (replace "" with the actual path of your Ubuntu Core image file: qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=,format=raw After configuring your account, connect to youd device via SSH: ssh @localhost -p 8022 And issue these commands sudo snap install microk8s --channel=latest/edge/stable # microk8s is going to eat up all your disk space, so stop it as soon # as the prompt comes back: sudo microk8s stop # Add your user to the microk8s group sudo usermod -G snap_microk8s $(whoami) The last command will fail unless this bug is fixed. If the bug is fixed, the command will succeed, and after logging out and in again, you can verify that you've been added to the snap_microk8s group by running the "groups" command. [Where problems could occur] * The patch only touches error code paths and adds a fallback mechanism in them. Therefore, "normal" operations, where these commands would have succeeded before, will not be affected at all. * In those cases when usermod fails because it failed to find or load the requested user/group, we reset the user/group database paths to our writable user/group databases, and retry the operation. Note that the path for our database is hardcoded in the program source, so the security risk seems contained. We do not add additional command-line parameters. [Other Info] Original bug description Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Update Released
The verification of the Stable Release Update for shadow has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Bionic: Fix Committed Status in shadow source package in Focal: Fix Committed Status in shadow source package in Impish: Won't Fix Status in shadow source package in Jammy: Fix Released Bug description: [Impact] * In order to use the microk8s snap in Ubuntu Core, one currently needs to be root. This is far from optimal, since normally (on desktop and server installations) this is not necessary. * This make it hard to provide consistent documentation on microk8s across all supported device, if we have to take the "sudo" command into account, and how file permissions for generated files might be affected. [Test Plan] The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps are as following (replace "" with the actual path of your Ubuntu Core image file: qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=,format=raw After configuring your account, connect to youd device via SSH: ssh @localhost -p 8022 And issue these commands sudo snap install microk8s --channel=latest/edge/stable # microk8s is going to eat up all your disk space, so stop it as soon # as the prompt comes back: sudo microk8s stop # Add your user to the microk8s group sudo usermod -G snap_microk8s $(whoami) The last command will fail unless this bug is fixed. If the bug is fixed, the command will succeed, and after logging out and in again, you can verify that you've been added to the snap_microk8s group by running the "groups" command. [Where problems could occur] * The patch only touches error code paths and adds a fallback mechanism in them. Therefore, "normal" operations, where these commands would have succeeded before, will not be affected at all. * In those cases when usermod fails because it failed to find or load the requested user/group, we reset the user/group database paths to our writable user/group databases, and retry the operation. Note that the path for our database is hardcoded in the program source, so the security risk seems contained. We do not add additional command-line parameters. [Other Info] Original bug description Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
Yeeah, ok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Bionic: Fix Committed Status in shadow source package in Focal: Fix Committed Status in shadow source package in Impish: Won't Fix Status in shadow source package in Jammy: Fix Released Bug description: [Impact] * In order to use the microk8s snap in Ubuntu Core, one currently needs to be root. This is far from optimal, since normally (on desktop and server installations) this is not necessary. * This make it hard to provide consistent documentation on microk8s across all supported device, if we have to take the "sudo" command into account, and how file permissions for generated files might be affected. [Test Plan] The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps are as following (replace "" with the actual path of your Ubuntu Core image file: qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=,format=raw After configuring your account, connect to youd device via SSH: ssh @localhost -p 8022 And issue these commands sudo snap install microk8s --channel=latest/edge/stable # microk8s is going to eat up all your disk space, so stop it as soon # as the prompt comes back: sudo microk8s stop # Add your user to the microk8s group sudo usermod -G snap_microk8s $(whoami) The last command will fail unless this bug is fixed. If the bug is fixed, the command will succeed, and after logging out and in again, you can verify that you've been added to the snap_microk8s group by running the "groups" command. [Where problems could occur] * The patch only touches error code paths and adds a fallback mechanism in them. Therefore, "normal" operations, where these commands would have succeeded before, will not be affected at all. * In those cases when usermod fails because it failed to find or load the requested user/group, we reset the user/group database paths to our writable user/group databases, and retry the operation. Note that the path for our database is hardcoded in the program source, so the security risk seems contained. We do not add additional command-line parameters. [Other Info] Original bug description Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962454] Re: Oops pages show wrong time window in JournalErrors
** Merge proposal linked: https://code.launchpad.net/~apport-hackers/apport/+git/apport/+merge/422775 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1962454 Title: Oops pages show wrong time window in JournalErrors Status in Apport: In Progress Status in Errors: Invalid Status in apport package in Ubuntu: Triaged Status in apport source package in Jammy: Triaged Bug description: For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. But it should be possible to tell journalctl to collect entries starting *before* the crash and cover the full crash timeframe. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1962454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962454] Re: Oops pages show wrong time window in JournalErrors
** Changed in: apport Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1962454 Title: Oops pages show wrong time window in JournalErrors Status in Apport: In Progress Status in Errors: Invalid Status in apport package in Ubuntu: Triaged Status in apport source package in Jammy: Triaged Bug description: For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. But it should be possible to tell journalctl to collect entries starting *before* the crash and cover the full crash timeframe. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1962454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969934] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1969934 Title: Update evolution-data-server to 3.44.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: Fix Released Bug description: Impact -- This is a new stable release in the 3.44 series (corresponding with GNOME 42). https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.1/NEWS It is required to update evolution to 3.44.1 (LP: #1969935) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+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 1969934] Re: Update evolution-data-server to 3.44.1
This bug was fixed in the package evolution-data-server - 3.44.1-0ubuntu2 --- evolution-data-server (3.44.1-0ubuntu2) jammy; urgency=medium * Don't build with libgweather4 evolution-data-server (3.44.1-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #1969934) evolution-data-server (3.44.0-3) unstable; urgency=medium * Build with libgweather4 -- Jeremy Bicha Mon, 09 May 2022 19:16:50 -0400 ** Changed in: evolution-data-server (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1969934 Title: Update evolution-data-server to 3.44.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: Fix Released Bug description: Impact -- This is a new stable release in the 3.44 series (corresponding with GNOME 42). https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.1/NEWS It is required to update evolution to 3.44.1 (LP: #1969935) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+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 1971474] Re: SRU: Update gdb to the final 12.1 release in 22.04 LTS
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971474 Title: SRU: Update gdb to the final 12.1 release in 22.04 LTS Status in gdb package in Ubuntu: Confirmed Bug description: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - updated gnulib library - Fix for PR mi/29002 (Windows only) - gdb: fix 'remote show FOO-packet' aliases - various testsuite fixes - fixing compiler warnings - Fix bug in Ada number lexing - Remove "Ada Settings" node from the manual - Handle TLS variable lookups when using separate debug files. - PR 28980: gdb: don't copy entirely optimized out values in value_copy - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474/+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 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1971538 Title: My machine as Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1973217] Re: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
Thanks for taking the time to file this bug and trying to make Ubuntu better. >From the attached logs: May 12 08:50:07 paradise sshd[59551]: /etc/ssh/sshd_config: line 125: Bad configuration option: Host May 12 08:50:07 paradise sshd[59551]: /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 May 12 08:50:07 paradise sshd[59551]: /etc/ssh/sshd_config: terminating, 2 bad configuration options Which tells us that this is a local configuration issue. The Host and ForwardX11 options are causing the issue, avoiding the service to start. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community -- 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/1973217 Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: It might be that two instances of update-manager seemed to be running at the same time. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 12 08:50:07 2022 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-06 (582 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 125: Bad configuration option: Host /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 /etc/ssh/sshd_config: terminating, 2 bad configuration options SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-09-29 (225 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1973217/+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 1973137] Re: ldap_do_free_request: Assertion `lr->lr_refcnt == 1' failed
You mentioned it is taking longer to process the request but it is working. So I am setting the priority to Low and I am adding this bug to the server team backlog. It will be looked at once we find some time. ** Changed in: openldap (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1973137 Title: ldap_do_free_request: Assertion `lr->lr_refcnt == 1' failed Status in openldap package in Ubuntu: New Bug description: I dont know it is openldap related: Operation System: Ubuntu 22.04 Packages: sssd-ldap 2.6.3-1ubuntu3 libldap-2.5-0:amd64 2.5.11+dfsg-1~exp1ubuntu3 libldap-common2.5.11+dfsg-1~exp1ubuntu3 I have configured sssd to use LDAPS over HAPROXY. With the latest Debian Version and Ubuntu 20.04 i have no error. But with Ubuntu 22.04 i randomly cant login. Syslog show this error: May 12 06:57:55 ingress2 sssd[870590]: sssd_be: ../../../../libraries/libldap/request.c:970: ldap_do_free_request: Assertion `lr->lr_refcnt == 1' failed. If i configured SSSD to use directly our LDAP Server, its working. Regards Sebastian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1973137/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
This behavior particularly affects Raspberry Pis, where USB is the only bus available for a lot of devices and treating this as "hotplug" gives wrong results. That doesn't mean the default should change for pulseaudio on the desktop in general, but should somehow be treated in a hardware-specific manner. I would suggest making /etc/pulse/default.pa key its loading of module- switch-on-connect on the absence of a flag file, which could then be provided by raspberry pi images. I'm going to open a task on ubuntu-settings for the moment, since it provides ubuntu-raspi-settings that seems the most likely existing package to attach the raspi side of this to. ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: pulseaudio (Ubuntu Kinetic) Importance: Low Status: Triaged ** Also affects: ubuntu-settings (Ubuntu Kinetic) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: New Status in pulseaudio source package in Kinetic: Triaged Status in ubuntu-settings source package in Kinetic: New Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1913775] Autopkgtest regression report (gtk+3.0/3.24.30-1ubuntu1.1)
All autopkgtests for the newly accepted gtk+3.0 (3.24.30-1ubuntu1.1) for impish have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.11-0ubuntu71 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#gtk+3.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Impish: Fix Committed Bug description: * Impact The clipboard copies from GTK based software sometime stop working under wayland * Test Case - in a wayland session try to copy text between software, from firefox to gedit for example, it should work in a consistent manner alternative testcase inspired from the gitlab ticket - install wl-clipboard - use evince to open a pdf - select and copy some content - on a cmdline do $ wl-paste -t TEXT - try to paste then in another software, gedit for example the copied text should be pasted * Regression potential The changes are in the wayland selection source so the impact should only be for wayland users and limited to clipboard interactions -- Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+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 1973747] Re: Please include Flatpak by default
** Changed in: ubuntu-meta (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1973747 Title: Please include Flatpak by default Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Hi, First, thank you for your hard work on Ubuntu! Adding Flatpak could make the user experience easier and better for new users, and it has much more apps than Snap has. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1973747/+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 1971299] Re: Merge nss from Debian unstable for kinetic
** Changed in: nss (Ubuntu) Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1971299 Title: Merge nss from Debian unstable for kinetic Status in nss package in Ubuntu: New Bug description: Upstream: tbd Debian: 2:3.77-1 Ubuntu: 2:3.68.2-0ubuntu1 ### New Debian Changes ### nss (2:3.77-1) unstable; urgency=medium * New upstream release. * debian/libnss3.symbols: Add NSS_3.77 symbol version. -- Mike Hommey Wed, 06 Apr 2022 09:18:22 +0900 nss (2:3.75-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 09 Feb 2022 08:46:51 +0900 nss (2:3.73.1-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Fri, 17 Dec 2021 06:16:55 +0900 nss (2:3.73-1) unstable; urgency=medium * New upstream release. * Fixes MFSA-2021-51, aka CVE-2021-43527: Memory corruption via DER-encoded DSA and RSA-PSS signatures. -- Mike Hommey Thu, 02 Dec 2021 06:04:31 +0900 nss (2:3.72-2) unstable; urgency=medium * debian/control: libnss3-dev breaks libxmlsec1-dev (<< 1.2.33-1). Closes: #998733. -- Mike Hommey Fri, 12 Nov 2021 06:21:05 +0900 nss (2:3.72-1) unstable; urgency=medium * New upstream release. * debian/libnss3.symbols, nss/lib/ssl/sslinfo.c, nss/lib/ssl/sslt.h, nss/cmd/selfserv/selfserv.c, nss/cmd/strsclnt/strsclnt.c, nss/cmd/tstclnt/tstclnt.c: Bump dependency version for SSL_GetChannelInfo symbol and remove the previous workaround. Closes: #990058. * debian/libnss3.lintian-overrides.in, debian/rules, nss/cmd/shlibsign/shlibsign.c, nss/lib/pk11wrap/pk11load.c, nss/lib/util/secload.c, nss/cmd/shlibsign/Makefile, nss/cmd/shlibsign/manifest.mn: Stop putting freebl, softokn, etc. in a subdirectory. It's a deviation from upstream that is causing more problems than it's worth keeping. Closes: #737855, #846012, #979159. * debian/libnss3-dev.links.in: Remove xulrunner-nss.pc. * debian/rules: Stop forcing xz compression. * debian/copyright: Add dot for continuation. * debian/watch: Upgrade to version 4. * debian/control: Upgrade Standard-Version to 4.6.0: - debian/rules: Build with `make -s` when DEB_BUILD_OPTIONS contains terse. - debian/control: Add Rules-Requires-Root: no. * debian/control: Remove conflict with libnss3-1d. The last Debian version with libnss3-1d was jessie, and it had a newer version anyways. * debian/rules: Enable all hardening options. * debian/libnss3-symbols: Add Build-Depends-Package in symbols file. * debian/*.lintian-overrides*: Remove copyright-refers-to-versionless-license-file lintian overrides. * debian/libnss3.lintian-overrides.in: - s/shlib-without-versioned-soname/shared-library-lacks-version/. - Add lacks-unversioned-link-to-shared-library overrides. * debian/nss-config.in, debian/rules: Ship upstream nss-config instead of ours. Closes: #737855, #963136. * debian/rules, debian/control: Always set Multi-Arch: same. * debian/copyright: - Remove commas in `Files`. - Add missing license name for ifparser. - Add missing `Copyright`. - Remove copyright for mkdepend, which is not in the source tree anymore. * debian/upstream/metadata: Add upstream bug tracking metadata. [ Daniel Kahn Gillmor ] * debian/control: correct Homepage (old URL redirects to 404) [ Janitor ] * debian/changelog: Trim trailing whitespace. * debian/copyright: Use secure copyright file specification URI. * debian/compat, debian/control: - Bump debhelper from deprecated 9 to 13. - Set debhelper-compat version in Build-Depends. * debian/upstream/metadata: Set upstream metadata fields: Repository. * debian/rules: Drop transition for old debug package migration. -- Mike Hommey Tue, 02 Nov 2021 06:57:06 +0900 nss (2:3.70-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 08 Sep 2021 08:31:23 +0900 nss (2:3.68-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Mon, 19 Jul 2021 06:23:39 +0900 ### Old Ubuntu Delta ### nss (2:3.68.2-0ubuntu1) jammy; urgency=medium * New upstream release. (LP: #1959126) * d/p/CVE-2021-43527.patch: drop patch applied upstream. [ Fixed in 3.68.1 ] -- Athos Ribeiro Mon, 21 Feb 2022 14:55:42 -0300 nss (2:3.68-1ubuntu2) jammy; urgency=medium * SECURITY UPDATE: heap overflow when verifying DSA/RSA-PSS DER-encoded signatures - debian/patches/CVE-2021-43527.patch: check signature lengths in nss/lib/cryptohi/secvfy.c. - CVE-2021-43527 -- Marc Deslauriers Mon, 29 Nov 2021 07:12:54 -0500 nss (2:3.68-1ubuntu1) impish; urgency=med
[Touch-packages] [Bug 1973747] Re: Please include Flatpak by default
** Summary changed: - Please Flatpak by default + Please include Flatpak by default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1973747 Title: Please include Flatpak by default Status in ubuntu-meta package in Ubuntu: New Bug description: Hi, First, thank you for your hard work on Ubuntu! Adding Flatpak could make the user experience easier and better for new users, and it has much more apps than Snap has. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1973747/+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 1973610] Re: Bluetooth will not stay on or connect to devices when on
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in bluez package in Ubuntu: Confirmed Status in bluez-firmware package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1973610/+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 1973610] Re: Bluetooth will not stay on or connect to devices when on
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in bluez package in Ubuntu: Confirmed Status in bluez-firmware package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1973610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Perhaps due to different type of hardware ? Here i used a Dell E5550. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971089] Re: Network Manager bug constant reconnecting and CPU usage
Yes I checked. Seems after remove the package system works as expected. -- 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/1971089 Title: Network Manager bug constant reconnecting and CPU usage Status in network-manager package in Ubuntu: New Bug description: Anyconnectin result cpu heavy usage. constant reconnections wifi/ethernet..no matter ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun May 1 17:00:00 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-03 (1793 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.148 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to jammy on 2022-04-25 (6 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971089/+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 1973788] Re: package findutils 4.9.0-3
Building in ppa:xypron/findutils ** Changed in: findutils (Ubuntu) Status: New => Confirmed ** Tags added: fr-2392 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1973788 Title: package findutils 4.9.0-3 Status in findutils package in Ubuntu: Confirmed Bug description: Package the Debian upstream plus Ubuntu specific changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1973788/+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 1973788] Re: package findutils 4.9.0-3
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1973788 Title: package findutils 4.9.0-3 Status in findutils package in Ubuntu: Confirmed Bug description: Package the Debian upstream plus Ubuntu specific changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1973788/+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 1973788] Re: package findutils 4.9.0-3
** Patch added: "findutils_4.8.0-1ubuntu3..4.9.0-3ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1973788/+attachment/5590426/+files/findutils_4.8.0-1ubuntu3..4.9.0-3ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1973788 Title: package findutils 4.9.0-3 Status in findutils package in Ubuntu: Confirmed Bug description: Package the Debian upstream plus Ubuntu specific changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1973788/+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 1973792] [NEW] [Philips TAT1215, playback] Bluetooth fails to reconnect (need to remove device to make it work)
Public bug reported: I can connect the Bluetooth Earbud correctly on the first time, but once I shutdown the laptop or the earbud it fails to reconnect. Even if I go there and manually click the toggle button to connect, it keeps loading for a while and fails to connect. The only way to connect the earbud again is going on the Bluetooth settings and clicking on "Remove device" shutdown and turn Bluetooth again to list the device and connect. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anderson 1363 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 17 12:06:38 2022 InstallationDate: Installed on 2022-05-15 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Philips TAT1215 Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [Philips TAT1215, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2022 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0P54MM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd01/28/2022:br1.12:svnDellInc.:pnVostro3401:pvr:rvnDellInc.:rn0P54MM:rvrA00:cvnDellInc.:ct10:cvr:sku0A29: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1973792 Title: [Philips TAT1215, playback] Bluetooth fails to reconnect (need to remove device to make it work) Status in alsa-driver package in Ubuntu: New Bug description: I can connect the Bluetooth Earbud correctly on the first time, but once I shutdown the laptop or the earbud it fails to reconnect. Even if I go there and manually click the toggle button to connect, it keeps loading for a while and fails to connect. The only way to connect the earbud again is going on the Bluetooth settings and clicking on "Remove device" shutdown and turn Bluetooth again to list the device and connect. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anderson 1363 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 17 12:06:38 2022 InstallationDate: Installed on 2022-05-15 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Philips TAT1215 Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [Philips TAT1215, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2022 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0P54MM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd01/28/2022:br1.12:svnDellInc.:pnVostro3401:pvr:rvnDellInc.:rn0P54MM:rvrA00:cvnDellInc.:ct10:cvr:sku0A29: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1973792/+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 1973788] [NEW] package findutils 4.9.0-3
Public bug reported: Package the Debian upstream plus Ubuntu specific changes ** Affects: findutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1973788 Title: package findutils 4.9.0-3 Status in findutils package in Ubuntu: New Bug description: Package the Debian upstream plus Ubuntu specific changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1973788/+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 1972029] Re: dhclient overriding stub-resolv.conf file on Jammy
** Tags added: sts sts-sponsor-halves -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1972029 Title: dhclient overriding stub-resolv.conf file on Jammy Status in isc-dhcp package in Ubuntu: New Bug description: [Issue] On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten if dhclient is executed. While debugging this, I found the reference on LP#1889068 [0] of the move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit- hooks.d/, and this new hook [2] has no reference of make_resolv_conf() being called. [Reproducer] - I used a cloud-image based Jammy installation (uvt-kvm). Once in: $ cat /run/system/resolve/stub-resolv.conf And one will see: nameserver 127.0.0.53 options edns0 trust-ad search . Then: $ sudo dhclient $ cat /run/system/resolve/stub-resolv.conf You'll see the definition of the nameserver(s) in, and the stub IP address no longer there. To revert this, a `systemctl restart systemd-resolved` is needed. [Impact] This is an improper way to keep nameserver(s) in *resolv* files; the override of the file should never happen in these circumstances. [Extra] - As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from a Focal installation to a Jammy one, and the problem _does not happen_ when such hook is in place. [ . . . ] Let me know if further clarification is needed to proceed. Thank you. BR, pprincipeza [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068 [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/ [2] https://paste.ubuntu.com/p/YQdG6z4WS7/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1972029/+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 1973642] Re: [REGRESSION] Unable to connect to EAP-TLS networks
1.38 has been uploaded to kinetic now, https://launchpad.net/ubuntu/+source/network-manager/1.38.0-1ubuntu1 -- 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/1973642 Title: [REGRESSION] Unable to connect to EAP-TLS networks Status in network-manager package in Ubuntu: Fix Committed Bug description: Fresh install of Xubuntu 22.04, currently with network-manager 1.36.4-2ubuntu1 Attempting to connect to an EAP-TLS network fails with: NetworkManager[703]: [1652732829.9142] device (wlp0s12f0): Activation: (wifi) connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager[703]: [1652732829.9143] Config: added 'ssid' value 'AP' NetworkManager[703]: [1652732829.9143] Config: added 'scan_ssid' value '1' NetworkManager[703]: [1652732829.9144] Config: added 'bgscan' value 'simple:30:-65:300' NetworkManager[703]: [1652732829.9144] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256' NetworkManager[703]: [1652732829.9144] Config: added 'eap' value 'TLS' NetworkManager[703]: [1652732829.9144] Config: added 'fragment_size' value '1266' NetworkManager[703]: [1652732829.9144] Config: added 'ca_cert' value '' NetworkManager[703]: [1652732829.9144] Config: added 'domain_suffix_match' value '' NetworkManager[703]: [1652732829.9145] Config: added 'private_key' value '.key' NetworkManager[703]: [1652732829.9145] Config: added 'private_key_passwd' value '' NetworkManager[703]: [1652732829.9145] Config: added 'client_cert' value '.crt' NetworkManager[703]: [1652732829.9145] Config: added 'identity' value '' NetworkManager[703]: [1652732829.9146] Config: added 'proactive_key_caching' value '1' NetworkManager[703]: [1652732829.9178] sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to add network: invalid message format NetworkManager[703]: [1652732829.9179] device (wlp0s12f0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed') Caused by NM providing an empty domain_suffix_match option Upstream commit fixing this (also attached): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec Upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973642/+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 1973760] Re: Crash when using DIGEST-MD5 with SSF>=128
https://github.com/cyrusimap/cyrus-sasl/pull/668 ** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #665 https://github.com/cyrusimap/cyrus-sasl/issues/665 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1973760 Title: Crash when using DIGEST-MD5 with SSF>=128 Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: I'm still troubleshooting this, but at the moment apps negotiating a DIGEST-MD5 authentication and requesting some form of transport encryption (ssf != 0) are crashing. The only example I have so far is the openldap client tools (so just one app really). ssf=0 works: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=0 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 0 dn:uid=ubuntu@lxd,cn=vms,cn=digest-md5,cn=auth ssf=128 crashes: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=128 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 128 SASL data security layer installed. Segmentation fault (core dumped) The crash seems to be inside openssl. I'll get a proper stack trace. 2.1.27, also built with openssl3, does not crash. So far only 2.1.28 (in kinetic-proposed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1973760/+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 1973760] Re: Crash when using DIGEST-MD5 with SSF>=128
https://github.com/cyrusimap/cyrus-sasl/pull/653 https://github.com/cyrusimap/cyrus-sasl/issues/665 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1973760 Title: Crash when using DIGEST-MD5 with SSF>=128 Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: I'm still troubleshooting this, but at the moment apps negotiating a DIGEST-MD5 authentication and requesting some form of transport encryption (ssf != 0) are crashing. The only example I have so far is the openldap client tools (so just one app really). ssf=0 works: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=0 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 0 dn:uid=ubuntu@lxd,cn=vms,cn=digest-md5,cn=auth ssf=128 crashes: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=128 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 128 SASL data security layer installed. Segmentation fault (core dumped) The crash seems to be inside openssl. I'll get a proper stack trace. 2.1.27, also built with openssl3, does not crash. So far only 2.1.28 (in kinetic-proposed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1973760/+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 1973760] Re: Crash when using DIGEST-MD5 with SSF>=128
Working theory at the moment is that cyrus-sasl2 is using RC4 from OpenSSL, and OpenSSL3 deprecated it: On Kinetic: $ openssl version OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) $ echo -ne test | openssl rc4 -k test *** WARNING : deprecated key derivation used. Using -iter or -pbkdf2 would be better. Error setting cipher RC4 4057FE8C0B7F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RC4 : 37), Properties () Salted__gG On Impish: $ openssl version OpenSSL 1.1.1l 24 Aug 2021 $ echo -ne test | openssl rc4 -k test *** WARNING : deprecated key derivation used. Using -iter or -pbkdf2 would be better. Salted__~T�|=�ʇ Jammy: $ openssl version OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) $ echo -ne "test" | openssl rc4 -k test *** WARNING : deprecated key derivation used. Using -iter or -pbkdf2 would be better. Error setting cipher RC4 40078BF4127F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RC4 : 37), Properties () Salted__��N�x��� Both jammy and kinetic show "Error setting cipher RC4". Oh, and the stack trace confirming it's inside openssl: (gdb) bt #0 0x774085cb in EVP_EncryptUpdate (ctx=0x0, out=out@entry=0x555c7cf4 "0\036\002\001\004w\031\200\027\061.3.6.1.4.1.4203.1.11.3ST-MD5 client step 3", outl=outl@entry=0x7fffdbc4, in=0x555c8d50 "0\036\002\001\004w\031\200\027\061.3.6.1.4.1.4203.1.11.311.311.3", inl=32) at ../crypto/evp/evp_enc.c:614 #1 0x770a07a9 in enc_rc4 (text=0x55585e00, input=, inputlen=, digest=0x7fffdc20 "^\316@+\322}\a\334\006T\005\353:H}\036\260l\\UUU", output=0x555c7cf4 "0\036\002\001\004w\031\200\027\061.3.6.1.4.1.4203.1.11.3ST-MD5 client step 3", outputlen=0x7fffdda4) at ../../plugins/digestmd5.c:1201 #2 0x770a1ddb in digestmd5_encode (context=0x55585e00, invec=, numiov=, output=0x5559e708, outputlen=0x7fffdda4) at ../../plugins/digestmd5.c:1552 #3 0x77f33c3e in _sasl_encodev (conn=conn@entry=0x55586cf0, invec=invec@entry=0x7fffdd70, numiov=numiov@entry=1, p_num_packets=p_num_packets@entry=0x7fffdd0c, output=output@entry=0x5559e708, outputlen=outputlen@entry=0x7fffdda4) at ../../lib/common.c:359 #4 0x77f360a1 in sasl_encodev (conn=conn@entry=0x55586cf0, invec=invec@entry=0x7fffdd70, numiov=numiov@entry=1, output=output@entry=0x5559e708, outputlen=outputlen@entry=0x7fffdda4) at ../../lib/common.c:582 #5 0x77f361d0 in sasl_encode (conn=0x55586cf0, input=, inputlen=, output=output@entry=0x5559e708, outputlen=outputlen@entry=0x7fffdda4) at ../../lib/common.c:304 #6 0x77f665ba in sb_sasl_cyrus_encode (p=0x5559e680, buf=, len=, dst=0x5559e6f0) at ../../../../libraries/libldap/cyrus.c:134 #7 0x77f66b90 in sb_sasl_generic_write (sbiod=0x55585a30, buf=0x555c8d50, len=) at ../../../../libraries/libldap/sasl.c:783 #8 0x77f4ad3c in sb_debug_write (sbiod=0x55586aa0, buf=0x555c8d50, len=32) at ../../../../libraries/liblber/sockbuf.c:854 #9 0x77f50105 in ber_int_sb_write (sb=sb@entry=0x55585900, buf=0x555c8d50, len=len@entry=32) at ../../../../libraries/liblber/sockbuf.c:445 #10 0x77f5027b in ber_flush2 (sb=0x55585900, ber=0x555c7c90, freeit=freeit@entry=0) at ../../../../libraries/liblber/io.c:249 #11 0x77f7e0a7 in ldap_int_flush_request (ld=ld@entry=0x555834e0, lr=lr@entry=0x555c6cb0) at ../../../../libraries/libldap/request.c:186 #12 0x77f8001f in ldap_send_server_request (ld=ld@entry=0x555834e0, ber=ber@entry=0x555c7c90, msgid=msgid@
[Touch-packages] [Bug 1973779] Re: Could not enable livepatch 22.04 LTS
** Package changed: ubuntu-release-upgrader (Ubuntu) => software- properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1973779 Title: Could not enable livepatch 22.04 LTS Status in software-properties package in Ubuntu: New Bug description: Once upgraded from 20.10 to 22.04 I try to enable livepatch (the PC is attached to Ubuntu Advantage Subscription) "Could not Enable Livepatch. Please try again." --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-04 (497 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: ubuntu-release-upgrader (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Tags: jammy dist-upgrade Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-05-15 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeTermlog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973779/+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 1973779] [NEW] Could not enable livepatch 22.04 LTS
You have been subscribed to a public bug: Once upgraded from 20.10 to 22.04 I try to enable livepatch (the PC is attached to Ubuntu Advantage Subscription) "Could not Enable Livepatch. Please try again." --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-04 (497 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: ubuntu-release-upgrader (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Tags: jammy dist-upgrade Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-05-15 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeTermlog: _MarkForUpload: True ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected dist-upgrade jammy -- Could not enable livepatch 22.04 LTS https://bugs.launchpad.net/bugs/1973779 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
** Changed in: ifupdown (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: ifupdown (Ubuntu) Assignee: (unassigned) => Heinrich Schuchardt (xypron) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Fix Committed Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1973747] Re: Please Flatpak by default
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1973747 Title: Please Flatpak by default Status in ubuntu-meta package in Ubuntu: New Bug description: Hi, First, thank you for your hard work on Ubuntu! Adding Flatpak could make the user experience easier and better for new users, and it has much more apps than Snap has. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1973747/+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 1973747] [NEW] Please Flatpak by default
You have been subscribed to a public bug: Hi, First, thank you for your hard work on Ubuntu! Adding Flatpak could make the user experience easier and better for new users, and it has much more apps than Snap has. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Please Flatpak by default https://bugs.launchpad.net/bugs/1973747 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1973777] [NEW] package linux-generic-hwe-20.04 5.13.0.41.46~20.04.26 failed to install/upgrade: 依存関係の問題 - 設定を見送ります
Public bug reported: package linux-generic-hwe-20.04 5.13.0.41.46~20.04.26 failed to install/upgrade: downgrade kernel to 5.13.0-39 avoided this problem. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.13.0.41.46~20.04.26 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 17 20:46:43 2022 ErrorMessage: 依存関係の問題 - 設定を見送ります InstallationDate: Installed on 2022-03-04 (74 days ago) InstallationMedia: Ubuntu 20.04.1 "Focal Fossa" - Release amd64(20200808.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-generic-hwe-20.04 5.13.0.41.46~20.04.26 failed to install/upgrade: 依存関係の問題 - 設定を見送ります UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1973777 Title: package linux-generic-hwe-20.04 5.13.0.41.46~20.04.26 failed to install/upgrade: 依存関係の問題 - 設定を見送ります Status in initramfs-tools package in Ubuntu: New Bug description: package linux-generic-hwe-20.04 5.13.0.41.46~20.04.26 failed to install/upgrade: downgrade kernel to 5.13.0-39 avoided this problem. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.13.0.41.46~20.04.26 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 17 20:46:43 2022 ErrorMessage: 依存関係の問題 - 設定を見送ります InstallationDate: Installed on 2022-03-04 (74 days ago) InstallationMedia: Ubuntu 20.04.1 "Focal Fossa" - Release amd64(20200808.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-generic-hwe-20.04 5.13.0.41.46~20.04.26 failed to install/upgrade: 依存関係の問題 - 設定を見送ります UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1973777/+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 1971112] Re: File picker gets bigger more and more each time!
** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Package changed: ubuntu => gtk4 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1971112 Title: File picker gets bigger more and more each time! Status in gtk4 package in Ubuntu: Confirmed Bug description: Hello. I've just switched to Ubuntu and ever since day 1 I had this issue that whenever I tried to choose a file the file picker window was way too big and it was getting bigger and bigger each time. I have posted a video on Reddit recording this unusual/unexpected behavior. Here is the reddit post link (with video): https://www.reddit.com/r/Ubuntu/comments/ug97qx/annoying_bug_file_picker_gets_bigger_more_and/ I've also attached the video to this post, in case you don't want to click the link above. Here is my neofetch output: OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-27-generic Uptime: 13 hours, 13 mins Shell: bash 5.1.16 Resolution: 1440x900, 1920x1080 DE: GNOME 42.0 WM: Mutter WM Theme: Adwaita Theme: Yaru-viridian-dark [GTK2/3] Icons: Yaru-viridian [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-8700K (12) @ 4.700GHz GPU: NVIDIA GeForce GTX 1060 3GB Memory: 5869MiB / 15936MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1971112/+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 1971112] Re: File picker gets bigger more and more each time!
As I've noted in my duplicate bug report, this effects snaps (Firefox, Brave) but not apts (Evince, Thunderbird). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1971112 Title: File picker gets bigger more and more each time! Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Hello. I've just switched to Ubuntu and ever since day 1 I had this issue that whenever I tried to choose a file the file picker window was way too big and it was getting bigger and bigger each time. I have posted a video on Reddit recording this unusual/unexpected behavior. Here is the reddit post link (with video): https://www.reddit.com/r/Ubuntu/comments/ug97qx/annoying_bug_file_picker_gets_bigger_more_and/ I've also attached the video to this post, in case you don't want to click the link above. Here is my neofetch output: OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-27-generic Uptime: 13 hours, 13 mins Shell: bash 5.1.16 Resolution: 1440x900, 1920x1080 DE: GNOME 42.0 WM: Mutter WM Theme: Adwaita Theme: Yaru-viridian-dark [GTK2/3] Icons: Yaru-viridian [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-8700K (12) @ 4.700GHz GPU: NVIDIA GeForce GTX 1060 3GB Memory: 5869MiB / 15936MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1971112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
On a different Ubuntu 22.04 system I DO NOT reproduce the problem. pcscd was working fine with no extra manual operation. This time I used a real laptop and not a virtual machine. But that should not have an effect. The problem may not be easy to understand. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928080] Re: Noto Sans Hebrew is not set as the fallback font of Noto Sans
Guess this is a wontfix ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1928080 Title: Noto Sans Hebrew is not set as the fallback font of Noto Sans Status in fontconfig package in Ubuntu: Invalid Bug description: [This is a minor issue] Hello, Noto Sans Hebrew is not set as the fallback font of Noto Sans in Kubuntu, and the current fallback font of Noto Sans is Liberation Sans, and not Noto Sans Hebrew. May you fix it, please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1928080/+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 1934825] Re: [Wishlist] RTL interface for software-properties-qt
My mistake. There is a problem when in root mode, not in the application itself. ** Changed in: software-properties (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934825 Title: [Wishlist] RTL interface for software-properties-qt Status in software-properties package in Ubuntu: Invalid Bug description: Please add RTL interface for software-properties-qt. This will improve its usability for users from the middle east. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934825/+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 1973760] Re: Crash when using DIGEST-MD5 with SSF>0
It's also crashing in debian: https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python- bonsai/21842977/log.gz ** Summary changed: - Crash when using DIGEST-MD5 with SSF>0 + Crash when using DIGEST-MD5 with SSF>=128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1973760 Title: Crash when using DIGEST-MD5 with SSF>=128 Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: I'm still troubleshooting this, but at the moment apps negotiating a DIGEST-MD5 authentication and requesting some form of transport encryption (ssf != 0) are crashing. The only example I have so far is the openldap client tools (so just one app really). ssf=0 works: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=0 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 0 dn:uid=ubuntu@lxd,cn=vms,cn=digest-md5,cn=auth ssf=128 crashes: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=128 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 128 SASL data security layer installed. Segmentation fault (core dumped) The crash seems to be inside openssl. I'll get a proper stack trace. 2.1.27, also built with openssl3, does not crash. So far only 2.1.28 (in kinetic-proposed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1973760/+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 1973760] [NEW] Crash when using DIGEST-MD5 with SSF>=128
Public bug reported: I'm still troubleshooting this, but at the moment apps negotiating a DIGEST-MD5 authentication and requesting some form of transport encryption (ssf != 0) are crashing. The only example I have so far is the openldap client tools (so just one app really). ssf=0 works: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=0 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 0 dn:uid=ubuntu@lxd,cn=vms,cn=digest-md5,cn=auth ssf=128 crashes: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=128 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 128 SASL data security layer installed. Segmentation fault (core dumped) The crash seems to be inside openssl. I'll get a proper stack trace. 2.1.27, also built with openssl3, does not crash. So far only 2.1.28 (in kinetic-proposed). ** Affects: cyrus-sasl2 (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Tags: server-todo update-excuse update-excuses -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1973760 Title: Crash when using DIGEST-MD5 with SSF>=128 Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: I'm still troubleshooting this, but at the moment apps negotiating a DIGEST-MD5 authentication and requesting some form of transport encryption (ssf != 0) are crashing. The only example I have so far is the openldap client tools (so just one app really). ssf=0 works: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=0 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 0 dn:uid=ubuntu@lxd,cn=vms,cn=digest-md5,cn=auth ssf=128 crashes: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=128 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 128 SASL data security layer installed. Segmentation fault (core dumped) The crash seems to be inside openssl. I'll get a proper stack trace. 2.1.27, also built with openssl3, does not crash. So far only 2.1.28 (in kinetic-proposed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1973760/+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 1971112] Re: File picker gets bigger more and more each time!
I also have this issue and have tried to troubleshoot it. Maybe this is an interesting contribution. If you use dconf-editor and find the "window-size" option for filechooser, you can see the dimensions of the current filechooser window. Here, you can manually set it to something reasonable (e.g., 800x600) or the default. Then press save. https://i.postimg.cc/zvGTpYmy/filechooer.jpg Ok, how here is the interesting bit. When you next call the filechooser from an app showing this annoying behaviour, you will see that you need to reload the deconf-editor window because changes have been made. So the app call changed the user-set size and increased it. But also changes it from default to another size (bigger). In my desperation I even tried to make the dconf file read only and even tried to change its owner to prevent my user from writing (changing it). None of these work. Another addition to this bug. The behaviour where the dialogue window is not responsive is because the background window (the browser, for example) is still in focus. This is why you cannot press escape to close the filechooser. In fact, you can press ctr+s multiple times and it just opens a new instance of filechooser with a larger window than before until maximised. I can confirm that this behaviour is shown in Brave browser (chrome), Firefox, and Telegram. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1971112 Title: File picker gets bigger more and more each time! Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Hello. I've just switched to Ubuntu and ever since day 1 I had this issue that whenever I tried to choose a file the file picker window was way too big and it was getting bigger and bigger each time. I have posted a video on Reddit recording this unusual/unexpected behavior. Here is the reddit post link (with video): https://www.reddit.com/r/Ubuntu/comments/ug97qx/annoying_bug_file_picker_gets_bigger_more_and/ I've also attached the video to this post, in case you don't want to click the link above. Here is my neofetch output: OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-27-generic Uptime: 13 hours, 13 mins Shell: bash 5.1.16 Resolution: 1440x900, 1920x1080 DE: GNOME 42.0 WM: Mutter WM Theme: Adwaita Theme: Yaru-viridian-dark [GTK2/3] Icons: Yaru-viridian [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-8700K (12) @ 4.700GHz GPU: NVIDIA GeForce GTX 1060 3GB Memory: 5869MiB / 15936MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1971112/+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 1973642] Re: [REGRESSION] Unable to connect to EAP-TLS networks
Thank you for your bug report. Upstream cherry picked the fix in their nm-1-36 serie now and plan to do a .6 stable update which we will SRU once it's available. ** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Committed -- 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/1973642 Title: [REGRESSION] Unable to connect to EAP-TLS networks Status in network-manager package in Ubuntu: Fix Committed Bug description: Fresh install of Xubuntu 22.04, currently with network-manager 1.36.4-2ubuntu1 Attempting to connect to an EAP-TLS network fails with: NetworkManager[703]: [1652732829.9142] device (wlp0s12f0): Activation: (wifi) connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager[703]: [1652732829.9143] Config: added 'ssid' value 'AP' NetworkManager[703]: [1652732829.9143] Config: added 'scan_ssid' value '1' NetworkManager[703]: [1652732829.9144] Config: added 'bgscan' value 'simple:30:-65:300' NetworkManager[703]: [1652732829.9144] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256' NetworkManager[703]: [1652732829.9144] Config: added 'eap' value 'TLS' NetworkManager[703]: [1652732829.9144] Config: added 'fragment_size' value '1266' NetworkManager[703]: [1652732829.9144] Config: added 'ca_cert' value '' NetworkManager[703]: [1652732829.9144] Config: added 'domain_suffix_match' value '' NetworkManager[703]: [1652732829.9145] Config: added 'private_key' value '.key' NetworkManager[703]: [1652732829.9145] Config: added 'private_key_passwd' value '' NetworkManager[703]: [1652732829.9145] Config: added 'client_cert' value '.crt' NetworkManager[703]: [1652732829.9145] Config: added 'identity' value '' NetworkManager[703]: [1652732829.9146] Config: added 'proactive_key_caching' value '1' NetworkManager[703]: [1652732829.9178] sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to add network: invalid message format NetworkManager[703]: [1652732829.9179] device (wlp0s12f0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed') Caused by NM providing an empty domain_suffix_match option Upstream commit fixing this (also attached): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec Upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973642/+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
Re: [Touch-packages] [Bug 1973732] Re: [vmwgfx] Artifacts in PHPSTORM, Browser, All applications. Lags, freeze.
VMware Workstation вт, 17 мая 2022 г. в 11:56, Daniel van Vugt <1973...@bugs.launchpad.net>: > Please also tell us what hypervisor you are using. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1973732 > > Title: > [vmwgfx] Artifacts in PHPSTORM, Browser, All applications. Lags, > freeze. > > Status in linux package in Ubuntu: > Incomplete > Status in mesa package in Ubuntu: > Incomplete > > Bug description: > I get artifacts in almost every app. There are problems with > searching, copying. The system is now running slowly. I use PHPSTORM, > Postman, Chrome. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: gnome-shell 42.0-2ubuntu1 > ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 > Uname: Linux 5.15.0-30-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Tue May 17 11:04:21 2022 > DisplayManager: gdm3 > InstallationDate: Installed on 2022-02-21 (84 days ago) > InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) > RelatedPackageVersions: mutter-common 42.0-3ubuntu2 > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to jammy on 2022-05-16 (0 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973732/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1973732 Title: [vmwgfx] Artifacts in PHPSTORM, Browser, All applications. Lags, freeze. Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: I get artifacts in almost every app. There are problems with searching, copying. The system is now running slowly. I use PHPSTORM, Postman, Chrome. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 17 11:04:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-21 (84 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973732/+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 1973732] Re: [vmwgfx] Artifacts in PHPSTORM, Browser, All applications. Lags, freeze.
Please also tell us what hypervisor you are using. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1973732 Title: [vmwgfx] Artifacts in PHPSTORM, Browser, All applications. Lags, freeze. Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: I get artifacts in almost every app. There are problems with searching, copying. The system is now running slowly. I use PHPSTORM, Postman, Chrome. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 17 11:04:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-21 (84 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973732/+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 1973732] Re: Artifacts in PHPSTORM, Browser, All applications. Lags, freeze.
Thanks for the bug report. Are you able to provide a photo or video of the problem? ** Tags added: vmwgfx ** Summary changed: - Artifacts in PHPSTORM, Browser, All applications. Lags, freeze. + [vmwgfx] Artifacts in PHPSTORM, Browser, All applications. Lags, freeze. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1973732 Title: [vmwgfx] Artifacts in PHPSTORM, Browser, All applications. Lags, freeze. Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: I get artifacts in almost every app. There are problems with searching, copying. The system is now running slowly. I use PHPSTORM, Postman, Chrome. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 17 11:04:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-21 (84 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973732/+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 1881935] Re: Minimum inode size should be raised to 256 for forward compatibility (Y2038)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1881935
Title:
Minimum inode size should be raised to 256 for forward compatibility
(Y2038)
Status in e2fsprogs package in Ubuntu:
Confirmed
Bug description:
mke2fs in all supported Ubuntu releases to date creates 'small' ext4
file systems with an inode size of 128. This is said to be
insufficient to store time stamps referring to year 2038 and later
(when the Unix epoch exceeds a signed 32-bit integer -
https://en.wikipedia.org/wiki/Year_2038_problem). When such file
systems are mounted by the kernel, such as a /boot file system created
by the Ubuntu 20.04.0 Desktop installer (ubiquity 20.04.15), the
kernel will warn about this fact:
kernel: ext4 filesystem being mounted at /boot supports timestamps
until 2038 (0x7fff)
Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953494
Admittedly, that's another 18 years, by when most systems installed
now will be no longer in use, or will have been reinstalled.
Also, on a /boot file system the 5.4.0-33-generic #37 Ubuntu (20.04) kernel
warned about this, I was able to
$ touch -t 203812312359 /tmp/test
and got
$ ls -l /tmp/test
-rw-r--r-- 1 root root 0 Dez 31 2038 /tmp/test
so this warning may not always apply, or patches may have been applied to
handle this situation more gracefully already.
Ubuntu 20.04 comes with e2fsprogs 1.45.5-2ubuntu1. Theodore Y. Ts'o
has submitted patches for Debian's 1.45.6-1 - but (strictly speaking
based on the changelog) these seem to be limited to documentation
changes.
Still, creating such file systems may seem undesirable in terms of
forward compatibility. I therefore suggest to change the minimum inode
size for mke2fs, as defined in /etc/mke2fs.conf, to 256 for all file
systems which do not already use this value (maybe with the exception
of floppies). That is, I suggest the following change to Ubuntu
20.04's /etc/mke2fs.conf:
Before change:
small = {
inode_size = 128
inode_ratio = 4096
}
After change:
small = {
inode_ratio = 4096
}
This assumes that the default inode size is already set to 256 further
above.
As a WORKAROUND, after backing up the file system (this command is not well
tested, according to the lead ext4 file system developer), users can unmount
the affected file system and run
tune2fs -I 256 /path/to/block_device
where /path/to/block_device should be replaced by the path to the block
device which contains the file system the kernel reports the warning for. For
example, for the file system mounted at /boot, the
findmnt /boot
command would return the block device path in the SOURCE column.
Please note I prefer not to use apport for this bug report, I believe it is
already sufficiently complete.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1881935/+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 1881935] Re: Minimum inode size should be raised to 256 for forward compatibility (Y2038)
It seems the default was fixed in upstream at
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/misc/mke2fs.conf.in?id=a23b50cdb55cb826b8745cbc37429c93f7b60c66
Also, it seems Ubuntu 22.04 has a version of e2fsprogs (1.46.5-2ubuntu1)
which includes this change. Thus I think this bug can be closed as
resolved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1881935
Title:
Minimum inode size should be raised to 256 for forward compatibility
(Y2038)
Status in e2fsprogs package in Ubuntu:
Confirmed
Bug description:
mke2fs in all supported Ubuntu releases to date creates 'small' ext4
file systems with an inode size of 128. This is said to be
insufficient to store time stamps referring to year 2038 and later
(when the Unix epoch exceeds a signed 32-bit integer -
https://en.wikipedia.org/wiki/Year_2038_problem). When such file
systems are mounted by the kernel, such as a /boot file system created
by the Ubuntu 20.04.0 Desktop installer (ubiquity 20.04.15), the
kernel will warn about this fact:
kernel: ext4 filesystem being mounted at /boot supports timestamps
until 2038 (0x7fff)
Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953494
Admittedly, that's another 18 years, by when most systems installed
now will be no longer in use, or will have been reinstalled.
Also, on a /boot file system the 5.4.0-33-generic #37 Ubuntu (20.04) kernel
warned about this, I was able to
$ touch -t 203812312359 /tmp/test
and got
$ ls -l /tmp/test
-rw-r--r-- 1 root root 0 Dez 31 2038 /tmp/test
so this warning may not always apply, or patches may have been applied to
handle this situation more gracefully already.
Ubuntu 20.04 comes with e2fsprogs 1.45.5-2ubuntu1. Theodore Y. Ts'o
has submitted patches for Debian's 1.45.6-1 - but (strictly speaking
based on the changelog) these seem to be limited to documentation
changes.
Still, creating such file systems may seem undesirable in terms of
forward compatibility. I therefore suggest to change the minimum inode
size for mke2fs, as defined in /etc/mke2fs.conf, to 256 for all file
systems which do not already use this value (maybe with the exception
of floppies). That is, I suggest the following change to Ubuntu
20.04's /etc/mke2fs.conf:
Before change:
small = {
inode_size = 128
inode_ratio = 4096
}
After change:
small = {
inode_ratio = 4096
}
This assumes that the default inode size is already set to 256 further
above.
As a WORKAROUND, after backing up the file system (this command is not well
tested, according to the lead ext4 file system developer), users can unmount
the affected file system and run
tune2fs -I 256 /path/to/block_device
where /path/to/block_device should be replaced by the path to the block
device which contains the file system the kernel reports the warning for. For
example, for the file system mounted at /boot, the
findmnt /boot
command would return the block device path in the SOURCE column.
Please note I prefer not to use apport for this bug report, I believe it is
already sufficiently complete.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1881935/+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 1973734] [NEW] FTBFS on riscv64 in focal
Public bug reported: [Impact] * FTBFS on riscv64 in focal in unittest of volume test * Disable that unit test, as later releases do not run unittests on riscv64, and it's better to have up to date pulseaudio on riscv64 (with many security fixes), even if it doesn't completely correctly work. [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * volume-test probably indicates that one can't set volume correctly on riscv64 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1973734 Title: FTBFS on riscv64 in focal Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: New Bug description: [Impact] * FTBFS on riscv64 in focal in unittest of volume test * Disable that unit test, as later releases do not run unittests on riscv64, and it's better to have up to date pulseaudio on riscv64 (with many security fixes), even if it doesn't completely correctly work. [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * volume-test probably indicates that one can't set volume correctly on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1973734/+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 1973733] [NEW] no change rebuild to get security update out on riscv64
Public bug reported: no change rebuild to get riscv64 build out [Impact] * riscv64 build of cups security update failed, and then succeeded in groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1 * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 * do a no change rebuild of cups as an SRU to get updated cups package out on focal [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * As usual, no change rebuilds of packages may introduce miss builds. [Other Info] * currently snap review tooling reports that cups has CVEs on riscv64 when one builds base:core20 snaps for riscv64. ** Affects: cups (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: cups (Ubuntu Focal) Importance: Undecided Status: In Progress ** Summary changed: - no change rebuild to get riscv64 build out + no change rebuild to get security update out on riscv64 ** Also affects: cups (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Status: New => Fix Released ** Description changed: no change rebuild to get riscv64 build out [Impact] - * riscv64 build of cups security update failed, and then succeeded in groovy - * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 - * do a no change rebuild of cups as an SRU to get updated cups package out on focal + * riscv64 build of cups security update failed, and then succeeded in groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1 + * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 + * do a no change rebuild of cups as an SRU to get updated cups package out on focal [Test Plan] - * autopkgtests pass - * riscv64 build is successful + * autopkgtests pass + * riscv64 build is successful [Where problems could occur] - * As usual, no change rebuilds of packages may introduce miss builds. + * As usual, no change rebuilds of packages may introduce miss builds. [Other Info] - - * currently snap review tooling reports that cups has CVEs on riscv64 when one builds base:core20 snaps for riscv64. + + * currently snap review tooling reports that cups has CVEs on riscv64 + when one builds base:core20 snaps for riscv64. ** Changed in: cups (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 Status in cups package in Ubuntu: Fix Released Status in cups source package in Focal: In Progress Bug description: no change rebuild to get riscv64 build out [Impact] * riscv64 build of cups security update failed, and then succeeded in groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1 * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 * do a no change rebuild of cups as an SRU to get updated cups package out on focal [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * As usual, no change rebuilds of packages may introduce miss builds. [Other Info] * currently snap review tooling reports that cups has CVEs on riscv64 when one builds base:core20 snaps for riscv64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+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 1968154] Re: Only keep 2 kernels
This bug was fixed in the package apt - 2.0.8 --- apt (2.0.8) focal; urgency=medium * Adjust conffile removal version in postinst and maintscript; followup fix for (LP: #1968154) apt (2.0.7) focal; urgency=medium * Revert "Protect currently running kernel at run-time" * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of 2.4.5; including the change to only protect two kernels, not last installed one (LP: #1968154) -- Julian Andres Klode Mon, 25 Apr 2022 15:58:46 +0200 ** Changed in: apt (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968154] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968154] Re: Only keep 2 kernels
This bug was fixed in the package apt - 2.3.9ubuntu0.1 --- apt (2.3.9ubuntu0.1) impish; urgency=medium * Only protect two kernels, not last installed one (LP: #1968154) * Point to impish in gitlab-ci and gbp.conf -- Julian Andres Klode Mon, 25 Apr 2022 16:14:41 +0200 ** Changed in: apt (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
This bug was fixed in the package wpa - 2:2.10-6ubuntu1 --- wpa (2:2.10-6ubuntu1) jammy; urgency=medium * debian/patches/allow-legacy-renegotiation.patch: allow legacy renegotiation to fix PEAP issues with some servers (lp: #1962541) -- Sebastien Bacher Thu, 05 May 2022 11:31:26 +0200 ** Changed in: wpa (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Released Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962541] Update Released
The verification of the Stable Release Update for wpa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Released Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
This bug was fixed in the package openssl - 3.0.2-0ubuntu1.2 --- openssl (3.0.2-0ubuntu1.2) jammy; urgency=medium * d/p/lp1968997/*: cherry-pick a patchset to fix issues with the Turkish locale (LP: #1968997) -- Simon Chopin Thu, 05 May 2022 10:04:52 +0200 ** Changed in: openssl (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Jammy: Fix Released Status in openssl source package in Kinetic: Fix Committed Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64&kernel=5.15.0-25-generic&series=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget&curl doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1968997] Update Released
The verification of the Stable Release Update for openssl has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Jammy: Fix Released Status in openssl source package in Kinetic: Fix Committed Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64&kernel=5.15.0-25-generic&series=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget&curl doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1973379] Re: "additional drivers" says we are using nvidia drivers but its not true
right, we would need the debug output when the issue is showing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1973379 Title: "additional drivers" says we are using nvidia drivers but its not true Status in software-properties package in Ubuntu: Incomplete Bug description: after selecting the recommended, tested nvidia driver, and restarting the system as suggested, no nvidia modules are loaded at all, instead just nouveau kernel modules are loaded and all the nvidia tools confirm that no nvidia drivers are being used and running. But starting the software properties and opening the "additional drivers" tab again, I'm being told the nvidia drivers are in selected and "1 proprietary driver in use". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 13 23:20:12 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-04-12 (760 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 SourcePackage: software-properties UpgradeStatus: Upgraded to jammy on 2022-04-28 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973379/+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 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04
** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine as Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: New Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
@Anton Please report a new bug using $ ubuntu-bug wpasupplicant then edit /lib/systemd/system/wpa_supplicant.service to add a '-d' to the ExecStart cmd, restart, try to connect and share the 'journalctl -b 0' log from the system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
The package successfully built in my PPA [1]. Note that I forgot to replace the changelog signoff with mine, please use the following: -- Alexandre Ghiti Mon, 28 Mar 2022 18:31:38 + [1] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13619002/+listing- archive-extra -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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
