[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Fix released for Firrefox (Nightly) 125. Since a few days, I can't launch Gpodder (podcast program) anymore, is it also related to this bug or is it something different ? "[gpodder.log] ERROR: Uncaught exception: Traceback (most recent call last): File "/usr/bin/gpodder", line 181, in main() File "/usr/bin/gpodder", line 173, in main from gpodder.gtkui import app File "/usr/lib/python3/dist-packages/gpodder/gtkui/app.py", line 31, in from gpodder import core, util File "/usr/lib/python3/dist-packages/gpodder/core.py", line 25, in from gpodder import config, dbsqlite, extensions, model, util File "/usr/lib/python3/dist-packages/gpodder/extensions.py", line 34, in import imp ModuleNotFoundError: No module named 'imp' Traceback (most recent call last): File "/usr/bin/gpodder", line 181, in main() File "/usr/bin/gpodder", line 173, in main from gpodder.gtkui import app File "/usr/lib/python3/dist-packages/gpodder/gtkui/app.py", line 31, in from gpodder import core, util File "/usr/lib/python3/dist-packages/gpodder/core.py", line 25, in from gpodder import config, dbsqlite, extensions, model, util File "/usr/lib/python3/dist-packages/gpodder/extensions.py", line 34, in import imp ModuleNotFoundError: No module named 'imp'" -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 468343] Re: blkid does not read non-ASCII characters from NTFS labels
[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: util-linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/468343 Title: blkid does not read non-ASCII characters from NTFS labels Status in util-linux package in Ubuntu: Expired Bug description: Binary package hint: hal When plugging in an external harddrive with an NTFS filesystem with a label set to contain UTF-8 characters, the mounted path as well as the label displayed in nautilus are incorrect. The label reported by ntfs-3g are always correct. The labels are set with the command ntfslabel. Some different examples follows: NTFS label # HAL label discovered # Label used in Nautilus / Filesystem path (/media/...) = dong # dong# dong 東西 # 55# ?? Å# % # 4A12287F1228725D dong西 # dong% # dong? dongÅ# dong% # dong dong西xi# dong%xi # dong?xi dongÅxi # dong%xi # dong Examining the above table shows that depending on what Unicode character the file system path and label shown in nautilus differ. The behaviour of hal is also a bit odd. When a chinese character is used together with a ASCII character, hal with read it as '%', while nautilus and the path as '?'. When the swedish character 'Å' is used together with ASCII characters, hal with do the same as with chinese characters, but nautilus and the path will simply truncate everything including and after the swedish character. If only chinese characters are used, hal with read them as the number '5'. '東西' is translated into '55'. ‘東西南北’ translates to ''. When only swedish characters are used, hal will read them in as '%', while the path as well as the label presented in nautilus will be something looking like a large random identifier number. In Ubuntu 9.04, these issues did not exist. A NTFS partition with label 東西 would automatically mount into /media/東西/, and would be presented correctly in nautilus. The issue occurred immediately after upgrading to Ubuntu 9.10. Setting the label is done with the command ntfslabel. Reading hal values is done with the command hal-devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/468343/+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 1045062] Re: No option to save without BOM (Byte Order Mark)
[Expired for nano (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nano (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1045062 Title: No option to save without BOM (Byte Order Mark) Status in nano package in Ubuntu: Expired Bug description: This may be a wishlist type bug. Currently, Nano in precise saves with BOM (Byte Order Mark) by default. There is no way within nano to save without BOM, which requires me to download remote server documents to this system and then update and reupload the documents after using gedit, kate, or some other editor. This sometimes screws up remote PHP programs and scripts, which means it may be prudent to give the option to decide whether to save with or without the Byte Order Mark. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nano 2.2.6-1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Sep 2 14:36:54 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1045062/+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 294871] Re: fdisk gives an incomplete list of partitions
[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: util-linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/294871 Title: fdisk gives an incomplete list of partitions Status in util-linux package in Ubuntu: Expired Bug description: I use Ubuntu Intrepid on Acer Aspire One A110L and are trying to use both built-in card readers. When the netbook is booted with both readers containing SD cards, both cards are mounted and can be used. However, the command "fdisk -l" shows only the SSD (which in my system contains two partitions, one for root, and one for swap): Platte /dev/sda: 8069 MByte, 8069677056 Byte 255 Köpfe, 63 Sektoren/Spuren, 981 Zylinder Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes Disk identifier: 0x0007da04 Gerät boot. AnfangEnde Blöcke Id System /dev/sda1 * 1 850 6827593+ 83 Linux /dev/sda2 851 981 1052257+ 82 Linux Swap / Solaris You will notice that none of the SD cards are listed. mount says about them: /dev/mmcblk0p1 on /media/SANVOL type vfat (ro,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush) /dev/mmcblk1p1 on /media/disk type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush) This is what the "man fdisk" is saying about the "-l" option to fdisk: -l List the partition tables for the specified devices and then exit. If no devices are given, those men‐ tioned in /proc/partitions (if that exists) are used. However, the /proc/partitions contain: cat /proc/partitions: major minor #blocks name 8 07880544 sda 8 16827593 sda1 8 21052257 sda2 179 0 128000 mmcblk0 179 1 127968 mmcblk0p1 179 8 15694336 mmcblk1 179 9 15690240 mmcblk1p1 Obviously, fdisk gives an incomplete list of partitions, inconsistent with its stated behaviour, since all mmcbl* partitions are missing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/294871/+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 2057924] Re: Display after a computer sleep
*** This bug is a duplicate of bug 1961508 *** https://bugs.launchpad.net/bugs/1961508 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1961508, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1961508 Dock displaying over window after resuming from blank screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2057924 Title: Display after a computer sleep Status in mutter package in Ubuntu: New Bug description: After a computer sleep, each window appear under the dock launcher. See the attachment for and example. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 13:06:45 2024 DistUpgraded: 2022-08-14 08:22:53,939 ERROR Cache can not be locked (E:Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 35271 (jammy), W:Be aware that removing the lock file is not a solution and may break your system., E:Impossible d'obtenir le verrou de dpkg (/var/lib/dpkg/lock-frontend). Il est possible qu'un autre processus l'utilise.) DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0816] InstallationDate: Installed on 2021-03-01 (1108 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=2243852e-cb82-44e5-9287-eb132a652223 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-14 (578 days ago) dmi.bios.date: 12/12/2023 dmi.bios.release: 1.33 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.33.0 dmi.board.name: 0DH2HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd12/12/2023:br1.33:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn0DH2HV:rvrA00:cvnDellInc.:ct10:cvr:sku0816: dmi.product.family: Latitude dmi.product.name: Latitude 5490 dmi.product.sku: 0816 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2057924/+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 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused
Since this bug has expired it would be useful to get a fresh bug report. Please run: ubuntu-bug gnome-shell -- 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/1761382 Title: Unable to connect to ibus: Could not connect: Connection refused Status in gnome-shell package in Ubuntu: Expired Status in ibus package in Ubuntu: Expired Bug description: Get this logged: oem@ubuntu:~$ journalctl -b | grep ibus dbus-daemon[1074]: [session uid=120 pid=1074] Activating service name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120 pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1084]: Unable to connect to ibus: Could not connect: Connection refused /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting QT_IM_MODULE=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting GTK_IM_MODULE=ibus dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000 pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1435]: Unable to connect to ibus: Could not connect: Connection refused ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 5 07:43:59 2018 DisplayManager: gdm3 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+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 2056696] Re: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors
> Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="ListActivatableNames" mask="send" name="org.freedesktop.DBus" pid=2950 label="snap.element-desktop.element-desktop" peer_label="unconfined" This is provided by the system-observe interface in snapd - currently it looks like element-desktop does not plug this so the element-desktop snap needs to be updated to include this. > Log: apparmor="DENIED" operation="dbus_method_call" bus="session" > path="/modules/kwalletd5" interface="org.kde.KWallet" member="isEnabled" > mask="send" name="org.kde.kwalletd5" pid=2950 > label="snap.element-desktop.element-desktop" peer_pid=1762 > peer_label="unconfined" > Log: apparmor="DENIED" operation="dbus_method_call" bus="session" > path="/modules/kwalletd5" interface="org.kde.KWallet" member="close" > mask="send" name="org.kde.kwalletd5" pid=2950 > label="snap.element-desktop.element-desktop" peer_pid=1762 > peer_label="unconfined" These are provided by the password-manager-service interface in snapd - again currently it looks like element-desktop does not plug this so the element-desktop snap needs to be updated to include this as well. Finally, for the last two > Log: apparmor="DENIED" operation="dbus_method_call" bus="session" > path="/StatusNotifierItem" interface="org.freedesktop.DBus.Properties" > member="GetAll" name=":1.45" mask="receive" pid=2950 > label="snap.element-desktop.element-desktop" peer_pid=2394 > peer_label="plasmashell" > Log: apparmor="DENIED" operation="dbus_signal" bus="session" > path="/StatusNotifierItem" interface="org.kde.StatusNotifierItem" > member="NewToolTip" mask="send" name="org.freedesktop.DBus" pid=2950 > label="snap.element-desktop.element-desktop" peer_pid=2394 > peer_label="plasmashell" Yes this is due to the peer_label mismatch - previously plasmashell would run without an AppArmor profile and so was "unconfined" - the most recent apparmor release in Noble contains a new profile for plasmashell in /etc/apparmor.d/plasmashell with the label "plasmashell" - and so now the peer_label doesn't match. This likely needs to be fixed on the snapd side (or we figure out a way in apparmor to not ship this profile). -- 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/2056696 Title: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors Status in snapd: New Status in apparmor package in Ubuntu: Confirmed Bug description: OS: Kubuntu Noble 24.04 Alpha (two-day old install) snapd version: 2.61.2 Affected Snaps: firefox, thunderbird, element-desktop Steps to reproduce: # For Firefox: 1. Open the Firefox Snap. 2. Open https://www.bennish.net/web-notifications.html. 3. Click "Authorize" and allow the website to send notifications. 4. Click "Show". Expected result: A notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: The notification shows up in the upper-right corner of the display, improperly themed and obviously generated by Firefox as a fallback. # For Thunderbird: 1. Open the Thunderbird Snap. 2. Ensure you are connected to an email account. 3. Unfocus the Thunderbird window. 4. Wait for an email to come through. Expected result: When the email comes through, a notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: The notification shows up improperly themed and obviously generated by Thunderbird as a fallback. # For Element: 1. Open the Element Snap. Expected result: An apptray indicator should appear in the system tray with the Element logo. Actual result: No such indicator appears. 2. Log in, ask someone to ping you, then unfocus the window and wait for the ping to come through. Expected result: A notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: No notification appears at all. Additional information: Based on the output of snappy-debug, this appears to be AppArmor related, at least for element-desktop (but presumably for the others too). Of note are some of the following log entries: ``` = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="ListActivatableNames" mask="send" name="org.freedesktop.DBus" pid=2950 label="snap.element-desktop.element-desktop" peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/modules/kwalletd5" interface="org.kde.KWallet" member="isEnabled" mask="send" name="org.kde.kwalletd5" pid=2950
[Touch-packages] [Bug 2057978] [NEW] package polkitd 124-1 failed to install/upgrade: le sous-processus paquet polkitd script post-installation installé a renvoyé un état de sortie d'erreur 1
Public bug reported: error during upgrade LTS version ProblemType: Package DistroRelease: Ubuntu 24.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Mar 14 23:29:51 2024 ErrorMessage: le sous-processus paquet polkitd script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2021-12-13 (822 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.4ubuntu5 apt 2.7.12 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: le sous-processus paquet polkitd script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to noble on 2024-03-14 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2057978 Title: package polkitd 124-1 failed to install/upgrade: le sous-processus paquet polkitd script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in policykit-1 package in Ubuntu: New Bug description: error during upgrade LTS version ProblemType: Package DistroRelease: Ubuntu 24.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Mar 14 23:29:51 2024 ErrorMessage: le sous-processus paquet polkitd script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2021-12-13 (822 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.4ubuntu5 apt 2.7.12 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: le sous-processus paquet polkitd script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to noble on 2024-03-14 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2057978/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: steam (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2056696] Re: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors
the rejects here are all from the snap.element-desktop.element-desktop profile. We will need to dig into that profiles permissions. If its getting all the right paths correct then I suspect the peer_label match might be the issue. -- 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/2056696 Title: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors Status in snapd: New Status in apparmor package in Ubuntu: Confirmed Bug description: OS: Kubuntu Noble 24.04 Alpha (two-day old install) snapd version: 2.61.2 Affected Snaps: firefox, thunderbird, element-desktop Steps to reproduce: # For Firefox: 1. Open the Firefox Snap. 2. Open https://www.bennish.net/web-notifications.html. 3. Click "Authorize" and allow the website to send notifications. 4. Click "Show". Expected result: A notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: The notification shows up in the upper-right corner of the display, improperly themed and obviously generated by Firefox as a fallback. # For Thunderbird: 1. Open the Thunderbird Snap. 2. Ensure you are connected to an email account. 3. Unfocus the Thunderbird window. 4. Wait for an email to come through. Expected result: When the email comes through, a notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: The notification shows up improperly themed and obviously generated by Thunderbird as a fallback. # For Element: 1. Open the Element Snap. Expected result: An apptray indicator should appear in the system tray with the Element logo. Actual result: No such indicator appears. 2. Log in, ask someone to ping you, then unfocus the window and wait for the ping to come through. Expected result: A notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: No notification appears at all. Additional information: Based on the output of snappy-debug, this appears to be AppArmor related, at least for element-desktop (but presumably for the others too). Of note are some of the following log entries: ``` = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="ListActivatableNames" mask="send" name="org.freedesktop.DBus" pid=2950 label="snap.element-desktop.element-desktop" peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/modules/kwalletd5" interface="org.kde.KWallet" member="isEnabled" mask="send" name="org.kde.kwalletd5" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=1762 peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/modules/kwalletd5" interface="org.kde.KWallet" member="close" mask="send" name="org.kde.kwalletd5" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=1762 peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/StatusNotifierItem" interface="org.freedesktop.DBus.Properties" member="GetAll" name=":1.45" mask="receive" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=2394 peer_label="plasmashell" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_signal" bus="session" path="/StatusNotifierItem" interface="org.kde.StatusNotifierItem" member="NewToolTip" mask="send" name="org.freedesktop.DBus" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=2394 peer_label="plasmashell" DBus access ``` Booting with `apparmor=0` set on the kernel command line fixes the issue with Element (apptray indicator appears, notifications show up). Obviously this is not a solution, but it does isolate AppArmor as being at least partially at fault. This issue seems to be somewhat similar to https://forum.snapcraft.io/t/dbus-related-apparmor-denials/37422, however it seems as if Element is trying to hit the right paths and interfaces and is still being denied (based on looking at the info in https://github.com/snapcore/snapd/blob/master/interfaces/builtin/desktop_legacy.go and comparing the paths and interfaces there with the paths and interfaces shown by snappy-debug. I talked about this issue with Erich Eickmeyer and he mentioned that it occurred after a Plasma update. This doesn't make a great deal of sense to me, and I suspect possibly some other component of the affected systems happened to get updated at the same
[Touch-packages] [Bug 2051672] Re: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iproute2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) Status in iproute2 package in Ubuntu: Confirmed Bug description: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 Upstream ChangeLog: - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/ (Previous changelog: https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 ) ChangeLog from Debian: iproute2 (6.8.0-1) unstable; urgency=medium [ Ceppo ] * Update Italian po-debconf translation (Closes: #1063002) [ Luca Boccassi ] * Add build dependency on libnsl-dev (Closes: #1065214) * Switch to pkgconf * Update upstream source from tag 'upstream/6.8.0' * Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged upstream * Drop iproute2-doc package * Drop tc/m_xt.so and tc/m_ipt.so, removed upstream -- Luca Boccassi <> Tue, 12 Mar 2024 14:02:38 + iproute2 (6.7.0-2) unstable; urgency=medium * Backport fix for 'ss' output -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium * Add Italian debconf translation (Closes: #1056582) * Update upstream source from tag 'upstream/6.7.0' * Bump copyright year ranges in d/copyright * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, merged upstream * Default config files moved from /usr/lib to /usr/share -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium * Update upstream source from tag 'upstream/6.6.0' * Backport patch to fix configuration installation * Remove handling of qt_atm.so, dropped upstream -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium * Use dh-sequence-movetousr -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium * Remove further leftovers as part of upstream's move of config to /usr (Closes: #1051577) -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 iproute2 (6.5.0-2) unstable; urgency=medium * Add maintscript to remove conffiles that upstream has moved to /usr (Closes: #1051577) -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 iproute2 (6.5.0-1) unstable; urgency=medium [ Luca Boccassi ] * Use wildcard for Lintian overrides [ Peter Kvillegård ] * Add Swedish translation of debconf messages (Closes: #1050442) [ Luca Boccassi ] * Update upstream source from tag 'upstream/6.5.0' * Use cap_bpf instead of cap_sys_admin for ip vrf-exec * Package-provided config files are now shipped in /usr/iproute2 instead of /etc/iproute2 -- Luca Boccassi <> Sat, 09 Sep 2023 16:32:54 +0100 iproute2 (6.4.0-1) unstable; urgency=medium * Fix patch header Forwarded field * Enable ELF metadata stamping * Update upstream source from tag 'upstream/6.4.0' * Update Lintian overrides -- Luca Boccassi <> Fri, 30 Jun 2023 12:16:40 +0100 iproute2 (6.3.0-1) unstable; urgency=medium * Drop obsolete conflicts/replaces
[Touch-packages] [Bug 2029473] Re: Backport Ubuntu Pro to Xenial
Version 0.96.20.10 passed in xenial/amd64 about 10 days ago (via an ubuntu-advantage-tools update), but version 0.96.20.12 failed a few days before. I triggered another run just in case. If that new run also fails, then something is going on, and it has to be sorted out before this update can be released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2029473 Title: Backport Ubuntu Pro to Xenial Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: Fix Committed Bug description: * Impact We want desktop integration with Ubuntu Pro * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations The livepatch checkbox is also inactive because the current update- notifier version in xenial doesn't include livepatch support - Ubuntu Pro enables extended support for 10 years for long term support Ubuntu series. Xenial is therefore currently also supported under Ubuntu Pro. Xenial's software-properties-gtk, however, doesn't have the Ubuntu Pro functionality that exists in Bionic, Focal etc. Thus this request to backport the Ubuntu Pro functionality to Xenial. This depends on LP:2029089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2029473/+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 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused
Still present on 24.04 with gnome-shell=45.3-1ubuntu1 and ibus=1.5.29-1 -- 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/1761382 Title: Unable to connect to ibus: Could not connect: Connection refused Status in gnome-shell package in Ubuntu: Expired Status in ibus package in Ubuntu: Expired Bug description: Get this logged: oem@ubuntu:~$ journalctl -b | grep ibus dbus-daemon[1074]: [session uid=120 pid=1074] Activating service name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120 pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1084]: Unable to connect to ibus: Could not connect: Connection refused /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting QT_IM_MODULE=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting GTK_IM_MODULE=ibus dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000 pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1435]: Unable to connect to ibus: Could not connect: Connection refused ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 5 07:43:59 2018 DisplayManager: gdm3 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+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 2057927] Re: lxd vga console throws "Operation not permitted" error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxd (Ubuntu) Status: New => Confirmed -- 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/2057927 Title: lxd vga console throws "Operation not permitted" error Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Confirmed Bug description: Since I upgraded to Noble the lxd vga console doesn't work anymore. I am using the lxd latest/stable snap (5.20-f3dd836). When trying to attach a vga console to an lxd vm I get: unshare: write failed /proc/self/uid_map: Operation not permitted It seems to be related to apparmor, I can see a matching DENIAL message in dmesg: [ 4735.233989] audit: type=1400 audit(1710419600.517:300): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=13157 comm="unshare" capability=21 capname="sys_admin" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+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 2057927] Re: lxd vga console throws "Operation not permitted" error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- 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/2057927 Title: lxd vga console throws "Operation not permitted" error Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Confirmed Bug description: Since I upgraded to Noble the lxd vga console doesn't work anymore. I am using the lxd latest/stable snap (5.20-f3dd836). When trying to attach a vga console to an lxd vm I get: unshare: write failed /proc/self/uid_map: Operation not permitted It seems to be related to apparmor, I can see a matching DENIAL message in dmesg: [ 4735.233989] audit: type=1400 audit(1710419600.517:300): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=13157 comm="unshare" capability=21 capname="sys_admin" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
Hello from noble by the way ) ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release:24.04 Codename: noble ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python-apt source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Invalid Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
This bug was fixed in the package python2.7 - 2.7.18-1~20.04.4 --- python2.7 (2.7.18-1~20.04.4) focal; urgency=medium * Add d/p/add-optimization-flags-to-cflags.diff: Add optimization flags to cflags when compiling C modules. (LP: #2002043) -- Mitchell Dzurick Wed, 31 Jan 2024 09:23:13 -0700 ** Changed in: python2.7 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 Status in python2.7 package in Ubuntu: Invalid Status in python2.7 source package in Bionic: Won't Fix Status in python2.7 source package in Focal: Fix Released Status in python2.7 source package in Jammy: Fix Released Status in python2.7 source package in Kinetic: Invalid Status in python2.7 source package in Lunar: Invalid Status in python2.7 source package in Mantic: Invalid Bug description: [ Impact ] When compiling Python extensions using Python2, CFLAGS optimization flags are dropped. This behavior has been caused by our update in this patch http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz which differs from upstream. The fix modifies the portion of code in Lib/distutils/sysconfig.py which gets the cflags from the environments, and includes the dropped OPT flag from get_config_vars(). [ Test Plan ] There will be 2 separate tests for this bug: * Ensuring no-change rebuilds are not changed * Ensuring local builds are not changed unless environment variable is set Test 1) No-change rebuilds To test that no-change rebuilds are not changed, the package python- stdlib-extensions will be built against the new python2.7, and confirm the compiler flags are not altered. This will be a manual test and visual inspection of the build logs. Test 2) Functional test 1. Create test container $ lxc launch ubuntu:jammy jammy-2002043 $ lxc shell jammy-2002043 2. Install required packages For Jammy # apt update -y && apt install -y python2 python-pip For Focal # apt update -y && apt install -y python2 python-setuptools gcc 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2002043] Update Released
The verification of the Stable Release Update for python2.7 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 python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 Status in python2.7 package in Ubuntu: Invalid Status in python2.7 source package in Bionic: Won't Fix Status in python2.7 source package in Focal: Fix Released Status in python2.7 source package in Jammy: Fix Released Status in python2.7 source package in Kinetic: Invalid Status in python2.7 source package in Lunar: Invalid Status in python2.7 source package in Mantic: Invalid Bug description: [ Impact ] When compiling Python extensions using Python2, CFLAGS optimization flags are dropped. This behavior has been caused by our update in this patch http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz which differs from upstream. The fix modifies the portion of code in Lib/distutils/sysconfig.py which gets the cflags from the environments, and includes the dropped OPT flag from get_config_vars(). [ Test Plan ] There will be 2 separate tests for this bug: * Ensuring no-change rebuilds are not changed * Ensuring local builds are not changed unless environment variable is set Test 1) No-change rebuilds To test that no-change rebuilds are not changed, the package python- stdlib-extensions will be built against the new python2.7, and confirm the compiler flags are not altered. This will be a manual test and visual inspection of the build logs. Test 2) Functional test 1. Create test container $ lxc launch ubuntu:jammy jammy-2002043 $ lxc shell jammy-2002043 2. Install required packages For Jammy # apt update -y && apt install -y python2 python-pip For Focal # apt update -y && apt install -y python2 python-setuptools gcc 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
This bug was fixed in the package python2.7 - 2.7.18-13ubuntu1.2 --- python2.7 (2.7.18-13ubuntu1.2) jammy; urgency=medium * Add d/p/add-optimization-flags-to-cflags.diff: Add optimization flags to cflags when compiling C modules. (LP: #2002043) -- Mitchell Dzurick Sun, 15 Oct 2023 12:43:11 -0400 ** Changed in: python2.7 (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 python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 Status in python2.7 package in Ubuntu: Invalid Status in python2.7 source package in Bionic: Won't Fix Status in python2.7 source package in Focal: Fix Released Status in python2.7 source package in Jammy: Fix Released Status in python2.7 source package in Kinetic: Invalid Status in python2.7 source package in Lunar: Invalid Status in python2.7 source package in Mantic: Invalid Bug description: [ Impact ] When compiling Python extensions using Python2, CFLAGS optimization flags are dropped. This behavior has been caused by our update in this patch http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz which differs from upstream. The fix modifies the portion of code in Lib/distutils/sysconfig.py which gets the cflags from the environments, and includes the dropped OPT flag from get_config_vars(). [ Test Plan ] There will be 2 separate tests for this bug: * Ensuring no-change rebuilds are not changed * Ensuring local builds are not changed unless environment variable is set Test 1) No-change rebuilds To test that no-change rebuilds are not changed, the package python- stdlib-extensions will be built against the new python2.7, and confirm the compiler flags are not altered. This will be a manual test and visual inspection of the build logs. Test 2) Functional test 1. Create test container $ lxc launch ubuntu:jammy jammy-2002043 $ lxc shell jammy-2002043 2. Install required packages For Jammy # apt update -y && apt install -y python2 python-pip For Focal # apt update -y && apt install -y python2 python-setuptools gcc 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2040465] 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/2040465 Title: New upstream microrelease 2.5.17 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.17. 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/XRQE4CVQDLTG4EYPKVEU2L76DYGIFR2Q/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/commit/99a124bb434052a71cf4ff115d0f949f6c6b7208/pipelines?ref=OPENLDAP_REL_ENG_2_5 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/4744NWC2HJP7L24WOUMZF4VCYGGUMRI7/ * 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/679769800/buildlog_ubuntu-jammy-amd64.openldap_2.5.16+dfsg-0ubuntu0.22.04.1~ppa1_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.16+dfsg-0ubuntu0.22.04.2 | jammy-security | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 - https://pad.lv/1983618 - https://pad.lv/2007625 - https://pad.lv/2027079 - https://pad.lv/2029170 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/2040465/+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 2040465] Re: New upstream microrelease 2.5.17
This bug was fixed in the package openldap - 2.5.17+dfsg-0ubuntu0.22.04.1 --- openldap (2.5.17+dfsg-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream version (LP: #2040465). - Added slapo-dynlist option to disable filter support (ITS#10025) - Fixed liblber missing newline on long msg (ITS#10105) - Fixed libldap exit handling with OpenSSL3 (ITS#9952) - Fixed libldap with TLS and multiple ldap URIs (ITS#10101) - Fixed libldap OpenSSL cipher suite handling (ITS#10094) - Fixed libldap OpenSSL 3.0 and Diffie-Hellman param files (ITS#10124) - Fixed libldap timestamps on Windows (ITS#10100) - Fixed lloadd to work when resolv.conf is missing (ITS#10070) - Fixed lloadd handling of closing connection (ITS#10083) - Fixed slapd to honour disclose in matchedDN handling (ITS#10139) - Fixed slapd handling of regex testing in ACLs (ITS#10089) - Fixed slapd-asyncmeta when remote suffix is empty (ITS#10076) - Fixed slapo-dynlist so it can't be global (ITS#10091) -- Sergio Durigan Junior Fri, 09 Feb 2024 15:12:07 -0500 ** 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/2040465 Title: New upstream microrelease 2.5.17 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.17. 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/XRQE4CVQDLTG4EYPKVEU2L76DYGIFR2Q/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/commit/99a124bb434052a71cf4ff115d0f949f6c6b7208/pipelines?ref=OPENLDAP_REL_ENG_2_5 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/4744NWC2HJP7L24WOUMZF4VCYGGUMRI7/ * 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/679769800/buildlog_ubuntu-jammy-amd64.openldap_2.5.16+dfsg-0ubuntu0.22.04.1~ppa1_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.16+dfsg-0ubuntu0.22.04.2 | jammy-security | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 - https://pad.lv/1983618 - https://pad.lv/2007625 - https://pad.lv/2027079 - https://pad.lv/2029170 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/2040465/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
We decided it would be best to just SRU python-apt to mantic to fix this, rather than write a workaround in ubuntu-release-upgrader. Updating the tasks to reflect that. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: New => Invalid ** Changed in: python-apt (Ubuntu Mantic) Status: New => Confirmed ** Changed in: python-apt (Ubuntu Mantic) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python-apt source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Invalid Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2057957] Re: Headphone and speaker
Boot logs, in text file, if needed ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2057957/+attachment/5756043/+files/journalctl.txt ** Description changed: Hello, when connecting a headset to the PC, the sound comes out at the same time from the PC speaker and the headset. And the volume bar only appears to have an effect on the headphone jack. The sound coming out of the speaker remains the same volume. I tested it on the desktop, just turning down the volume, with the game - Need for speed most wanted 2012, proton, on Steam .deb, on the official - website. + Need for speed most wanted 2012, proton, on Steam (.deb) Steps to reproduce 1 - Connect the headphones to the Laptop while it is still turned off 2 - After connecting, carry out sound tests 3 - the sound comes out of both headphones and speaker Thank you in advance, good luck to you always ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: leandro 952 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: leandro 952 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 14 14:51:19 2024 InstallationDate: Installed on 2024-01-13 (61 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all ProcEnviron: - LANGUAGE=pt_BR:pt:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pt_BR.UTF-8 - SHELL=/bin/bash + LANGUAGE=pt_BR:pt:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pt_BR.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias: dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6 dmi.product.version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO -- 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/2057957 Title: Headphone and speaker Status in alsa-driver package in Ubuntu: New Bug description: Hello, when connecting a headset to the PC, the sound comes out at the same time from the PC speaker and the headset. And the volume bar only appears to have an effect on the headphone jack. The sound coming out of the speaker remains the same volume. I tested it on the desktop, just turning down the volume, with the game Need for speed most wanted 2012, proton, on Steam (.deb) Steps to reproduce 1 - Connect the headphones to the Laptop while it is still turned off 2 - After connecting, carry out sound tests 3 - the sound comes out of both headphones and speaker Thank you in advance, good luck to you always ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leandro 952 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 14 14:51:19 2024 InstallationDate: Installed on 2024-01-13 (61 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias:
[Touch-packages] [Bug 2057957] [NEW] Headphone and speaker
Public bug reported: Hello, when connecting a headset to the PC, the sound comes out at the same time from the PC speaker and the headset. And the volume bar only appears to have an effect on the headphone jack. The sound coming out of the speaker remains the same volume. I tested it on the desktop, just turning down the volume, with the game Need for speed most wanted 2012, proton, on Steam (.deb) Steps to reproduce 1 - Connect the headphones to the Laptop while it is still turned off 2 - After connecting, carry out sound tests 3 - the sound comes out of both headphones and speaker Thank you in advance, good luck to you always ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leandro 952 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 14 14:51:19 2024 InstallationDate: Installed on 2024-01-13 (61 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias: dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6 dmi.product.version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2057957 Title: Headphone and speaker Status in alsa-driver package in Ubuntu: New Bug description: Hello, when connecting a headset to the PC, the sound comes out at the same time from the PC speaker and the headset. And the volume bar only appears to have an effect on the headphone jack. The sound coming out of the speaker remains the same volume. I tested it on the desktop, just turning down the volume, with the game Need for speed most wanted 2012, proton, on Steam (.deb) Steps to reproduce 1 - Connect the headphones to the Laptop while it is still turned off 2 - After connecting, carry out sound tests 3 - the sound comes out of both headphones and speaker Thank you in advance, good luck to you always ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leandro 952 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 14 14:51:19 2024 InstallationDate: Installed on 2024-01-13 (61 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias: dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6 dmi.product.version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Touch-packages] [Bug 2057943] Re: Can't disable or modify snap package apparmor rules
If you are admin of your system, you can manually replace snap profiles.
But there are some caveats in that snapd doesn't really want this. It
manages its profiles, dynamically regenerates and replaces them etc.
You are correct that the tooling doesn't work here. It expects the
abstractions to be in the same directory as the profile, which snapd
profiles dir doesn't do.
I put this as a wish list as its a feature development request to make
the tooling support abstractions in a different location than the
profile.
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Wishlist
--
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/2057943
Title:
Can't disable or modify snap package apparmor rules
Status in apparmor package in Ubuntu:
New
Bug description:
On Ubuntu 20.04 (and probably 22.04 and greater), it is impossible to
disable snap chromium apparmor rules:
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure
Can't find chromium.hook.configure in the system path list. If the name of
the application
is correct, please run 'which snap.chromium.hook.configure' as a user with
correct PATH
environment set up in order to find the fully-qualified path and
use the full path as parameter.
root@{HOSTNAME}:~# aa-complain snap.chromium.chromedriver -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.chromium -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global
not found
It seems like no one has an answer on how these overly restricted
rules can be disabled:
https://askubuntu.com/questions/1267980/how-to-disable-apparmor-for-chromium-snap-ubuntu-20-04
https://ubuntuforums.org/showthread.php?t=2410550
https://ubuntuforums.org/showthread.php?t=2449022
https://answers.launchpad.net/ubuntu/+source/apparmor/+question/701036
So I just got rid of apparmor which doesn't seem like the solution I
was after, but it works great now:
sudo systemctl stop apparmor
sudo systemctl disable apparmor
Please give us a way to modify (and keep the rules permanently
modified even after snap updates) snap apparmor rules.
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057943/+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 2030784] Re: Backport Intel's AVX512 patches on openssl 3.0
Thanks a lot for looking at this. The issue seems fixed on my machine. There are currently several changes being prepared for openssl and I think I'd rather batch them considering the state of the CI queue but this will definitely go into Noble. Thanks again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2030784 Title: Backport Intel's AVX512 patches on openssl 3.0 Status in openssl package in Ubuntu: Fix Released Bug description: https://github.com/openssl/openssl/pull/14908 https://github.com/openssl/openssl/pull/17239 These should provide a nice performance bonus on recent CPUs, and the patches are fairly self-contained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+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 2057944] [NEW] pidwait doesn't work. Instead behaves like pgrep
Public bug reported: pidwait doesn't work at all. Seems like pidwait was renamed in an Ubuntu patch from upstream pwait - however the executable that is built acts as "pgrep" unless it's called as "pwait"; this check also needs to be updated with the executable name "pidwait". ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2057944 Title: pidwait doesn't work. Instead behaves like pgrep Status in procps package in Ubuntu: New Bug description: pidwait doesn't work at all. Seems like pidwait was renamed in an Ubuntu patch from upstream pwait - however the executable that is built acts as "pgrep" unless it's called as "pwait"; this check also needs to be updated with the executable name "pidwait". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2057944/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
> That is not the case Seems you are right In my case there was `/etc/apt/sources.list.d/vscode.list` with content ``` ### THIS FILE IS AUTOMATICALLY CONFIGURED ### # You may comment out this entry, but any other modifications may be lost. ``` If wipe out/remove this file then upgrader does not complain about apt repos -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2057943] [NEW] Can't disable or modify snap package apparmor rules
Public bug reported:
On Ubuntu 20.04 (and probably 22.04 and greater), it is impossible to
disable snap chromium apparmor rules:
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure
Can't find chromium.hook.configure in the system path list. If the name of the
application
is correct, please run 'which snap.chromium.hook.configure' as a user with
correct PATH
environment set up in order to find the fully-qualified path and
use the full path as parameter.
root@{HOSTNAME}:~# aa-complain snap.chromium.chromedriver -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.chromium -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not
found
It seems like no one has an answer on how these overly restricted rules
can be disabled:
https://askubuntu.com/questions/1267980/how-to-disable-apparmor-for-chromium-snap-ubuntu-20-04
https://ubuntuforums.org/showthread.php?t=2410550
https://ubuntuforums.org/showthread.php?t=2449022
https://answers.launchpad.net/ubuntu/+source/apparmor/+question/701036
So I just got rid of apparmor which doesn't seem like the solution I was
after, but it works great now:
sudo systemctl stop apparmor
sudo systemctl disable apparmor
Please give us a way to modify (and keep the rules permanently modified
even after snap updates) snap apparmor rules.
Thank you!
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2057943
Title:
Can't disable or modify snap package apparmor rules
Status in apparmor package in Ubuntu:
New
Bug description:
On Ubuntu 20.04 (and probably 22.04 and greater), it is impossible to
disable snap chromium apparmor rules:
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure
Can't find chromium.hook.configure in the system path list. If the name of
the application
is correct, please run 'which snap.chromium.hook.configure' as a user with
correct PATH
environment set up in order to find the fully-qualified path and
use the full path as parameter.
root@{HOSTNAME}:~# aa-complain snap.chromium.chromedriver -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.chromium -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global
not found
It seems like no one has an answer on how these overly restricted
rules can be disabled:
https://askubuntu.com/questions/1267980/how-to-disable-apparmor-for-chromium-snap-ubuntu-20-04
https://ubuntuforums.org/showthread.php?t=2410550
https://ubuntuforums.org/showthread.php?t=2449022
https://answers.launchpad.net/ubuntu/+source/apparmor/+question/701036
So I just got rid of apparmor which doesn't seem like the solution I
was after, but it works great now:
sudo systemctl stop apparmor
sudo systemctl disable apparmor
Please give us a way to modify (and keep the rules permanently
modified even after snap updates) snap apparmor rules.
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057943/+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 2057490] Re: Crash during upgrade from Jammy/Mantic to Noble
There, I finally got an apport crash file. Is that enough for you to have a first look? ** Attachment added: "_usr_sbin_NetworkManager.0.crash" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+attachment/5756023/+files/_usr_sbin_NetworkManager.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble Status in network-manager package in Ubuntu: New Bug description: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
It was upgraded too in prev update ``` $ cat /etc/apt/sources.list.d/vscode.sources Types: deb URIs: http://packages.microsoft.com/repos/code Suites: stable Components: main Architectures: amd64 Signed-By: /etc/apt/trusted.gpg.d/microsoft.gpg ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2057924] Re: Display after a computer sleep
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2057924 Title: Display after a computer sleep Status in xorg package in Ubuntu: New Bug description: After a computer sleep, each window appear under the dock launcher. See the attachment for and example. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 13:06:45 2024 DistUpgraded: 2022-08-14 08:22:53,939 ERROR Cache can not be locked (E:Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 35271 (jammy), W:Be aware that removing the lock file is not a solution and may break your system., E:Impossible d'obtenir le verrou de dpkg (/var/lib/dpkg/lock-frontend). Il est possible qu'un autre processus l'utilise.) DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0816] InstallationDate: Installed on 2021-03-01 (1108 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=2243852e-cb82-44e5-9287-eb132a652223 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-14 (578 days ago) dmi.bios.date: 12/12/2023 dmi.bios.release: 1.33 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.33.0 dmi.board.name: 0DH2HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd12/12/2023:br1.33:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn0DH2HV:rvrA00:cvnDellInc.:ct10:cvr:sku0816: dmi.product.family: Latitude dmi.product.name: Latitude 5490 dmi.product.sku: 0816 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2057924/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
`/etc/apt/sources.list.d/vscode.list` seems created on every vscode update. Seems there some script about it in deb. I definitely remember that I removed that file in past. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
** Tags removed: rls-nn-incoming -- 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/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2057944] Re: pidwait doesn't work. Instead behaves like pgrep
This is the case for jammy - for numbat the pwait -> pidwait change has happened upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2057944 Title: pidwait doesn't work. Instead behaves like pgrep Status in procps package in Ubuntu: New Bug description: pidwait doesn't work at all. Seems like pidwait was renamed in an Ubuntu patch from upstream pwait - however the executable that is built acts as "pgrep" unless it's called as "pwait"; this check also needs to be updated with the executable name "pidwait". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2057944/+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 2054609] Re: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1
The reason for the crash is that ntp uses an outdated OpenSSL API to use MD5 despite it normally being blocked in FIPS mode. This particular API has been deprecated with OpenSSL 3 which we ship in Jammy. This could be mitigated by switching to a newer OpenSSL API, but ntp also seems to be on life support, is only available via Universe and was removed for 24.04. I would recommend switching to another ntp implementation such as chrony which is in main. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: Confirmed Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
Very odd. I am able to upgrade just fine using your sources, Xavier. For now, I will work on fixing the issue I described[1] since it is at least *one* way to reproduce this error. [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/2047447/comments/7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
> The problem not in "sources" file but "empty" /etc/apt/sources.list That is not the case. You can easily verify this by testing with an empty /etc/apt/sources.list, and /etc/apt/sources.list.d/ubuntu.sources which contains: Types: deb URIs: http://archive.ubuntu.com/ubuntu Suites: mantic mantic-updates Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
I see nothing in this bug that needs sponsoring. Unsubscribing ~ubuntu- sponsors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: Won't Fix Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: Won't Fix Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057924] [NEW] Display after a computer sleep
You have been subscribed to a public bug: After a computer sleep, each window appear under the dock launcher. See the attachment for and example. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 13:06:45 2024 DistUpgraded: 2022-08-14 08:22:53,939 ERROR Cache can not be locked (E:Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 35271 (jammy), W:Be aware that removing the lock file is not a solution and may break your system., E:Impossible d'obtenir le verrou de dpkg (/var/lib/dpkg/lock-frontend). Il est possible qu'un autre processus l'utilise.) DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0816] InstallationDate: Installed on 2021-03-01 (1108 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=2243852e-cb82-44e5-9287-eb132a652223 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-14 (578 days ago) dmi.bios.date: 12/12/2023 dmi.bios.release: 1.33 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.33.0 dmi.board.name: 0DH2HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd12/12/2023:br1.33:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn0DH2HV:rvrA00:cvnDellInc.:ct10:cvr:sku0816: dmi.product.family: Latitude dmi.product.name: Latitude 5490 dmi.product.sku: 0816 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- Display after a computer sleep https://bugs.launchpad.net/bugs/2057924 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057927] [NEW] lxd vga console throws "Operation not permitted" error
Public bug reported: Since I upgraded to Noble the lxd vga console doesn't work anymore. I am using the lxd latest/stable snap (5.20-f3dd836). When trying to attach a vga console to an lxd vm I get: unshare: write failed /proc/self/uid_map: Operation not permitted It seems to be related to apparmor, I can see a matching DENIAL message in dmesg: [ 4735.233989] audit: type=1400 audit(1710419600.517:300): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=13157 comm="unshare" capability=21 capname="sys_admin" ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2057927 Title: lxd vga console throws "Operation not permitted" error Status in apparmor package in Ubuntu: New Status in lxd package in Ubuntu: New Bug description: Since I upgraded to Noble the lxd vga console doesn't work anymore. I am using the lxd latest/stable snap (5.20-f3dd836). When trying to attach a vga console to an lxd vm I get: unshare: write failed /proc/self/uid_map: Operation not permitted It seems to be related to apparmor, I can see a matching DENIAL message in dmesg: [ 4735.233989] audit: type=1400 audit(1710419600.517:300): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=13157 comm="unshare" capability=21 capname="sys_admin" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+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 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
I think you missed the extra arg to userauth_gsskeyex()
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
slightly wrong
Status in openssh package in Ubuntu:
In Progress
Status in openssh source package in Jammy:
In Progress
Status in openssh source package in Mantic:
In Progress
Status in openssh source package in Noble:
In Progress
Bug description:
The Authmethod struct now have 4 entries but the initialization of the
method_gsskeyex in the debian/patches/gssapi.patch only have 3
entries.
The struct was changed in upstream commit
dbb339f015c33d63484261d140c84ad875a9e548 as
===
@@ -104,7 +104,8 @@ struct Authctxt {
struct Authmethod {
char*name;
- int (*userauth)(struct ssh *);
+ char*synonym;
+ int (*userauth)(struct ssh *, const char *);
int *enabled;
};
===
The incorrect code does
===
+Authmethod method_gsskeyex = {
+ "gssapi-keyex",
+ userauth_gsskeyex,
+ _authentication
+};
===
but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex
This is now (change from Focal) causing gssapi-keyex to be disabled.
===
lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
===
apt-cache policy openssh-server
openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
Candidate: 1:8.9p1-3ubuntu0.6
Version table:
*** 1:8.9p1-3ubuntu0.6 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-updates/main amd64 Packages
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
1:8.9p1-3 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main
amd64 Packages
===
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+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 2051672] Re: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Summary changed: - Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) + Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) ** Description changed: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 Upstream ChangeLog: - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ + - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/ (Previous changelog: https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 ) ChangeLog from Debian: + + iproute2 (6.8.0-1) unstable; urgency=medium + + [ Ceppo ] + * Update Italian po-debconf translation (Closes: #1063002) + + [ Luca Boccassi ] + * Add build dependency on libnsl-dev (Closes: #1065214) + * Switch to pkgconf + * Update upstream source from tag 'upstream/6.8.0' + * Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged + upstream + * Drop iproute2-doc package + * Drop tc/m_xt.so and tc/m_ipt.so, removed upstream + + -- Luca Boccassi <> Tue, 12 Mar 2024 14:02:38 + iproute2 (6.7.0-2) unstable; urgency=medium * Backport fix for 'ss' output -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium * Add Italian debconf translation (Closes: #1056582) * Update upstream source from tag 'upstream/6.7.0' * Bump copyright year ranges in d/copyright * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, merged upstream * Default config files moved from /usr/lib to /usr/share -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium * Update upstream source from tag 'upstream/6.6.0' * Backport patch to fix configuration installation * Remove handling of qt_atm.so, dropped upstream -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium * Use dh-sequence-movetousr -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium * Remove further leftovers as part of upstream's move of config to /usr (Closes: #1051577) -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 iproute2 (6.5.0-2) unstable; urgency=medium * Add maintscript to remove conffiles that upstream has moved to /usr (Closes: #1051577) -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 iproute2 (6.5.0-1) unstable; urgency=medium [ Luca Boccassi ] * Use wildcard for Lintian overrides [ Peter Kvillegård ] * Add Swedish translation of debconf messages (Closes: #1050442) [ Luca Boccassi ] * Update upstream source from tag 'upstream/6.5.0' * Use cap_bpf instead of cap_sys_admin for ip vrf-exec * Package-provided config files are now shipped in /usr/iproute2 instead of /etc/iproute2 -- Luca Boccassi <> Sat, 09 Sep 2023 16:32:54 +0100 iproute2 (6.4.0-1) unstable; urgency=medium * Fix patch header Forwarded field * Enable ELF metadata stamping * Update upstream source from tag 'upstream/6.4.0' * Update Lintian overrides -- Luca Boccassi <> Fri, 30 Jun 2023 12:16:40 +0100 iproute2 (6.3.0-1) unstable; urgency=medium * Drop obsolete conflicts/replaces * Update upstream source from tag 'upstream/6.3.0' -- Luca Boccassi <> Tue, 13 Jun 2023 23:49:37 +0100 iproute2 (6.1.0-3) unstable; urgency=medium * Ensure
[Touch-packages] [Bug 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
I fixed this in Debian today in https://salsa.debian.org/ssh-
team/openssh/-/commit/0947dd466d64cabfb527d8326e2507f473373a32, uploaded
as part of 1:9.7p1-1. You could possibly just merge 1:9.7p1-1 into
noble since it's mostly a bug-fix release, but failing that you could
cherry-pick the relevant change easily enough.
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
slightly wrong
Status in openssh package in Ubuntu:
In Progress
Status in openssh source package in Jammy:
In Progress
Status in openssh source package in Mantic:
In Progress
Status in openssh source package in Noble:
In Progress
Bug description:
The Authmethod struct now have 4 entries but the initialization of the
method_gsskeyex in the debian/patches/gssapi.patch only have 3
entries.
The struct was changed in upstream commit
dbb339f015c33d63484261d140c84ad875a9e548 as
===
@@ -104,7 +104,8 @@ struct Authctxt {
struct Authmethod {
char*name;
- int (*userauth)(struct ssh *);
+ char*synonym;
+ int (*userauth)(struct ssh *, const char *);
int *enabled;
};
===
The incorrect code does
===
+Authmethod method_gsskeyex = {
+ "gssapi-keyex",
+ userauth_gsskeyex,
+ _authentication
+};
===
but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex
This is now (change from Focal) causing gssapi-keyex to be disabled.
===
lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
===
apt-cache policy openssh-server
openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
Candidate: 1:8.9p1-3ubuntu0.6
Version table:
*** 1:8.9p1-3ubuntu0.6 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-updates/main amd64 Packages
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
1:8.9p1-3 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main
amd64 Packages
===
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+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 2057671] Re: Rename the ubuntu-advantage-tools package
Subscribing ubuntu-release as per FFE policy. This bug affects noble cloud image release ** Also affects: software-properties (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2057671 Title: Rename the ubuntu-advantage-tools package Status in software-properties package in Ubuntu: New Status in software-properties source package in Noble: New Bug description: From ubuntu-advantage-tools v31, it has been renamed to ubuntu-pro- client. The current package is now a transitional package pointing to ubuntu-pro-client. software-properties depends on ubuntu-advantage- tool thus we should rename the dependency to ubuntu-pro-client to avoid having the transitional package as a dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2057671/+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 1970069] Re: Annoying boot messages interfering with splash screen
Fedora 39: CONFIG_FB_VESA=y CONFIG_FB_EFI=y Ubuntu 24.04: # CONFIG_FB_VESA is not set # CONFIG_FB_EFI is not set In the kernel source, DRM_SIMPLEDRM recommends SYSFB_SIMPLEFB if you want it to work on UEFI and VESA. And we do enable SYSFB_SIMPLEFB whose help text says: > you should still keep vesafb and others enabled as fallback > if a system framebuffer is incompatible with simplefb. So overall I don't think SimpleDRM *needs* any legacy fbdev like FB_EFI or FB_VESA, they're just recommended as a fallback. I'll do more testing in the coming days to verify if SimpleDRM is really working as intended. But the main concern here is that we might have broken some systems by disabling the legacy fbdev drivers. I'm not sure. Anyone testing Noble with kernel 6.8 right now should be able to tell us... -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
Files attached ** Attachment added: "aptsources.tar.bz2" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2047447/+attachment/5755869/+files/aptsources.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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
