[Touch-packages] [Bug 2028187] Re: Bluetooth audio locked to device disallows other devices to use Bluetooth speaker
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2028187 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/2028187 Title: Bluetooth audio locked to device disallows other devices to use Bluetooth speaker Status in bluez package in Ubuntu: Incomplete Bug description: Not sure which layer is causing this. I switch bluetooth audio sources going to my AVR frequently throughout the day. After an update, Ubuntu seems to continue sending something like a keepalive to the bluetooth receiver despite no audio being played on the computer. This prohibits switching to my phone as the audio source. For example if I play a youtube video in Chrome, and then stop the video and then play Amazon Music or Spotify, the device is connected but I get no audio. If I close Chrome, no change. If I disconnect Ubuntu from that bluetooth device, audio starts coming through. No change to bluetooth receiver, but there was a Samsung update the other day. Interestingly, I disconnected Ubuntu from my BT device. Connected my phone, played some audio, then disconnected my phone from the BT device. Ubuntu then automatically connected back to that BT device and prohibits my phone from using it. This was clearly a change to the bluetooth stack that doesn't release the BT device when audio is stopped by the application. Linux gnosis 5.15.0-76-generic #83 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2028187/+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 2028282] Re: SSH pubkey authetication fails when GSSAPI enabled
On Wed, Jul 26, 2023 at 07:24:37AM -, Moritz Carmesin wrote: > Unsetting KRB5CCNAME breaks the Kerbreros based login, so it is really > just an emergency workaround. You can unset it for just the ssh process that needs non-Kerberos login. -- 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/2028282 Title: SSH pubkey authetication fails when GSSAPI enabled Status in openssh package in Ubuntu: Triaged Bug description: Since the upgrade from Ubuntu 20.04 to 22.04 the SSH login via a SSH pubkey to our servers fails, while password and kerberos are still working. $ssh user@server sign_and_send_pubkey: internal error: initial hostkey not recorded This seem related to the bugreport at openssh: https://bugzilla.mindrot.org/show_bug.cgi?id=3406 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Jul 20 17:25:01 2023 InstallationDate: Installed on 2020-08-24 (1060 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: openssh UpgradeStatus: Upgraded to jammy on 2023-07-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2028282/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
I'm not sure we need so many "Confirmed" tasks at the top of this page. It's misleading if most of them are not required to fix the bug, but we'll be more confident that it's fixed for most people when GTK 4.6.9 is released to Ubuntu 22.04. -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Invalid Status in GTK+: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Fix Committed Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
It's not mentioned in the changelog but it looks like a fix for 22.04 will arrive with: https://launchpad.net/ubuntu/+source/gtk4/4.6.9+ds-0ubuntu0.22.04.1 ** No longer affects: gnome-shell (Ubuntu) ** Changed in: gtk4 (Ubuntu Jammy) Status: Triaged => Fix Committed -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Invalid Status in GTK+: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Fix Committed Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
I'm just generally curious, does debootstrap function differently with/without this patch? I'd imagine it either goes off the task, or a level lower than the metapackages. -- 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/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028810] Re: rsync 3.1.3 performance regression
The attachment "add-trusted-sender-arg.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2028810 Title: rsync 3.1.3 performance regression Status in rsync package in Ubuntu: New Bug description: OS: Ubuntu 20.04 Focal Package: rsync 3.1.3-8ubuntu0.5 rsync's performance was regressed by ~7x amount after some security patch (debian/patches/CVE-2022-29154-*) was applied to the package, and introduced a list of filters that iterate on every file being transferred. We think that was where the performance regression came from. A Jammy version of the package (3.2.5) introduced a new flag "--trust- sender" that allowed user to avoid the expensive client-side filtering introduced by those security patches. After pulling this change (https://github.com/WayneD/rsync/commit/cff8f044776c5143a5b270969d4bb0f1fea8b017) from rsync ourselves and applied it to the Focal version, the performance regression went away. The patch we used to backport our Focal rsync is attached in this thread. Can you please backport it too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2028810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
Thanks Nathan, I finally lined up all the ducks, and it appears to have worked. - The dir I'm building in has to be in my home dir - the xvfb-run seems necessary - don't attempt to use --headless - both --user-data-dir=/tmp/ChrUnsnapped and --class="ChrUnsnapped" seem unnecessary So, user@host:~/tmp/ChromeExtensions$ xvfb-run /snap/bin/chromium --pack-extension=MyExt --pack-extension-key=MyExt.pem Tested with chromium snap v2556 (115.0.5790.102). I'll have to update our build system to copy files to somewhere in /home/, build there, and copy the results back. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2028811] [NEW] systemd-network installs adjacency routes to DNS servers from DHCP even if they're off-net
Public bug reported: This is a known issue upstream: https://github.com/systemd/systemd/issues/28495 and indeed a fix is milestoned for v255: https://github.com/systemd/systemd/pull/28508 It would be good to see this in the next backports build. Note: this bug only manifests when the DHCP server is sending you a list of DNS servers (fairly common) as well as static-classless-routes (option 121... much less common). Description:Ubuntu 22.04.2 LTS Release:22.04 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jul 26 16:57:28 2023 InstallationDate: Installed on 2017-02-28 (2339 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M MachineType: Red Hat KVM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-76-generic root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to jammy on 2022-09-07 (322 days ago) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.1-1.el9 dmi.board.name: RHEL dmi.board.vendor: Red Hat dmi.board.version: RHEL-9.2.0 PC (Q35 + ICH9, 2009) dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL-9.2.0 PC (Q35 + ICH9, 2009) dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.1-1.el9:bd04/01/2014:br0.0:svnRedHat:pnKVM:pvrRHEL-9.2.0PC(Q35+ICH9,2009):rvnRedHat:rnRHEL:rvrRHEL-9.2.0PC(Q35+ICH9,2009):cvnRedHat:ct1:cvrRHEL-9.2.0PC(Q35+ICH9,2009):sku9.2.0: dmi.product.family: Red Hat Enterprise Linux dmi.product.name: KVM dmi.product.sku: 9.2.0 dmi.product.version: RHEL-9.2.0 PC (Q35 + ICH9, 2009) dmi.sys.vendor: Red Hat ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2028811 Title: systemd-network installs adjacency routes to DNS servers from DHCP even if they're off-net Status in systemd package in Ubuntu: New Bug description: This is a known issue upstream: https://github.com/systemd/systemd/issues/28495 and indeed a fix is milestoned for v255: https://github.com/systemd/systemd/pull/28508 It would be good to see this in the next backports build. Note: this bug only manifests when the DHCP server is sending you a list of DNS servers (fairly common) as well as static-classless-routes (option 121... much less common). Description: Ubuntu 22.04.2 LTS Release: 22.04 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
[Touch-packages] [Bug 2028810] [NEW] rsync 3.1.3 performance regression
Public bug reported: OS: Ubuntu 20.04 Focal Package: rsync 3.1.3-8ubuntu0.5 rsync's performance was regressed by ~7x amount after some security patch (debian/patches/CVE-2022-29154-*) was applied to the package, and introduced a list of filters that iterate on every file being transferred. We think that was where the performance regression came from. A Jammy version of the package (3.2.5) introduced a new flag "--trust- sender" that allowed user to avoid the expensive client-side filtering introduced by those security patches. After pulling this change (https://github.com/WayneD/rsync/commit/cff8f044776c5143a5b270969d4bb0f1fea8b017) from rsync ourselves and applied it to the Focal version, the performance regression went away. The patch we used to backport our Focal rsync is attached in this thread. Can you please backport it too? ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Patch added: "add-trusted-sender-arg.patch" https://bugs.launchpad.net/bugs/2028810/+attachment/5688659/+files/add-trusted-sender-arg.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2028810 Title: rsync 3.1.3 performance regression Status in rsync package in Ubuntu: New Bug description: OS: Ubuntu 20.04 Focal Package: rsync 3.1.3-8ubuntu0.5 rsync's performance was regressed by ~7x amount after some security patch (debian/patches/CVE-2022-29154-*) was applied to the package, and introduced a list of filters that iterate on every file being transferred. We think that was where the performance regression came from. A Jammy version of the package (3.2.5) introduced a new flag "--trust- sender" that allowed user to avoid the expensive client-side filtering introduced by those security patches. After pulling this change (https://github.com/WayneD/rsync/commit/cff8f044776c5143a5b270969d4bb0f1fea8b017) from rsync ourselves and applied it to the Focal version, the performance regression went away. The patch we used to backport our Focal rsync is attached in this thread. Can you please backport it too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2028810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
** Changed in: ibus (Ubuntu) Status: Confirmed => In Progress ** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: Fix Released Status in ibus package in Ubuntu: In Progress Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+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 2028774] Re: ssh fails to load opensc-pkcs11.so
One of the commits for the security fix for CVE-2023-28408 will now attempt to mmap the library and search for the "C_GetFunctionList" symbol before doing the dlopen. Unfortunately, dlopen allows specifying just the library name and the dynamic linker will search for it, but the new code just tries to open the filename directly. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-28408 -- 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/2028774 Title: ssh fails to load opensc-pkcs11.so Status in openssh package in Ubuntu: New Bug description: I have PKCS11Provider opensc-pkcs11.so in my ~/.ssh/config After the last update of openssh-client I now get: $ strace -o slogin.log slogin host lib_contains_symbol: open opensc-pkcs11.so: No such file or directory provider opensc-pkcs11.so is not a PKCS11 library (uwe@host) Password for uwe@host: $ grep -i pkcs11 slogin.log read(3, "PKCS11Provider opensc-pkcs11.so\n"..., 4096) = 1603 openat(AT_FDCWD, "opensc-pkcs11.so", O_RDONLY) = -1 ENOENT (No such file or directory) write(2, "provider opensc-pkcs11.so is not"..., 51) = 51 $ dpkg-query --listfiles opensc-pkcs11 | grep opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.9p1-3ubuntu0.3 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 26 15:46:30 2023 InstallationDate: Installed on 2022-08-25 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-13 libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.9p1 Ubuntu-3ubuntu0.3, OpenSSL 3.0.2 15 Mar 2022 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2028774/+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 2028774] Re: ssh fails to load opensc-pkcs11.so
Can you try putting the full path to the library in your config file? -- 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/2028774 Title: ssh fails to load opensc-pkcs11.so Status in openssh package in Ubuntu: New Bug description: I have PKCS11Provider opensc-pkcs11.so in my ~/.ssh/config After the last update of openssh-client I now get: $ strace -o slogin.log slogin host lib_contains_symbol: open opensc-pkcs11.so: No such file or directory provider opensc-pkcs11.so is not a PKCS11 library (uwe@host) Password for uwe@host: $ grep -i pkcs11 slogin.log read(3, "PKCS11Provider opensc-pkcs11.so\n"..., 4096) = 1603 openat(AT_FDCWD, "opensc-pkcs11.so", O_RDONLY) = -1 ENOENT (No such file or directory) write(2, "provider opensc-pkcs11.so is not"..., 51) = 51 $ dpkg-query --listfiles opensc-pkcs11 | grep opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.9p1-3ubuntu0.3 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 26 15:46:30 2023 InstallationDate: Installed on 2022-08-25 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-13 libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.9p1 Ubuntu-3ubuntu0.3, OpenSSL 3.0.2 15 Mar 2022 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2028774/+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 2028721] Re: Merge openldap from Debian experimental for mantic
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/447816 ** Changed in: openldap (Ubuntu) Status: New => In Progress -- 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/2028721 Title: Merge openldap from Debian experimental for mantic Status in openldap package in Ubuntu: In Progress Bug description: I uploaded version 2.6.5 to Debian experimental yesterday. This bug is a reminder to merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2028721/+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 2028774] Re: ssh fails to load opensc-pkcs11.so
Can you run fatrace or opensnoop-bpfcc to discover what exact paths are being probed? Thanks -- 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/2028774 Title: ssh fails to load opensc-pkcs11.so Status in openssh package in Ubuntu: New Bug description: I have PKCS11Provider opensc-pkcs11.so in my ~/.ssh/config After the last update of openssh-client I now get: $ strace -o slogin.log slogin host lib_contains_symbol: open opensc-pkcs11.so: No such file or directory provider opensc-pkcs11.so is not a PKCS11 library (uwe@host) Password for uwe@host: $ grep -i pkcs11 slogin.log read(3, "PKCS11Provider opensc-pkcs11.so\n"..., 4096) = 1603 openat(AT_FDCWD, "opensc-pkcs11.so", O_RDONLY) = -1 ENOENT (No such file or directory) write(2, "provider opensc-pkcs11.so is not"..., 51) = 51 $ dpkg-query --listfiles opensc-pkcs11 | grep opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.9p1-3ubuntu0.3 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 26 15:46:30 2023 InstallationDate: Installed on 2022-08-25 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-13 libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.9p1 Ubuntu-3ubuntu0.3, OpenSSL 3.0.2 15 Mar 2022 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2028774/+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 1971242] Autopkgtest regression report (cups/2.4.1op1-1ubuntu4.5)
All autopkgtests for the newly accepted cups (2.4.1op1-1ubuntu4.5) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
libreoffice/blacklisted (s390x)
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/jammy/update_excuses.html#cups
[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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Status in cups source package in Lunar:
Fix Committed
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 2026757] Re: dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates
Hello and thanks for taking the time to report this bug. I read the discussion above and would like to clarify a few things: 1) Does the segfault happen with the dnsmasq package from Lunar/Mantic? I see tasks for both systems added to this bug (and the Mantic one is set as Confirmed), but it's not clear from the messages above whether the failure really happens there. 2) Assuming that the segfault does *not* happen in Lunar/Mantic, I can prepare a PPA with the backported patch from upstream and ask you to test it. 3) If the failure *does* happen in Lunar/Mantic, we will need to investigate it further. FWIW, Kinetic has reached its end of standard support so I will set its task as Won't Fix. Thank you. ** Changed in: dnsmasq (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2026757 Title: dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates Status in Ironic: New Status in neutron: New Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq source package in Jammy: New Status in dnsmasq source package in Kinetic: Won't Fix Status in dnsmasq source package in Lunar: New Status in dnsmasq source package in Mantic: Confirmed Bug description: The Ironic project's CI has been having major blocking issues moving to utilizing Ubuntu Jammy and with some investigation we were able to isolate the issues down to the dhcp updates causing dnsmasq to crash on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds similar to an issue known about to the dnsmasq maintainers, where dnsmasq would crash with updates occurring due to configuration refresh[0]. This resulted in us upgrading dnsmasq to the version which ships with Ubuntu Lunar. Which was no better. Dnsmasq still crashed upon record updates for addresses and ports getting configuration added/changed/removed. We later downgraded to the version of dnsmasq shipped in Ubuntu Focal, and dnsmasq stopped crashing and appeared stable enough to utilize for CI purposes. ** Kernel log from Ubuntu Jammy Package ** [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000] [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000] [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000] [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000] [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000] [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000] [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000] [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a ** Kernel log entries from Ubuntu Lunar package ** [234724.842339] dnsmasq[409843]: segfault at fffd ip 7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000] [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e
[Touch-packages] [Bug 1849859] Re: smb printing fails
In case you are accessing a shared USB printer on a Windows machine I am sharing another workaround: https://askubuntu.com/questions/1039052/always-prompts-for-username-and-password-when-printing Spin up the built in LPD print server via Windows additional features and map the printer on Ubuntu through lpd:// instead of smb:// By the way the "This bug was fixed in the package system-config-printer - 1.5.12-0ubuntu1" did not fix the issue. I am currently on 1.5.12-0ubuntu1.1 and the bug is still there. -- 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/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Fix Released Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 2018074] Re: Merge heimdal from Debian unstable for mantic
7.8.git20221117.28daf24+dfsg-3ubuntu1. Marking fix released.
** Changed in: heimdal (Ubuntu)
Status: New => Fix Released
** Changed in: heimdal (Ubuntu)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/2018074
Title:
Merge heimdal from Debian unstable for mantic
Status in heimdal package in Ubuntu:
Fix Released
Bug description:
Upstream: tbd
Debian: 7.8.git20221117.28daf24+dfsg-2
Ubuntu: 7.8.git20221117.28daf24+dfsg-1ubuntu1
Debian does new releases regularly, so it's likely there will be newer
versions available before FF that we can pick up if this merge is done
later in the cycle.
If it turns out this needs a sync rather than a merge, please change
the tag 'needs-merge' to 'needs-sync', and (optionally) update the
title as desired.
### New Debian Changes ###
heimdal (7.8.git20221117.28daf24+dfsg-2) unstable; urgency=medium
* Fix incorrect license of Debian files.
* Fix deprecated dependancies.
* gsskrb5: fix accidental logic inversions (CVE-2022-45142)
(Closes: #1030849) - change applied from NMU version
7.8.git20221117.28daf24+dfsg-1.1
* Add ro.po file. Closes: #1031897.
-- Brian May Sat, 25 Feb 2023 09:32:57 +1100
heimdal (7.8.git20221117.28daf24+dfsg-1) unstable; urgency=medium
* New upstream release.
-- Brian May Sat, 10 Dec 2022 16:29:20 +1100
heimdal (7.8.git20221115.a6cf945+dfsg-3) unstable; urgency=medium
* Source-only upload to enable migration to testingi (2nd attempt).
-- Brian May Sun, 04 Dec 2022 09:56:06 +1100
heimdal (7.8.git20221115.a6cf945+dfsg-2) unstable; urgency=medium
* Source-only upload to enable migration to testing.
-- Brian May Sun, 04 Dec 2022 09:09:44 +1100
heimdal (7.8.git20221115.a6cf945+dfsg-1) unstable; urgency=medium
* New upstream version.
* Numerous security fixes (Closes: #1024187).
* asn1: Invalid free in ASN.1 codec (CVE-2022-44640)
* krb5: PAC parse integer overflows (CVE-2022-42898)
* gsskrb5: Use constant-time memcmp() for arcfour unwrap (CVE-2022-3437)
* gsskrb5: Use constant-time memcmp() in unwrap_des3() (CVE-2022-3437)
* gsskrb5: Don't pass NULL pointers to memcpy() in DES unwrap
(CVE-2022-3437)
* gsskrb5: Avoid undefined behaviour in _gssapi_verify_pad()
(CVE-2022-3437)
* gsskrb5: Check the result of _gsskrb5_get_mech() (CVE-2022-3437)
* gsskrb5: Check buffer length against overflow for DES{,3} unwrap
(CVE-2022-3437)
* gsskrb5: Check for overflow in _gsskrb5_get_mech() (CVE-2022-3437)
* gsskrb5: Pass correct length to _gssapi_verify_pad() (CVE-2022-3437)
* libhx509: Fix denial of service vulnerability (CVE-2022-41916)
* spnego: send_reject when no mech selected (CVE-2021-44758)
* Fix regression in _krb5_get_int64 on 32 bit systems.
https://github.com/heimdal/heimdal/pull/1025
* Increment soname for libroken.
* Increment soname for libhcrypto.
* Remove legacy shared library version requirements.
* Add symbols to libkadm5srv8.
-- Brian May Sun, 27 Nov 2022 10:44:26 +1100
heimdal (7.7.0+dfsg-6) unstable; urgency=medium
* Retry deleting dangling windc.so again. Closes: #857215.
* Create /var/lib/heimdal-kdc/m-key not /var/lib/heimdal-kdc/heimdal.mkey.
Closes: #964008.
* Disable use of -rpath in krb5-config.heimdal. Closes: #868840.
-- Brian May Mon, 05 Sep 2022 08:35:33 +1000
heimdal (7.7.0+dfsg-5) unstable; urgency=medium
* Fix missing closefrom symbol. Closes: #1016884, #1017244.
* Fix spelling of dependency in changelog.
* Fix override_dh_fixperms typo, use 700 for /var/lib/heimdal-kdc/
* Remove default --parallel from dh call.
* Remove unused debian/upstream/signing-key.asc key.
* Fix Multi-Arch headers. heimdal-multidev is not co-installable, so
heimdal-dev cannot be co-installable either.
-- Brian May Fri, 02 Sep 2022 07:59:59 +1000
heimdal (7.7.0+dfsg-4) unstable; urgency=medium
* Delete dependency on install-info. Closes: #1013735.
* Non-maintainer upload.
* Reduce Build-Depends: (Closes: #980531)
+ Drop unused libhesiod-dev.
+ Drop unused libperl4-corelibs-perl as cf/make-proto.pl no longer uses
it.
+ Drop unused libx11-dev, libxau-dev, libxt-dev, ss-dev, and
x11proto-core-dev.
+ Clean generated C tables to actually rebuild them using python3.
-- Brian May Mon, 27 Jun 2022 10:36:10 +1000
heimdal (7.7.0+dfsg-3) unstable; urgency=high
* Fix CVE-2021-3671: A null pointer de-reference was found in the way
samba kerberos server handled missing sname in TGS-REQ. Closes: #996586.
* Fix autoconf 2.7 issues.
-- Brian May Wed, 17 Nov 2021 12:12:45 +1100
### Old Ubuntu Delta ###
heimdal
[Touch-packages] [Bug 2018074] Re: Merge heimdal from Debian unstable for mantic
7.8.git20221117.28daf24+dfsg-3 was already merged, nothing new for now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/2018074
Title:
Merge heimdal from Debian unstable for mantic
Status in heimdal package in Ubuntu:
Fix Released
Bug description:
Upstream: tbd
Debian: 7.8.git20221117.28daf24+dfsg-2
Ubuntu: 7.8.git20221117.28daf24+dfsg-1ubuntu1
Debian does new releases regularly, so it's likely there will be newer
versions available before FF that we can pick up if this merge is done
later in the cycle.
If it turns out this needs a sync rather than a merge, please change
the tag 'needs-merge' to 'needs-sync', and (optionally) update the
title as desired.
### New Debian Changes ###
heimdal (7.8.git20221117.28daf24+dfsg-2) unstable; urgency=medium
* Fix incorrect license of Debian files.
* Fix deprecated dependancies.
* gsskrb5: fix accidental logic inversions (CVE-2022-45142)
(Closes: #1030849) - change applied from NMU version
7.8.git20221117.28daf24+dfsg-1.1
* Add ro.po file. Closes: #1031897.
-- Brian May Sat, 25 Feb 2023 09:32:57 +1100
heimdal (7.8.git20221117.28daf24+dfsg-1) unstable; urgency=medium
* New upstream release.
-- Brian May Sat, 10 Dec 2022 16:29:20 +1100
heimdal (7.8.git20221115.a6cf945+dfsg-3) unstable; urgency=medium
* Source-only upload to enable migration to testingi (2nd attempt).
-- Brian May Sun, 04 Dec 2022 09:56:06 +1100
heimdal (7.8.git20221115.a6cf945+dfsg-2) unstable; urgency=medium
* Source-only upload to enable migration to testing.
-- Brian May Sun, 04 Dec 2022 09:09:44 +1100
heimdal (7.8.git20221115.a6cf945+dfsg-1) unstable; urgency=medium
* New upstream version.
* Numerous security fixes (Closes: #1024187).
* asn1: Invalid free in ASN.1 codec (CVE-2022-44640)
* krb5: PAC parse integer overflows (CVE-2022-42898)
* gsskrb5: Use constant-time memcmp() for arcfour unwrap (CVE-2022-3437)
* gsskrb5: Use constant-time memcmp() in unwrap_des3() (CVE-2022-3437)
* gsskrb5: Don't pass NULL pointers to memcpy() in DES unwrap
(CVE-2022-3437)
* gsskrb5: Avoid undefined behaviour in _gssapi_verify_pad()
(CVE-2022-3437)
* gsskrb5: Check the result of _gsskrb5_get_mech() (CVE-2022-3437)
* gsskrb5: Check buffer length against overflow for DES{,3} unwrap
(CVE-2022-3437)
* gsskrb5: Check for overflow in _gsskrb5_get_mech() (CVE-2022-3437)
* gsskrb5: Pass correct length to _gssapi_verify_pad() (CVE-2022-3437)
* libhx509: Fix denial of service vulnerability (CVE-2022-41916)
* spnego: send_reject when no mech selected (CVE-2021-44758)
* Fix regression in _krb5_get_int64 on 32 bit systems.
https://github.com/heimdal/heimdal/pull/1025
* Increment soname for libroken.
* Increment soname for libhcrypto.
* Remove legacy shared library version requirements.
* Add symbols to libkadm5srv8.
-- Brian May Sun, 27 Nov 2022 10:44:26 +1100
heimdal (7.7.0+dfsg-6) unstable; urgency=medium
* Retry deleting dangling windc.so again. Closes: #857215.
* Create /var/lib/heimdal-kdc/m-key not /var/lib/heimdal-kdc/heimdal.mkey.
Closes: #964008.
* Disable use of -rpath in krb5-config.heimdal. Closes: #868840.
-- Brian May Mon, 05 Sep 2022 08:35:33 +1000
heimdal (7.7.0+dfsg-5) unstable; urgency=medium
* Fix missing closefrom symbol. Closes: #1016884, #1017244.
* Fix spelling of dependency in changelog.
* Fix override_dh_fixperms typo, use 700 for /var/lib/heimdal-kdc/
* Remove default --parallel from dh call.
* Remove unused debian/upstream/signing-key.asc key.
* Fix Multi-Arch headers. heimdal-multidev is not co-installable, so
heimdal-dev cannot be co-installable either.
-- Brian May Fri, 02 Sep 2022 07:59:59 +1000
heimdal (7.7.0+dfsg-4) unstable; urgency=medium
* Delete dependency on install-info. Closes: #1013735.
* Non-maintainer upload.
* Reduce Build-Depends: (Closes: #980531)
+ Drop unused libhesiod-dev.
+ Drop unused libperl4-corelibs-perl as cf/make-proto.pl no longer uses
it.
+ Drop unused libx11-dev, libxau-dev, libxt-dev, ss-dev, and
x11proto-core-dev.
+ Clean generated C tables to actually rebuild them using python3.
-- Brian May Mon, 27 Jun 2022 10:36:10 +1000
heimdal (7.7.0+dfsg-3) unstable; urgency=high
* Fix CVE-2021-3671: A null pointer de-reference was found in the way
samba kerberos server handled missing sname in TGS-REQ. Closes: #996586.
* Fix autoconf 2.7 issues.
-- Brian May Wed, 17 Nov 2021 12:12:45 +1100
### Old Ubuntu Delta ###
heimdal (7.8.git20221117.28daf24+dfsg-1ubuntu1) lunar; urgency=low
* Merge from Debian unstable. Remaining changes:
- d/rules: Disable lto, to
[Touch-packages] [Bug 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
** Merge proposal linked: https://code.launchpad.net/~xypron/ubuntu/+source/ubuntu-meta/+git/ubuntu-meta/+merge/447802 -- 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/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 1978079] Re: EFI pstore not cleared on boot
** Also affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-bluefield (Ubuntu Impish) ** No longer affects: linux-bluefield (Ubuntu Kinetic) ** Changed in: linux-bluefield (Ubuntu) Assignee: (unassigned) => William Tu (wtu) ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => William Tu (wtu) ** Changed in: linux-bluefield (Ubuntu Jammy) Assignee: (unassigned) => William Tu (wtu) -- 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/1978079 Title: EFI pstore not cleared on boot Status in linux-bluefield package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in linux-bluefield source package in Focal: New Status in systemd source package in Focal: Fix Released Status in systemd source package in Impish: Won't Fix Status in linux-bluefield source package in Jammy: New Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] Systemd has a systemd-pstore component that scans the pstore on boot and if non-empty, takes all previously created dumps, transfers them into its journal and removes the pstore elements. This is very important on UEFI systems, which only have a limited amount of space for variables. In Ubuntu, the kernel is configured with CONFIG_EFI_VARS_PSTORE=m which means the EFI pstore support gets loaded dynamically. In all of my boots, this dynamic module loading happened *after* systemd tried to check for pstore variables. So systemd-pstore never starts and never clears the UEFI variable store. I see this happening in AWS on Graviton instances, which eventually run out of space to store the dumps. On real hardware, this behavior may lead to unbootable systems. ``` $ systemctl status systemd-pstore ○ systemd-pstore.service - Platform Persistent Storage Archival Loaded: loaded (/lib/systemd/system/systemd-pstore.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Thu 2022-06-09 09:11:41 UTC; 29min ago └─ ConditionDirectoryNotEmpty=/sys/fs/pstore was not met Docs: man:systemd-pstore(8) Jun 09 09:11:41 ip-172-31-0-61 systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. $ ls -la /sys/fs/pstore total 0 drwxr-x--- 2 root root0 Jun 9 09:11 . drwxr-xr-x 8 root root0 Jun 9 09:11 .. -r--r--r-- 1 root root 1803 Jun 9 09:07 dmesg-efi-165476562001001 -r--r--r-- 1 root root 1777 Jun 9 09:07 dmesg-efi-165476562002001 -r--r--r-- 1 root root 1773 Jun 9 09:07 dmesg-efi-165476562003001 -r--r--r-- 1 root root 1815 Jun 9 09:07 dmesg-efi-165476562004001 -r--r--r-- 1 root root 1826 Jun 9 09:07 dmesg-efi-165476562005001 -r--r--r-- 1 root root 1754 Jun 9 09:07 dmesg-efi-165476562006001 -r--r--r-- 1 root root 1821 Jun 9 09:07 dmesg-efi-165476562007001 -r--r--r-- 1 root root 1767 Jun 9 09:07 dmesg-efi-165476562008001 -r--r--r-- 1 root root 1729 Jun 9 09:07 dmesg-efi-165476562009001 -r--r--r-- 1 root root 1819 Jun 9 09:07 dmesg-efi-165476562010001 -r--r--r-- 1 root root 1767 Jun 9 09:07 dmesg-efi-165476562011001 -r--r--r-- 1 root root 1775 Jun 9 09:07 dmesg-efi-165476562012001 -r--r--r-- 1 root root 1802 Jun 9 09:07 dmesg-efi-165476562013001 -r--r--r-- 1 root root 1812 Jun 9 09:07 dmesg-efi-165476562014001 -r--r--r-- 1 root root 1764 Jun 9 09:07 dmesg-efi-165476562015001 -r--r--r-- 1 root root 1795 Jun 9 09:11 dmesg-efi-165476589801001 -r--r--r-- 1 root root 1785 Jun 9 09:11 dmesg-efi-165476589802001 -r--r--r-- 1 root root 1683 Jun 9 09:11 dmesg-efi-165476589803001 -r--r--r-- 1 root root 1785 Jun 9 09:11 dmesg-efi-165476589804001 -r--r--r-- 1 root root 1771 Jun 9 09:11 dmesg-efi-165476589805001 -r--r--r-- 1 root root 1797 Jun 9 09:11 dmesg-efi-165476589806001 -r--r--r-- 1 root root 1805 Jun 9 09:11 dmesg-efi-165476589807001 -r--r--r-- 1 root root 1781 Jun 9 09:11 dmesg-efi-165476589808001 -r--r--r-- 1 root root 1806 Jun 9 09:11 dmesg-efi-165476589809001 -r--r--r-- 1 root root 1821 Jun 9 09:11 dmesg-efi-165476589810001 -r--r--r-- 1 root root 1763 Jun 9 09:11 dmesg-efi-165476589811001 -r--r--r-- 1 root root 1783 Jun 9 09:11 dmesg-efi-165476589812001 -r--r--r-- 1 root root 1788 Jun 9 09:11 dmesg-efi-165476589813001 -r--r--r-- 1 root root 1788 Jun 9 09:11 dmesg-efi-165476589814001 -r--r--r-- 1 root root 1786 Jun 9 09:11 dmesg-efi-165476589815001 ``` This problem affects (at least) Ubuntu 20.04 and 22.04. A quick fix would be to configure CONFIG_EFI_VARS_PSTORE=y so that it's always available. A long term fix would make systemd rescan the directory after all module probing settled. [Test Plan] In order
Re: [Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
As far as I know, Xvfb and --headless result in quite different environments, as the first will run in normal graphical mode and the latter won't. I see no reason why this would affect your extension packing, however I have no experience with extensions in Chromium. Could the graphical environment be playing a role here? Did you try the natural ---> xvfb-run /snap/bin/chromium --class="ChrUnsnapped" --pack-extension=MyExt --pack-extension-key=MyExt.pem <--- instead? The snap won't have access to the system's /tmp, but I think you can work around that, at least for the sake of testing. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Is there any progress on this issue? (Progress as in: works for end- users as it did the last 20 years…) -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Invalid Status in GTK+: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 2027079] Re: New upstream microrelease 2.5.15
This bug was fixed in the package openldap - 2.5.15+dfsg-0ubuntu0.22.04.1 --- openldap (2.5.15+dfsg-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream version (LP: #2027079). - Several fixes, including to asynchronous connections to the OpenLDAP server. -- Sergio Durigan Junior Tue, 11 Jul 2023 15:26:41 -0400 ** Changed in: openldap (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 openldap in Ubuntu. https://bugs.launchpad.net/bugs/2027079 Title: New upstream microrelease 2.5.15 Status in openldap package in Ubuntu: Invalid Status in openldap source package in Jammy: Fix Released Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.15. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/ZQC6MWMJMETDFWV3UHDKESBFPHHTNO5S/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/commit/d0fbbc3599148e1033218ec097bf5ab5f6236c76/pipelines?ref=OPENLDAP_REL_ENG_2_5_15 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/message/HUNFQO6GJR7CCJAYKMTRXE44ZPHBKKMD/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in a PPA and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: - https://launchpadlibrarian.net/676793029/buildlog_ubuntu-jammy-amd64.openldap_2.5.15+dfsg-0ubuntu0.22.04.1_BUILDING.txt.gz [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in supported releases that got updates: openldap | 2.5.14+dfsg-0ubuntu0.22.04.2 | jammy-updates | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 - https://pad.lv/1983618 - https://pad.lv/2007625 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2027079/+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 2027079] Update Released
The verification of the Stable Release Update for openldap 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 openldap in Ubuntu. https://bugs.launchpad.net/bugs/2027079 Title: New upstream microrelease 2.5.15 Status in openldap package in Ubuntu: Invalid Status in openldap source package in Jammy: Fix Released Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.15. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/ZQC6MWMJMETDFWV3UHDKESBFPHHTNO5S/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/commit/d0fbbc3599148e1033218ec097bf5ab5f6236c76/pipelines?ref=OPENLDAP_REL_ENG_2_5_15 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/message/HUNFQO6GJR7CCJAYKMTRXE44ZPHBKKMD/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in a PPA and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: - https://launchpadlibrarian.net/676793029/buildlog_ubuntu-jammy-amd64.openldap_2.5.15+dfsg-0ubuntu0.22.04.1_BUILDING.txt.gz [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in supported releases that got updates: openldap | 2.5.14+dfsg-0ubuntu0.22.04.2 | jammy-updates | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 - https://pad.lv/1983618 - https://pad.lv/2007625 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2027079/+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 1942260] Re: compress firmware in /lib/firmware
Both linux-firmware patches were accepted upstream. Upstream currently does not set a compression level and has no way to specify it. -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+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 2017401] Re: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled
** Tags added: rls-ff-incoming rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2017401 Title: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Following the resolution for bug #1747499, after a kernel upgrade when Livepatch is enabled, the current behaviour in unattended-upgrades (2.3ubuntu0.2 and later) is not to touch /var/run/reboot-required so as not to confuse users with two separate messages calling for a restart in motd. This functionality is implemented in the script at /etc/kernel/postinst.d/unattended-upgrades. While this works as intended in terms of suppressing an extra message in motd, it defeats the ability of unattended-upgrades to restart automatically with the new kernel, which is reliant on /var/run/reboot-required being present. This is unexpected / unwanted behaviour in scenarios where a) Livepatch is being used to provide fast-response kernel patching; and b) Unattended-Upgrade::Automatic-Reboot is set to true, to enable automatic reboots during a regular maintenance window. In this case, without administrative intervention, the system could never boot into the new kernel even though it would be expected to, leaving Livepatch to do all the heavy lifting indefinitely, and unnecessarily. I believe this counts as a regression caused by the resolution to bug #1747499. It also has the potential to be a security threat if Livepatch doesn't work comprehensively for a particular kernel flaw, and an administrator is reliant on expected behaviour according to unattended-upgrades settings. Potential options for a fix that come to mind: 1. Revert to original behaviour in /etc/kernel/postinst.d/unattended-upgrades, and change the ***System restart required*** message to be less alarming or confusing when the cause is a kernel upgrade that's being patched by Livepatch. 2. Add an extra configuration setting (eg Unattended-Upgrade::Automatic-Reboot-After-Livepatch) that triggers a reboot when it's 'recommended' by Livepatch, not reliant on the presence of /var/run/reboot-required. 3. Add support in /etc/kernel/postinst.d/unattended-upgrades for an extra file somewhere. When present, /var/run/reboot-required is always touched, even if Livepatch is enabled. (This is my first time reporting a bug in this system, and I apologise if I haven't followed the usual descriptive format.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2017401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932329] Re: Support compressed kernel modules in initramfs-tools and kernel
moving linux tasks to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568 ** No longer affects: linux (Ubuntu Jammy) ** No longer affects: linux (Ubuntu) -- 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/1932329 Title: Support compressed kernel modules in initramfs-tools and kernel Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: New Status in initramfs-tools source package in Impish: Won't Fix Status in initramfs-tools source package in Jammy: Fix Released Bug description: --- initramfs-tools [Impact] * Initramfs-tools already supports compressed kernel modules. However, in focal and impish it does so inefficiently. It is always better to have a compressed initramfs of uncommpressed kernel modules, than a compressed initrd of compressed kernel modules. Thus when kernel module compression is turned on, it is prudent for initramfs- tools to pre-uncompress kernel modules when building initramfs. [Test Plan] * Compress all kernel modules with xz for a current kernel, check that all of them have .ko.xz extension and no .ko ones available * Rerun depmod * Update initramfs with update-initramfs -u * lsinitramfs contents and check that all kernel modules are present, and are uncompressed (.ko extension) [Where problems could occur] * This optimization for compressed kernel modules will make initramfs build time longer (due to decompression) whilst improving bootspeed (overall smaller size of the initrd). [Other Info] * Original bug report re kernel feature --- linux Symbol: MODULE_COMPRESS_ZSTD [=n] Type : bool = Impacts to measure and observe = == Disk space == * Inspect linux-modules-* and linux-modules-extra* deb package Installed-Size and Download-Size changes, i.e. $ apt show linux-modules-5.8.0-53-generic linux-modules- extra-5.8.0-53-generic | grep -e Package: -e Size: Package: linux-modules-5.8.0-53-generic Installed-Size: 81.5 MB Download-Size: 15.5 MB Package: linux-modules-extra-5.8.0-53-generic Installed-Size: 215 MB Download-Size: 41.5 MB In theory, there should not be a significant change in the Download- size. It is desired that there is a significant reduction in Installed-Size. Modules take up about 300MB and normally one has upto three kernel version installed, resulting in about of 1GB of disk space that one constantly pays for. == Boot Speed == In theory, boot speed may either improve or regress. It depends if disk IO is slower than decompression speed, meaning loading compressed modules is faster. Also one has to observe the changes in the initrd size. zstd(zstd) compression may result in slight growth, which shouldn't impact boot speed too much. = Outcomes = If installed size savings can be achieved without regressing bootspeed we should enable CONFIG_MODULE_COMPRESS_ZSTD=y by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932329/+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 305837] Re: No dots in script filenames?
This change was applied in commit
97f26c6e0d61a4ff700b8f79c61a41320f317e2e and released in initramfs-tools
0.93.2.
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/305837
Title:
No dots in script filenames?
Status in initramfs-tools package in Ubuntu:
Fix Released
Bug description:
Binary package hint: initramfs-tools
Hi,
Files placed in the scripts directory can no longer have a dot in
their names (i.e. no script.sh files in there). This worked in Hardy.
Is there a reason for this?
A friend pasted me this patch, but I think it may need more than just
the dot in the expression (spacing may be badly messed up):
--- /usr/sbin/mkinitramfs.orig 2008-07-16 12:09:55.0 +0200
+++ /usr/sbin/mkinitramfs 2008-11-29 23:09:09.0 +0100
-232,7 +232,7 @@
"${DESTDIR}/scripts/$(dirname "${b}")/"
done
for b in $(cd "${CONFDIR}/scripts" && find . \
- -regextype posix-extended -regex '.*/[[:alnum:]_]+$' -type f); do
+ -regextype posix-extended -regex '.*/[[:alnum:]_.]+$' -type f); do
[ -d "${DESTDIR}/scripts/$(dirname "${b}")" ] \
|| mkdir -p "${DESTDIR}/scripts/$(dirname "${b}")"
cp -p "${CONFDIR}/scripts/${b}" "${DESTDIR}/scripts/$(dirname
"${b}")/"
--- /usr/share/initramfs-tools/scripts/functions.orig 2008-10-01
15:15:48.0 +0200
+++ /usr/share/initramfs-tools/scripts/functions2008-11-29
23:50:52.0 +0100
-110,7 +110,7 @@
# only allow variable name chars
case ${si_x#${initdir}/} in
- *[![:alnum:]_]*)
+ *[![:alnum:]_.]*)
[ "${verbose}" = "y" ] \
&& echo "$si_x ignored: not alphanumeric or '_' file"
continue
Hardy didn't seem to use regular expressions at all.
I think a bug report like LP:78348 that prompted such a change, but I
can't see anything specific to this change in the changelog.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/305837/+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 2028774] [NEW] ssh fails to load opensc-pkcs11.so
Public bug reported: I have PKCS11Provider opensc-pkcs11.so in my ~/.ssh/config After the last update of openssh-client I now get: $ strace -o slogin.log slogin host lib_contains_symbol: open opensc-pkcs11.so: No such file or directory provider opensc-pkcs11.so is not a PKCS11 library (uwe@host) Password for uwe@host: $ grep -i pkcs11 slogin.log read(3, "PKCS11Provider opensc-pkcs11.so\n"..., 4096) = 1603 openat(AT_FDCWD, "opensc-pkcs11.so", O_RDONLY) = -1 ENOENT (No such file or directory) write(2, "provider opensc-pkcs11.so is not"..., 51) = 51 $ dpkg-query --listfiles opensc-pkcs11 | grep opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.9p1-3ubuntu0.3 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 26 15:46:30 2023 InstallationDate: Installed on 2022-08-25 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-13 libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.9p1 Ubuntu-3ubuntu0.3, OpenSSL 3.0.2 15 Mar 2022 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/2028774 Title: ssh fails to load opensc-pkcs11.so Status in openssh package in Ubuntu: New Bug description: I have PKCS11Provider opensc-pkcs11.so in my ~/.ssh/config After the last update of openssh-client I now get: $ strace -o slogin.log slogin host lib_contains_symbol: open opensc-pkcs11.so: No such file or directory provider opensc-pkcs11.so is not a PKCS11 library (uwe@host) Password for uwe@host: $ grep -i pkcs11 slogin.log read(3, "PKCS11Provider opensc-pkcs11.so\n"..., 4096) = 1603 openat(AT_FDCWD, "opensc-pkcs11.so", O_RDONLY) = -1 ENOENT (No such file or directory) write(2, "provider opensc-pkcs11.so is not"..., 51) = 51 $ dpkg-query --listfiles opensc-pkcs11 | grep opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.9p1-3ubuntu0.3 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 26 15:46:30 2023 InstallationDate: Installed on 2022-08-25 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-13 libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.9p1 Ubuntu-3ubuntu0.3, OpenSSL 3.0.2 15 Mar 2022 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2028774/+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 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
Merge request https://code.launchpad.net/~xypron/ubuntu/+source/ubuntu-meta/+git/ubuntu-meta/+merge/447779 -- 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/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
** Merge proposal linked: https://code.launchpad.net/~xypron/ubuntu/+source/ubuntu-meta/+git/ubuntu-meta/+merge/447779 -- 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/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 2028769] [NEW] [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
Public bug reported: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal + [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy -- 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/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 2028767] Re: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwe
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/2028767 Title: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in initramfs-tools package in Ubuntu: Invalid Bug description: error code 1 I don't find a documentation for this error code ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.2 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: amd64-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jul 26 13:53:55 2023 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2023-05-20 (67 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, unpackaged RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück 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/2028767/+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 2028767] [NEW] package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehler
Public bug reported: error code 1 I don't find a documentation for this error code ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.2 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: amd64-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jul 26 13:53:55 2023 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2023-05-20 (67 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, unpackaged RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2028767 Title: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in initramfs-tools package in Ubuntu: New Bug description: error code 1 I don't find a documentation for this error code ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.2 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: amd64-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jul 26 13:53:55 2023 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2023-05-20 (67 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, unpackaged RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück 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/2028767/+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 2028187] Re: Bluetooth audio locked to device disallows other devices to use Bluetooth speaker
** Package changed: ubuntu => bluez (Ubuntu) -- 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/2028187 Title: Bluetooth audio locked to device disallows other devices to use Bluetooth speaker Status in bluez package in Ubuntu: New Bug description: Not sure which layer is causing this. I switch bluetooth audio sources going to my AVR frequently throughout the day. After an update, Ubuntu seems to continue sending something like a keepalive to the bluetooth receiver despite no audio being played on the computer. This prohibits switching to my phone as the audio source. For example if I play a youtube video in Chrome, and then stop the video and then play Amazon Music or Spotify, the device is connected but I get no audio. If I close Chrome, no change. If I disconnect Ubuntu from that bluetooth device, audio starts coming through. No change to bluetooth receiver, but there was a Samsung update the other day. Interestingly, I disconnected Ubuntu from my BT device. Connected my phone, played some audio, then disconnected my phone from the BT device. Ubuntu then automatically connected back to that BT device and prohibits my phone from using it. This was clearly a change to the bluetooth stack that doesn't release the BT device when audio is stopped by the application. Linux gnosis 5.15.0-76-generic #83 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2028187/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
This breaks our command-line pack of an in-house extension, under Ubuntu 20.04. Is there a way to do this using the confined run? Our current unconfined run build command-line (please excuse legacy from years ago, eg --headless might be more appropriate now): xvfb-run /snap/chromium/current/usr/lib/chromium-browser/chrome --user- data-dir=/tmp/ChrUnsnapped --class="ChrUnsnapped" --pack-extension=MyExt --pack-extension-key=MyExt.pem This understandably gets libm GLIBC version errors with a core22 dependent chromium snap. Trying with confinement and --headless (and files moved to a subdirectory of /home/): user@host:~/tmp/ChromeExtensions$ /snap/bin/chromium --headless --enable-logging=stderr --pack-extension=MyExt --pack-extension-key=MyExt.pem [0726/200919.476268:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process. [0726/200919.543209:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable. user@host:~/tmp/ChromeExtensions$ echo $? 0 Sadly no .crx comes out that I can find. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2004551] Re: upgrade to lunar fails due to rescue-ssh.target or port 22 takeover
@Steve Since the machines original use case is blocked until we know if we can go on. Is the above enough for your to have a deeper look together with us? If so please let Miriam know when once she can reset the machine to go on with the MRE verifications that this was supposed to do :-) -- 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/2004551 Title: upgrade to lunar fails due to rescue-ssh.target or port 22 takeover Status in openssh package in Ubuntu: New Bug description: Hi, I just upgraded a system from Jammy to Lunar and openssh-server refuses to upgrade well. Setting up openssh-server (1:9.0p1-1ubuntu8) ... Replacing config file /etc/ssh/sshd_config with new version Replacing config file /etc/ssh/sshd_config with new version Synchronizing state of ssh.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install disable ssh rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.11.2-1) ... Processing triggers for libc-bin (2.36-0ubuntu4) ... Errors were encountered while processing: openssh-server Error: Timeout was reached needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) I'm not sure what exactly it is. This output complains about rescue-ssh.target and indeed that can not be started even directly. $ sudo systemctl start rescue-ssh.target A dependency job for rescue-ssh.target failed. See 'journalctl -xe' for details. And in postinst is a try to start it: $ grep rescue /var/lib/dpkg/info/openssh-server.postinst deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null || true But I think the underlying issue is that ssh is already on, and I'm logged in via it. And that makes the service restart of the ssh socket which was added break. Feb 02 10:40:56 node-horsea systemd[104560]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed with result 'resources'. Now, whichever it is, it is hard to resolve. The only way to get the socket to own it would be rebooting so that sshd lets go and systemd can take over. I could reboot, but that is not the point. What if I'd want to get the service and upgrade completed before reboot. Because as of now dpkg considers the system unhappy, and that would usually be a sign for "better not reboot before being resolved" to me. One thing though, I have not upgraded with do-release-upgrade - would we / do we have magic there to make the ssh socket activation transition smoother? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2004551/+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 2024499] Re: sound stopped after upgraded to lunar lobster
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/2024499 Title: sound stopped after upgraded to lunar lobster Status in alsa-driver package in Ubuntu: Confirmed Bug description: when alsamixer is started in terminal, the "default" driver seems to be "Pipewire" whereas F6 allows to see the HAD Intel PCH. However there is no maneuver that will switch to the correct driver as a consequence, pavucontrol shows "no output device"... while in configurations the only device is the "dummy" one. All recent posts in the fora about this similar problem have been tried but with no avail. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-45.46-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: csrabak 32413 F alsamixer /dev/snd/seq:csrabak 30491 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 20 16:51:10 2023 InstallationDate: Installed on 2020-10-22 (971 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR: PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-06-19 (1 days ago) dmi.bios.date: 06/20/2019 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0W83FH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd06/20/2019:br1.8:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA00:cvnDellInc.:ct10:cvr:sku08A6: dmi.product.family: Inspiron dmi.product.name: Inspiron 7580 dmi.product.sku: 08A6 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-06-16T13:26:54.846163 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2024499/+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 2028282] Re: SSH pubkey authetication fails when GSSAPI enabled
Unsetting KRB5CCNAME breaks the Kerbreros based login, so it is really just an emergency workaround. -- 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/2028282 Title: SSH pubkey authetication fails when GSSAPI enabled Status in openssh package in Ubuntu: Triaged Bug description: Since the upgrade from Ubuntu 20.04 to 22.04 the SSH login via a SSH pubkey to our servers fails, while password and kerberos are still working. $ssh user@server sign_and_send_pubkey: internal error: initial hostkey not recorded This seem related to the bugreport at openssh: https://bugzilla.mindrot.org/show_bug.cgi?id=3406 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Jul 20 17:25:01 2023 InstallationDate: Installed on 2020-08-24 (1060 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: openssh UpgradeStatus: Upgraded to jammy on 2023-07-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2028282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: apparmor (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Committed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
