[Touch-packages] [Bug 2038834] Autopkgtest regression report (mesa/23.2.1-1ubuntu3.1)
All autopkgtests for the newly accepted mesa (23.2.1-1ubuntu3.1) for mantic have finished running. The following regressions have been reported in tests triggered by the package: asymptote/2.86+ds-1 (armhf) clutter-1.0/1.26.4+git2779b932+dfsg-5 (armhf) freeglut/3.4.0-1 (armhf) gle/3.1.0-10 (armhf) glfw3/3.3.8-1 (armhf) gtk+3.0/3.24.38-5ubuntu1 (armhf) libcsfml/2.5-1.1 (armhf) libsdl2/2.28.3+dfsg-2 (armhf) mutter/45.0-3ubuntu3.1 (armhf) njplot/2.4-9 (armhf) vtk9/9.1.0+really9.1.0+dfsg2-7 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: Fix Committed Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
** Tags removed: impish ** Tags added: mantic -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 2034986] Re: some text became unreadable during a distribution upgrade
This bug was fixed in the package ubuntu-release-upgrader - 1:23.10.14 --- ubuntu-release-upgrader (1:23.10.14) mantic; urgency=medium * DistUpgradeQuirks: prevent upgrades on BIOS systems with XFS /boot (LP: #2039172) * Run pre-build.sh: updating po files, mirrors, and demotions. -- Nick Rosbrook Sun, 05 Nov 2023 01:39:16 -0400 ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Released Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 1437209] Re: package ubuntu-keyring 2012.05.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
something is wrong with your install gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team-sublime-text-2.gpg': resource limit gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team-sublime-text-3.gpg': resource limit gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team-tor-browser.gpg': resource limit gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team-y-ppa-manager.gpg': resource limit ** Changed in: ubuntu-keyring (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1437209 Title: package ubuntu-keyring 2012.05.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in ubuntu-keyring package in Ubuntu: Invalid Bug description: This appeared randomly after upgrading from terminal. When I run software updater, it keeps prompting from "Partial upgrade" ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ubuntu-keyring 2012.05.19 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 AptOrdering: ubuntu-keyring: Install ubuntu-keyring: Configure Architecture: amd64 Date: Fri Mar 27 13:43:09 2015 DuplicateSignature: package:ubuntu-keyring:2012.05.19:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2014-05-08 (322 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-keyring Title: package ubuntu-keyring 2012.05.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1437209/+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 1060349] Re: package ubuntu-keyring 2011.11.21.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
it seems maybe incompatible gnupg was installed on the system? gpg: fatal: /etc/apt/trustdb.gpg: invalid trustdb ** Changed in: ubuntu-keyring (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1060349 Title: package ubuntu-keyring 2011.11.21.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in ubuntu-keyring package in Ubuntu: Invalid Bug description: I was trying to upgrade some programs . And teminal says that my signing key's weren't upgraded ProblemType: Package DistroRelease: Ubuntu 12.04 Package: ubuntu-keyring 2011.11.21.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Tue Oct 2 12:06:52 2012 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all SourcePackage: ubuntu-keyring Title: package ubuntu-keyring 2011.11.21.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1060349/+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 1553673] Re: package ubuntu-keyring 2012.05.19 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2
Something is broken with these files: gpg: /etc/apt/trusted.gpg.d/webupd8team-y-ppa-manager.gpg: recurso de bloqueo de claves: límite de recurso gpg: /etc/apt/trusted.gpg.d/wine-wine-builds.gpg: recurso de bloqueo de claves: límite de recurso gpg: /etc/apt/trusted.gpg.d/yorba-ppa.gpg: recurso de bloqueo de claves: límite de recurso unrelated to ubuntu-keyring ** Changed in: ubuntu-keyring (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1553673 Title: package ubuntu-keyring 2012.05.19 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 Status in ubuntu-keyring package in Ubuntu: Invalid Bug description: Fixed with this post forum: http://ubuntuforums.org/showthread.php?t=2257304=2 Problem for exceeding or duplicate keys gpg. Possibly by way of adding PPA repositories. Thanks, David Gámiz Jiménez ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ubuntu-keyring 2012.05.19 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: ubuntu-keyring: Install ubuntu-keyring: Configure Architecture: amd64 Date: Sat Mar 5 10:54:29 2016 DuplicateSignature: package:ubuntu-keyring:2012.05.19:el subproceso instalado el script post-installation devolvió el código de salida de error 2 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 2 InstallationDate: Installed on 2014-05-26 (649 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: ubuntu-keyring Title: package ubuntu-keyring 2012.05.19 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1553673/+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 1897836] Re: package ubuntu-keyring 2012.05.19.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
something is wrong with your installation gpg: invalid key resource URL `/etc/apt/trusted.gpg.d/home:osmc.gpg' unrelated to this package ** Changed in: ubuntu-keyring (Ubuntu) Status: New => Won't Fix ** Changed in: ubuntu-keyring (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1897836 Title: package ubuntu-keyring 2012.05.19.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in ubuntu-keyring package in Ubuntu: Invalid Bug description: - Ubuntu 16.04 - ubuntu-keyring installed ver. 2012.05.19.1 (which is also the latest version) - I had previously had issues with an expired key from the OSMC installer, so I removed it, and after "sudo apt-get update" I've had no issues with mentioning that expired key. This issue with ubuntu-keyring now came up after the command "sudo apt-get upgrade" and looks like it could be related to that initial OSMC key issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-keyring 2012.05.19.1 ProcVersionSignature: Ubuntu 4.15.0-101.102~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Tue Sep 29 21:49:03 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-07-07 (1181 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: ubuntu-keyring Title: package ubuntu-keyring 2012.05.19.1 failed to install/upgrade: subprocess installed post-installation script 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/ubuntu-keyring/+bug/1897836/+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 1752656] Re: Please SRU archive keyrings to older releases
SRU of debian keyring is also somehow counter productive. Most likely usecase is to debootstrap unstable chroot. And for that to be done correctly, often enough most recent debootstrap from debian is required as otherwise the debootstrap might not complete, or complete incorrectly (see all the recent usrmerge changes and flip-flops). Similarly in Ubuntu keyring we have similar issue with debootstrap. However we are trying to maintain as large overlap window as possible. But it is impractical to SRU all keyrings ever, to all releases ever. Thus this item is won't fix. ** Changed in: ubuntu-keyring (Ubuntu) Status: New => Won't Fix ** Changed in: debian-archive-keyring (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1752656 Title: Please SRU archive keyrings to older releases Status in debian-archive-keyring package in Ubuntu: Won't Fix Status in ubuntu-keyring package in Ubuntu: Won't Fix Bug description: While not necessarily a critical issue for the Ubuntu keyrings, as Debian uses newer keys periodically, it becomes impossible with the default keyrings to verify the latest Debian archive files. It seems reasonable to ensure the keyring contents in all releases are the same, as the latest release is reflecting the latest archives. Related: bug 1801725 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-archive-keyring/+bug/1752656/+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 1776329] Re: apport-cli and cowbuilder fail with cert and keyring errors
** Changed in: ubuntu-keyring (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1776329 Title: apport-cli and cowbuilder fail with cert and keyring errors Status in ubuntu-keyring package in Ubuntu: Won't Fix Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 ubuntu-keyring: Installed: 2018.02.28 apport: Installed: 2.20.9-0ubuntu7.2 cowbuilder: Installed: 0.86 On a bionic system when attempting to report what I suspect is a bug in ubuntu-keying I got the following error start capture- $ apport-cli ubuntu-keyring *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (1.2 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. *** Error: Network problem Cannot connect to crash database, please check your Internet connection. Press any key to continue... end capture--- I worked around the problem by K'eeping the report and copying it to a Xenial system. From there I am submitting this bug report. The original problem that caused me to attempt to file a bug report against ubuntu-keyring was an attempt to build a bionic chroot for package building with the following command: start capture- # DIST=bionic cowbuilder --create --distribution bionic --components "main universe" --basepath /var/cache/pbuilder/base-bionic-amd64-test.cow --mirror http://us.archive.ubuntu.com:80/ubuntu --debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg I: Invoking pbuilder I: forking: pbuilder create --components 'main universe' --debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --buildplace /var/cache/pbuilder/base-bionic-amd64-test.cow --mirror http://us.archive.ubuntu.com:80/ubuntu --distribution bionic --no-targz --extrapackages cowdancer W: /root/.pbuilderrc does not exist I: Running in no-targz mode I: Distribution is bionic. I: Current time: Mon Jun 11 22:44:21 UTC 2018 I: pbuilder-time-stamp: 1528757061 I: Building the build environment I: running debootstrap /usr/sbin/debootstrap I: Retrieving InRelease I: Checking Release signature E: Release signed by unknown key (key id 3B4FE6ACC0B21F32) E: debootstrap failed E: Tail of debootstrap.log: gpgv: Signature made Thu Apr 26 23:38:40 2018 UTC gpgv:using RSA key 3B4FE6ACC0B21F32 gpgv: Can't check signature: No public key E: End of debootstrap.log W: Aborting with an error E: pbuilder create failed I: forking: rm -rf /var/cache/pbuilder/base-bionic-amd64-test.cow end capture--- On the same system the following command succeeds: start capture- DIST=xenial cowbuilder --create --distribution xenial \ --components "main universe" \ --basepath /var/cache/pbuilder/base-xenial-amd64.cow \ --mirror http://us.archive.ubuntu.com:80/ubuntu \ --debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg end capture--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-keyring 2018.02.28 [modified: usr/share/keyrings/ubuntu-archive-keyring.gpg] ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jun 11 22:51:48 2018 Dependencies: PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 TERM=xterm SHELL=/bin/bash PATH=(custom, no user) SourcePackage: ubuntu-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1776329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
Hello Mate, or anyone else affected, Accepted mesa into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Mantic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: Fix Committed Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2044726] Re: no abre aplicaciones
Can you share a screenshot or log of the error? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Package changed: xorg-server (Ubuntu) => 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/2044726 Title: no abre aplicaciones Status in Ubuntu: Incomplete Bug description: al intenar abrir whatsapp desde una cuenta instagram arroja error xorg ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Mon Nov 27 07:10:10 2023 DistUpgraded: 2023-05-05 04:55:30,841 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1019:7dd9] MachineType: Inspur Inspur Computer ProcEnviron: LANGUAGE=es_VE:es TERM=qterminal PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=015299ef-91dd-42b5-bbbc-f9da188b591e ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2023-05-05 (206 days ago) dmi.bios.date: 06/26/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.name: Inspur Computer All in one PC dmi.board.vendor: Inspur dmi.board.version: V1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/26/2014:br4.6:svnInspur:pnInspurComputer:pvr:rvnInspur:rnInspurComputerAllinonePC:rvrV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:sku: dmi.product.name: Inspur Computer dmi.sys.vendor: Inspur version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 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.2 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 xserver.bootTime: Mon Nov 27 06:50:00 2023 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:21.1.4-2ubuntu1.7~22.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2044726/+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 2042772] Re: [amdgpu] Display corrupted/freeze
After all updates with kernel 5.15.0-89 generic at logon screen same problem occurs after clicking user name. Following boot in recovery mode System Monitor shows Xorg running instead of Xwayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2042772 Title: [amdgpu] Display corrupted/freeze Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After latest updates login display is fine but after entering password display changes to black with random full width 1 pixel high white lines that move randomly vertically. Must power off to recover. Boot in recovery mode works OK. Send email if you need more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 07:09:04 2023 DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2018-08-11 (1912 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago) dmi.bios.date: 10/18/2016 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.5 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.5 dmi.modalias: dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.0.5 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.0.4-0ubuntu1~22.04.1 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.2 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/linux/+bug/2042772/+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 2044300] Re: [Merge] ~sudipmuk/ubuntu/+source/zeitgeist:merge-lp2044300-noble into ubuntu/+source/zeitgeist:debian/sid
Hi Utkarsh, Thanks for looking into this. On Sat, 25 Nov 2023 at 17:04, Utkarsh Gupta wrote: > > Review: Needs Information > > Hey there! > > Thanks for raising this much, much appreciated. This is great as-is but here > are some points that'd make it EVEN better: > > - > https://git.launchpad.net/~sudipmuk/ubuntu/+source/zeitgeist/commit/?id=95fd328c45f72fa0f3895900216ad0726e86139e > -> it misses the DEP-3 headers. I am aware that you're just rebasing the new > version and you're not really adding the patch itself. But whilst at it, if > you could really add DEP-3 headers to a patch, that'd be EXCELLENT! I could not find any bug report which might explain this patch. Seems to be an Ubuntu specific patch and introduced in zeitgeist_0.9.14-0ubuntu1. > > See: > https://git.launchpad.net/~sudipmuk/ubuntu/+source/zeitgeist/commit/?id=a6cff2e5ac675b90cc574a26dc953f452aa9a00c > for example. It has the DEP-3 headers and tells me why it's needed, some bug > history, et al. > > I generally look at it because sometimes we shouldn't really be merging stuff > as-is and carry-forwarding the tech-debt but actively be looking at drop the > delta wherever and whenever possible. > > Now, OTOH, look at > https://git.launchpad.net/~sudipmuk/ubuntu/+source/zeitgeist/commit/?id=e940d9763d0fba97dc8504ed382e01210a43f08d > -> it gives me a quick description but doesn't tell me if it's coming from > upstream or was it written by downstream, is there an upstream bug? a > downstream bug? or? and I spend my time looking at things, et al. That's why > DEP-3 headers are really useful. This one seems to fix LP: #962265 but I could not find a way to be sure and so not confident enough to add DEP-3 headers to the patch. Again, this also was introduced in zeitgeist_0.9.14-0ubuntu1. > > - > https://git.launchpad.net/~sudipmuk/ubuntu/+source/zeitgeist/commit/?id=2ab99989a22d2e07bfc28e5eae942bd8283c1aa7 > -> did you verify if that's still needed? why? :) Yes, this is still needed. My initial build failed as I did not have this one disabled. I have done a diff of the buildinfo and saw there are version mismatch of many packages between Debian and Ubuntu. One of the mismatch is still causing the issue in Ubuntu, but I don't know which one yet. -- Regards Sudip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/2044300 Title: Please merge zeitgeist 1.0.4-5 (universe) from Debian unstable (main) Status in zeitgeist package in Ubuntu: Confirmed Bug description: Please merge zeitgeist 1.0.4-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta: Carry forward three previous Ubuntu specific patch. 1. add_datahub_autostart_delay.patch 2. nodisplay_autostart.patch 3. pre_populator.patch Extra change for this version: The monitor-test was skipped in the previous version as it was failing. That test has now been enabled in Debian but is still failing in Ubuntu. And, so the extra change for this version was to disable it for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/2044300/+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 1979879] Re: Apparmor profile in 22.04 jammy - fails to start when printing enabled
** Description changed: [Impact] Users who have: a) opted in to confining samba with apparmor (by installing apparmor-profiles); and b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode; will experience an error in starting the smbd service in jammy: [2022/08/25 16:04:05.848067, 0] ../../lib/util/become_daemon.c:119(exit_daemon) exit_daemon: daemon failed to start: Samba failed to init printing subsystem, error code 13 This "printing subsystem" is actually a new daemon called samba-bgqd. This errors prevents "smbd" from starting. The reason it failed to start is that this binary is installed on a different path than what is allowed in the samba apparmor profiles, and as a result its execution is denied. The chosen fix for this is to change the path of samba-bgqd in the samba apparmor profiles to match where it is actually being installed in the jammy packaging. Changing the actual path in the samba packaging would be a more invasive fix. In kinetic and later, the installation path of samba-bgqd was changed instead, and requires no changes to the apparmor profiles. However, once the path in the apparmor profiles was fixed for jammy, another error comes up which also requires an apparmor change. samba- bgqd is using locking when opening the *.tdb files in /run/samba, and that requires an extra "k" flag to apparmor rules that cover that directory and its tdb files. This bug doesn't affect jammy samba users by default, as they have to complete steps (a) and (b) from above to be impacted. Therefore, on its own, this bug does not warrant an SRU, and we are using the block- proposed-jammy tag to prevent its release until such time when another more SRU-worthy apparmor bug is fixed for Jammy. [Test Plan] Make a container for testing: $ lxc launch ubuntu-daily:jammy jammy-test $ lxc shell jammy-test - Install the needed packages in this order, with two separate commands:L + Install the needed packages in this order, with two separate commands: # apt update # apt install apparmor-profiles apparmor-utils apparmor-profiles-extra # apt install samba smbclient cups cups-client Confirm that you have smbd and samba-bgqd processes confined and in complain mode (check first column): # ps faxZ | grep -E "(smbd|bgqd)" | grep -v grep smbd (complain)2432 ?Ss 0:00 /usr/sbin/smbd --foreground --no-process-group smbd (complain)2434 ?S 0:00 \_ /usr/sbin/smbd --foreground --no-process-group smbd (complain)2435 ?S 0:00 \_ /usr/sbin/smbd --foreground --no-process-group smbd//null-/usr/lib/x86_64-linux-gnu/samba/samba-bgqd (complain) 2436 ? S 0:00 \_ /usr/lib/x86_64-linux-gnu/samba/samba-bgqd Change the samba profiles to enforce mode: # aa-enforce /etc/apparmor.d/usr.sbin.smbd /etc/apparmor.d/samba-bgqd Setting /etc/apparmor.d/usr.sbin.smbd to enforce mode. Setting /etc/apparmor.d/samba-bgqd to enforce mode. Restart smbd: # systemctl restart smbd systemctl won't complain, but smbd failed to start: # ps faxZ | grep smbd | grep -v grep # # tail -2 /var/log/samba/log.smbd [2022/09/09 18:20:35.200901, 0] ../../lib/util/become_daemon.c:119(exit_daemon) exit_daemon: daemon failed to start: Samba failed to init printing subsystem, error code 13 And dmesg on the *host* (not the container) will log a few DENIED messages like this: [sex set 9 15:20:30 2022] audit: type=1400 audit(1662747635.194:10356): apparmor="DENIED" operation="exec" namespace="root//lxd-jammy-test_" profile="smbd" name="/usr/lib/x86_64-linux-gnu/samba/samba-bgqd" pid=994396 comm="smbd" requested_mask="x" denied_mask="x" fsuid=100 ouid=100 After installing the fixed package (and accepting the dpkg conf prompt changes), the new profile will be loaded in complain mode again. So let's put it in enforce mode one more time: # aa-enforce /etc/apparmor.d/usr.sbin.smbd /etc/apparmor.d/samba-bgqd Setting /etc/apparmor.d/usr.sbin.smbd to enforce mode. Setting /etc/apparmor.d/samba-bgqd to enforce mode. Restart: # systemctl restart smbd And confirm that smbd and samba-bgqd are running this time, and in enforce mode: # ps faxZ | grep -E "(smbd|bgqd)" | grep -v grep avahi-daemon (complain)4363 ?Ss 0:00 avahi-daemon: running [j-samba-bgqd-apparmor.local] smbd (enforce) 6734 ?Ss 0:00 /usr/sbin/smbd --foreground --no-process-group smbd (enforce) 6736 ?S 0:00 \_ /usr/sbin/smbd --foreground --no-process-group smbd (enforce) 6737 ?S 0:00 \_ /usr/sbin/smbd --foreground --no-process-group samba-bgqd (enforce) 6738 ?S 0:00 \_ /usr/lib/x86_64-linux-gnu/samba/samba-bgqd
[Touch-packages] [Bug 1878617] Re: Apple pages file type should be added to MIME types
** Changed in: shared-mime-info (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 shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types Status in shared-mime-info: Fix Released Status in mime-support package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Fix Released Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+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 2041672] Re: in mime/packages/freedesktop.org.xml is matching wrong files
When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. This issue is believed to be fixed in shared-mime-info 2.2 which is available in Ubuntu 22.10 and higher: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/b5df32dc ** Changed in: shared-mime-info (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/2041672 Title: in mime/packages/freedesktop.org.xml is matching wrong files Status in shared-mime-info package in Ubuntu: Fix Released Bug description: /usr/share/mime/packages/freedesktop.org.xml line 10466 -> value="import Qt" offset="0:3000" context: is matching python files using Pyside with imports like: from PySide2.QtCore import Qt, QSettings, QSize considering them 'Qt Markup Language files (text/x-qml)' thus wrecking havoc down the line. Maybe just remove this match entry as it seems very broad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/2041672/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
Right, it's probably appropriate to finally have a documented wiki-page for Mesa SRU's, so I'll create one. Upstream does extensive conformance testing on every release, but they do not cover hardware drivers. For that, we should be able to use Intel's Mesa CI which tests branches on many generations of GPU's from them. In order to use it, they need to grant developer access to it and I have a request pending now. For AMD hardware we can maybe ask them to test the backport on their CI (AIUI it's not public). In the past we've had the cert team test the backports on a handful of enabled machines (both Intel & AMD), but having the above would greatly improve the coverage and give greater confidence in these SRU's. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Incomplete Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2044795] Re: Please merge openssl from debian unstable
Will resume once new openssl LTS is realsed. ** Changed in: openssl (Ubuntu) Assignee: Ravi Kant Sharma (ravi-sharma) => (unassigned) -- 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/2044795 Title: Please merge openssl from debian unstable Status in openssl package in Ubuntu: Confirmed Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2044795/+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 1485396] Re: impossible to upgrade package from vivid to wily because of maintainer script reference to upstart job without matching init script
Well also this bug was fixed in later releases, the package doesn't fail to unpack on systems with systemd as init ** Changed in: isc-dhcp (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1485396 Title: impossible to upgrade package from vivid to wily because of maintainer script reference to upstart job without matching init script Status in isc-dhcp package in Ubuntu: Fix Released Bug description: The isc-dhcp-server package is not upgradable on a real machine (vs. a chroot) in vivid or wily, because it installs two upstart jobs in the usual debhelper way, but only one of them has a matching init script. As a result, on a system with systemd as init, isc-dhcp-server will fail to even unpack over a running system: Preparing to unpack .../isc-dhcp-server_4.3.1-5ubuntu3_amd64.deb ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused invoke-rc.d: unknown initscript, /etc/init.d/isc-dhcp-server6 not found. dpkg: warning: subprocess old pre-removal script returned error exit status 100 dpkg: trying script from the new package instead ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused invoke-rc.d: unknown initscript, /etc/init.d/isc-dhcp-server6 not found. dpkg: error processing archive /var/cache/apt/archives/isc-dhcp-server_4.3.1-5ubuntu3_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 100 This is because both new and old packages include the following in the prerm: # Automatically added by dh_installinit if [ -x "/etc/init.d/isc-dhcp-server6" ] || [ -e "/etc/init/isc-dhcp-server6.conf" ]; then invoke-rc.d isc-dhcp-server6 stop || exit $? fi # End automatically added section This code will never succeed on a system running systemd. It may be that debhelper's behavior here should be changed. However, as we have two upstart jobs in the package for a reason, I think the more important fix is to split the init script. This will then also require some particular upgrade handling in the prerm since the prerm runs before any new /etc/init.d/isc-dhcp-server6 script would be unpacked. It's also worth noting that this problem was apparently not picked up by the reports about packages missing init scripts; presumably because the isc-dhcp-server has an init script, but not init scripts matching all of the included upstart jobs. https://people.canonical.com/~jhunt/systemd/packages-to-convert/2015-08-17.txt ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: isc-dhcp-server 4.3.1-5ubuntu2.2 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 17 02:58:14 2015 InstallationDate: Installed on 2010-09-24 (1787 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: isc-dhcp UpgradeStatus: Upgraded to wily on 2015-08-17 (0 days ago) modified.conffile..etc.dhcp.dhcpd.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2013-09-19T21:48:37.910820 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1485396/+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 2039083] Re: "optional: true" flag introduces problem it's meant to fix in certain circumstances
So if I understand correctly, this does not affect Focal or Bionic. It also does not affect Mantic or Noble. We're just hitting this issue on Jammy = systemd v249.11 (and probably Lunar = systemd v252.5). Netplan's behavior seems to be correct, here. It writes sensible configuration for systemd-networkd. The issue is in (upstream) systemd, which blocks on an empty list, which it shouldn't. That behavior is apparently fixed in systemd v253. I think we should not try to work around this systemd behaviour in Netplan, but either live with the upstream behavior for v249 or backport the fixes from systemd v253 into Jammy. ** Tags added: rls-jj-incoming ** Changed in: netplan Status: Triaged => Invalid -- 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/2039083 Title: "optional: true" flag introduces problem it's meant to fix in certain circumstances Status in netplan: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: Hello! This bug is in relation to the situation where the "systemd-networkd- wait-online.service" hangs for several minutes on boot before eventually failing. I guess I don't know if this flag was introduced specifically for this situation, but I do know that one of the fixes for this issue is to add "optional: true" to any non-critical interfaces (as per the docs[1]). While this may be the case, it just so happens that adding this flag to an interface when it's the only configured interface in netplan can actually INTRODUCE the issue as well. Example: --- :~# grep -Ev "^#" /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: enp5s0: dhcp4: true optional: true --- The above config will cause the service hang/failure, and the removal of the flag will resolve the issue. I primarily opened this bug report with the idea that we might update aforementioned documentation to include a caveat that you want to avoid adding this flag to the only configured interface. However, it was also discussed that we might consider having the netplan config parser complain about such a setup and consider it invalid, which it kinda is. I believe in a situation where you may have a server that should have NO network connectivity, you would simply leave netplan unconfigured and/or stop any relevant services, rather than try to configure all interfaces as optional. My original test was on Jammy, though I tested this also on Focal and Bionic, and neither of those appear to be affected by this - setting the only interface as optional in either of those does not cause the "systemd-networkd-wait-online" service to hang and the system boots normally. Let me know if you'd like/need any more info from me! Thank you! [1] https://netplan.io/faq#prevent-waiting-for-interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2039083/+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 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface
This should have been fixed upstream as of https://github.com/canonical/netplan/pull/371 and should be fixed in Mantic. Can you still re-produce this issue today? ** Changed in: netplan.io (Ubuntu) Status: In Progress => Fix Released -- 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/2024661 Title: Unable to configure Wireguard connection at NetworkManager interface Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Bug description: Repro steps: 1) Open NetworkManager GUI. 2) Click "Add new Connection" and select "Wireguard" connection type. 3) Then you have to configure new connection. Basic configuration looks like that: a) Write down connection name, b) Write down local private key, c) Create new peer and populate peer's parameters: public key of the peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port. 4) Click "OK" and "Save". 5) Open "Peers" again. Ensure that settings were not stored. All fields are empty. Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager interface. netplan.io 0.106.1-2 network-manager 1.42.4-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
I just did remove all the wireguard connections and recreated them. Actually I found out that as long as I keep counting up on the wgX, everything works smooth. But whenever I reuse a wg, it messes it all up and nm is dying. -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 1920933] Re: live desktop system booted with ip=dhcp has the right lease, hostname not set at all
Netplan is not involved with setting the hostname at all. Marking invalid for that package. ** Changed in: netplan.io (Ubuntu) Status: New => Invalid -- 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/1920933 Title: live desktop system booted with ip=dhcp has the right lease, hostname not set at all Status in initramfs-tools package in Ubuntu: New Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Here the cmdline: vmlinuz initrd=initrd rootfstype=nfs netboot=nfs nfsroot=162.38.151.26:/exports/focal-desktop boot=casper ip=dhcp fsck.mode=skip automatic-ubiquity url=http://162.38.151.26/preseed/fds/focal-efi.seed File /run/systemd/netif/leases/2: # This is private data. Do not parse. ADDRESS=162.38.80.32 NETMASK=255.255.248.0 ROUTER=162.38.80.1 SERVER_ADDRESS=162.38.87.254 NEXT_SERVER=162.38.151.26 T1=7200 T2=12600 LIFETIME=14400 DNS=162.38.151.23 162.38.151.24 NTP=193.51.157.3 DOMAINNAME=fdsetu.infra.domain.fr DOMAIN_SEARCH_LIST=infra.domain.fr fdsetu.infra.domain.fr HOSTNAME=focal-uefi CLIENTID=0152540071e1f2 But the hostname is still the default one "ubuntu" $ hostnamectl Static hostname: ubuntu Icon name: computer-vm Chassis: vm Machine ID: cbb8d889829d4e2594ab55a53749e7e9 Boot ID: c93c8cc26fa040f6b010077e676bf7ec Virtualization: kvm Operating System: Ubuntu 20.04.2 LTS Kernel: Linux 5.8.0-43-generic Architecture: x86-64 It should be "focal-uefi". I had the same issue with ubuntu server autoinstall See https://bugs.launchpad.net/subiquity/+bug/1905932 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.4 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperVersion: 1.445.1 Date: Tue Mar 23 15:30:42 2021 LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: vmlinuz initrd=initrd rootfstype=nfs netboot=nfs nfsroot=162.38.151.26:/exports/focal-desktop boot=casper ip=dhcp fsck.mode=skip automatic-ubiquity url=http://162.38.151.26/preseed/fds/focal-efi.seed SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1920933/+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 2044795] Re: Please merge openssl 3.1.4-2 from debian unstable
Openssl's support policy means we won't be using a non-LTS version in Ubuntu. There's a small window where we might use a non-LTS version provided we are sure we can upgrade to an LTS version of openssl in time for our own LTS but at the moment this situation has not happened yet. Openssl 3.1 is not an LTS, nor is 3.2 (released a few days ago), and it is not known if 3.3 will be. By the way, 3.3 should be released in April, almost in time for our LTS, but again, we don't know if it will also be an LTS release. As a consequence, we are unfortunately most likely going with 3.0 in 24.04, and every subsequent ubuntu release until we know we will have an LTS in time for our 26.04 (because we can't "downgrade" openssl version for our LTS releases). In the future it is possible that we introduce "openssl-latest" or something like that in order to track most recent releases but without any support guarantee. This would be a completely separate package. In any case, I hadn't noticed that 3.1.* had been uploaded to Debian unstable. I was assuming that the debian maintainers would stick to 3.0 for the same reasons as I outlined above. It's possible they're betting they will have an openssl LTS release in time for trixie's release since trixie might be out in 2025 and by that time openssl 3.0 will roughly reach EOL, and a new openssl LTS would be needed. I guess we'll have to discuss which openssl version to use post-24.04 but probably not before 24.04 is released. I'm going to re-write this report as something post 24.04 since we can't do anything before 24.04 sadly. ** Changed in: openssl (Ubuntu) Milestone: None => later ** Summary changed: - Please merge openssl 3.1.4-2 from debian unstable + Please merge openssl from debian unstable ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- 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/2044795 Title: Please merge openssl from debian unstable Status in openssl package in Ubuntu: Confirmed Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2044795/+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 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted
** Changed in: netplan.io (Ubuntu) Status: Triaged => Invalid -- 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/2040153 Title: Network Manager will not remove Netplan YAMLs when connections are deleted Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Released Status in netplan.io source package in Mantic: Invalid Status in network-manager source package in Mantic: Fix Released Bug description: [ Impact ] Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete Network Manager connections persistently. That means that, when the connection is deliberately deleted by the user, it will re-appear when the system is rebooted or netplan apply is executed. This is happening because the systemd service unit is setting the property "ProtectSystem" to true. Because of that, /usr is being presented to the Network Manager daemon as read-only. When connections are deleted, libnetplan will try to open its YAML files with writing permissions and will fail for files from /usr/lib/netplan. Even if the user hasn't added any files there manually, the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by the package ubuntu-settings. This issue is fixed by allow-listing /usr/lib/netplan with ReadWritePaths=/usr/lib/netplan in systemd so the Network Manager's daemon will be able to write to that directory. This upload also improves the autopkgtests related to Netplan. Network Manager will be started by systemd, which ensures we are testing in the same environment conditions used by a desktop installation. It also adds a few more instances of connections deletions so we can test a bit more that YAML files are being removed. It also adds all the dependencies required by the test script (which sadly was causing the nm_netplan.py tests to be skipped). [ Test Plan ] Launch a new Mantic VM: $ lxc launch ubuntu:mantic --vm Install network-manager and ubuntu-settings: # apt install network-manager ubuntu-settings Run Netplan # netplan apply Create a dummy connection via nmcli: # nmcli con add type dummy connection.interface-name dummy0 Check a new YAML will be created in /etc/netplan Delete the connection with nmcli # nmcli con del dummy-dummy0 Check the YAML WAS NOT removed from /etc/netplan You will see the error below in the NetworkManager's journal netplan_delete_connection: Cannot write output state: Read-only file system Add the PPA containing the fix and run the same test described above # add-apt-repository ppa:danilogondolfo/network-manager # apt update # apt upgrade Check that the YAML will be created when the connection is added and deleted and the connection is removed. [ Where problems could occur ] As the only change is a relaxation of the restrictions applied by systemd on the environment where Network Manager runs, we are not expecting any regression. As for the changes in the autopkgtest related to Netplan, they are passing on all architectures. Autopkgtests amd64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz ppc64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz s390x - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz arm64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/arm64/n/network-manager/20231024_084542_ac017@/log.gz armhf - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/armhf/n/network-manager/20231024_083545_ac017@/log.gz [ Other Info ] --- Original description --- When a connection is deleted using any NM facility, libnetplan is failing to delete the YAML file. Because of that, the connection will be recreated when "netplan generate" runs again. This is probably being caused by a combination of two things. First, the NM's systemd unit has this setting "ProtectSystem=true", which will mount /usr as read-only for NM. Second, we migrated the default "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1]. When libnetplan tries to open this file for writing, the open system fails with EROFS: --- 22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system) 22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76 --- [1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1 To manage
[Touch-packages] [Bug 2044795] [NEW] Please merge openssl 3.1.4-2 from debian unstable
Public bug reported: tracking bug ** Affects: openssl (Ubuntu) Importance: Wishlist Assignee: Ravi Kant Sharma (ravi-sharma) Status: New ** Summary changed: - Please merge openssl 3.1.4-2 from debian unstable + Please merge openssl 3.1.4-2 into noble ** Changed in: openssl (Ubuntu) Assignee: (unassigned) => Ravi Kant Sharma (ravi-sharma) ** Summary changed: - Please merge openssl 3.1.4-2 into noble + Please merge openssl 3.1.4-2 from debian unstable ** Changed in: openssl (Ubuntu) Importance: Undecided => Wishlist -- 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/2044795 Title: Please merge openssl 3.1.4-2 from debian unstable Status in openssl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2044795/+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 1485396] Re: impossible to upgrade package from vivid to wily because of maintainer script reference to upstart job without matching init script
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Since this bug only affected upgrades, the time to fix has passed. So I am marking this bug as invalid. ** Changed in: isc-dhcp (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1485396 Title: impossible to upgrade package from vivid to wily because of maintainer script reference to upstart job without matching init script Status in isc-dhcp package in Ubuntu: Invalid Bug description: The isc-dhcp-server package is not upgradable on a real machine (vs. a chroot) in vivid or wily, because it installs two upstart jobs in the usual debhelper way, but only one of them has a matching init script. As a result, on a system with systemd as init, isc-dhcp-server will fail to even unpack over a running system: Preparing to unpack .../isc-dhcp-server_4.3.1-5ubuntu3_amd64.deb ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused invoke-rc.d: unknown initscript, /etc/init.d/isc-dhcp-server6 not found. dpkg: warning: subprocess old pre-removal script returned error exit status 100 dpkg: trying script from the new package instead ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused invoke-rc.d: unknown initscript, /etc/init.d/isc-dhcp-server6 not found. dpkg: error processing archive /var/cache/apt/archives/isc-dhcp-server_4.3.1-5ubuntu3_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 100 This is because both new and old packages include the following in the prerm: # Automatically added by dh_installinit if [ -x "/etc/init.d/isc-dhcp-server6" ] || [ -e "/etc/init/isc-dhcp-server6.conf" ]; then invoke-rc.d isc-dhcp-server6 stop || exit $? fi # End automatically added section This code will never succeed on a system running systemd. It may be that debhelper's behavior here should be changed. However, as we have two upstart jobs in the package for a reason, I think the more important fix is to split the init script. This will then also require some particular upgrade handling in the prerm since the prerm runs before any new /etc/init.d/isc-dhcp-server6 script would be unpacked. It's also worth noting that this problem was apparently not picked up by the reports about packages missing init scripts; presumably because the isc-dhcp-server has an init script, but not init scripts matching all of the included upstart jobs. https://people.canonical.com/~jhunt/systemd/packages-to-convert/2015-08-17.txt ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: isc-dhcp-server 4.3.1-5ubuntu2.2 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 17 02:58:14 2015 InstallationDate: Installed on 2010-09-24 (1787 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: isc-dhcp UpgradeStatus: Upgraded to wily on 2015-08-17 (0 days ago) modified.conffile..etc.dhcp.dhcpd.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2013-09-19T21:48:37.910820 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1485396/+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 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes
** Changed in: isc-dhcp (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1664352 Title: dhclient-script doesn't use configured metric for rfc3442 classless routes Status in isc-dhcp package in Ubuntu: Fix Committed Status in isc-dhcp package in Debian: New Bug description: lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy isc-dhcp-client isc-dhcp-client: Installed: 4.3.3-5ubuntu12.6 Candidate: 4.3.3-5ubuntu12.6 Version table: *** 4.3.3-5ubuntu12.6 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 4.3.3-5ubuntu12 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages If the metric option is set in interfaces(5), dhclient is executed with the variable IF_METRIC set to the configured administrative metric. The exit-hook rfc3442-classless-routes doesn't use the variable; thus, a multi-interface box will experience a race condition if multiple interfaces are supplied with one or more duplicate rfc3442 routes. The attached patch adds support for IF_METRIC handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1664352/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2
verification-needed-jammy-linux-lowlatency-hwe-6.5
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
Fix Released
Status in MAAS:
Fix Released
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in systemd source package in Lunar:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
This bug is awaiting verification that the linux-lowlatency- hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency- hwe-6.5'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy- linux-lowlatency-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 verification-needed-jammy-linux-lowlatency-hwe-6.5 -- 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/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: Confirmed Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2029410] Re: File dialog: using mouse buttons 4/5 to go back/forward?
** Changed in: gtk Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2029410 Title: File dialog: using mouse buttons 4/5 to go back/forward? Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Hello. I just realised that I have tried subconsciously several times now to use the same mechanism that's available in browsers, to move back and forward through page history, when I have been using the GTK file dialog, in an attempt to move back to the previous directory I was in. I am wondering if this there is any potential this mechanism could be included in the GTK file dialog at some point in the future? I'm guessing many folk are now familiar with this from their browser use that it would benefit. Thanks for your time. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2029410/+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 2044420] Re: gtkpod segfaults when attempting to display songs
** Changed in: glib Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2044420 Title: gtkpod segfaults when attempting to display songs Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Triaged Status in gtkpod package in Ubuntu: New Status in glib2.0 source package in Mantic: Triaged Status in gtkpod source package in Mantic: New Status in glib2.0 source package in Noble: Triaged Status in gtkpod source package in Noble: New Bug description: Open gtkpod, and select your ipod from the list. If it has more than one screenfull of songs to display in the list, gtkpod will immediately segfault. I haven't found a workaround yet. Broken on Mantic, works on Lunar. Thread 1 "gtkpod" received signal SIGSEGV, Segmentation fault. __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 <_nl_global_locale>) at ../string/strxfrm_l.c:685 685 ../string/strxfrm_l.c: No such file or directory. (gdb) bt #0 __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 <_nl_global_locale>) at ../string/strxfrm_l.c:685 #1 0x770c5a5e in g_utf8_collate_key () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x77f852ec in fuzzy_skip_prefix () at /lib/x86_64-linux-gnu/libgtkpod.so.1 #3 0x7fffa80980ca in ??? () at /usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so #4 0x7fffa80997fd in normal_sort_tab_page_add_track () at /usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so #5 0x7fffa8099526 in normal_sort_tab_page_add_track () at /usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so #6 0x7fffa809f196 in sorttab_display_select_playlist_cb () at /usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so #7 0x7718d130 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x771ba4ac in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x771ab9b1 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x771abbd6 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x771abc93 in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x77f67e4b in gtkpod_set_current_playlist () at /lib/x86_64-linux-gnu/libgtkpod.so.1 #13 0x7fffa807cce0 in ??? () at /usr/lib/x86_64-linux-gnu/gtkpod/libplaylist_display.so #14 0x7708ba11 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x770e746f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7708c46f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x777f61ed in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #18 0xea1f in main () To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2044420/+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 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes
** Changed in: isc-dhcp (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1664352 Title: dhclient-script doesn't use configured metric for rfc3442 classless routes Status in isc-dhcp package in Ubuntu: Fix Committed Status in isc-dhcp package in Debian: New Bug description: lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy isc-dhcp-client isc-dhcp-client: Installed: 4.3.3-5ubuntu12.6 Candidate: 4.3.3-5ubuntu12.6 Version table: *** 4.3.3-5ubuntu12.6 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 4.3.3-5ubuntu12 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages If the metric option is set in interfaces(5), dhclient is executed with the variable IF_METRIC set to the configured administrative metric. The exit-hook rfc3442-classless-routes doesn't use the variable; thus, a multi-interface box will experience a race condition if multiple interfaces are supplied with one or more duplicate rfc3442 routes. The attached patch adds support for IF_METRIC handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1664352/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
Hello Danilo, sorry for the late reply - yes, there are more than one connections with wg0. But this should not be an issue as long as only one connection is enabled at a time. Yes, it's very likely that I was hit by this bug. Do you think it's a good idea to remove all the wireguard-config-files from /etc/netplan and recreate them? Is it possible to use wg0 multiple times then? Thank you! -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 1543799] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files
** Changed in: isc-dhcp (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1543799 Title: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files Status in isc-dhcp package in Ubuntu: Fix Committed Status in isc-dhcp source package in Xenial: Triaged Status in isc-dhcp source package in Bionic: Triaged Status in isc-dhcp source package in Cosmic: Won't Fix Status in isc-dhcp source package in Disco: Won't Fix Bug description: dhcpd reports 'Can't create PID file /run/dhcp-server/dhcpd.pid' (or '/run/dhcp-server/dhcpd6.pid' for isc-dhcp-server6), and no file is found /run/dhcp-server. Additionally, both isc-dhcp-server & isc-dhcp-server6 service unit files specify the RuntimeDirectory 'dhcp-server', which is removed when either unit stops (and thus would wipe out the other unit's pid file, were it being successfully written). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-server 4.3.3-5ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 9 21:34:08 2016 InstallationDate: Installed on 2016-02-09 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dhcp.dhcpd.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2016-02-09T21:11:20.104056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543799/+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 1704174] Re: update apparmor rules to include wicd's dhclient.conf file
Thank you for taking the time to report this bug and helping to make Ubuntu better. The wicd package has been removed in Ubuntu 20.04 LTS "Focal Fossa". So I am closing this bug as Invalid. ** Changed in: isc-dhcp (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1704174 Title: update apparmor rules to include wicd's dhclient.conf file Status in isc-dhcp package in Ubuntu: Invalid Bug description: Package: isc-dhcp-client Version: 4.3.5-3ubuntu Arch: amd64 Release: artful Report == The apparmor rules for /sbin/dhclient are missing an entry for wicd's dhclient.conf file, see the log bellow: audit: type=1400 audit(1499962030.711:50): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/var/lib/wicd/dhclient.conf" pid=16339 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Expected result === /sbin/dhclient should be allowed to read from /var/lib/wicd/dhclient.conf Other = Patch has been attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1704174/+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 1371833] Re: dhclient is unable to parse zero-length option values (breaks DHCPv6)
This patch has been applied in the meantime. isc-dhcp 4.4.1-2.3ubuntu2 in Ubuntu 22.04 (jammy) carries it. ** Changed in: isc-dhcp (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1371833 Title: dhclient is unable to parse zero-length option values (breaks DHCPv6) Status in isc-dhcp package in Ubuntu: Fix Released Status in dhcp package in Fedora: Fix Released Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 isc-dhcp-client: Installed: 4.2.4-7ubuntu12 Candidate: 4.2.4-7ubuntu12 Version table: *** 4.2.4-7ubuntu12 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Any option with a zero-length value, ie the common DHCPv6 option: option dhcp6.reconf-accept ; with isc-dhcp-client_4.2.4 produces a parser failure: dhclient: /var/lib/NetworkManager/dhclient6-...-wlan0.lease line 35: semicolon expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1371833/+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 1446103] Re: upstart vs sysV init script pid-file-name conflict
Upstart support has been removed in Ubuntu 17.04 "Zesty Zapus". ** Changed in: isc-dhcp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1446103 Title: upstart vs sysV init script pid-file-name conflict Status in isc-dhcp package in Ubuntu: Fix Released Bug description: Hi, the pid-file-name for upstart is hardcoded in /etc/init/isc-dhcp- server.conf to "/run/dhcp-server/dhcpd.pid" while /etc/init.d/isc- dhcp-server tries to parse "/etc/dhcp/dhcpd.conf" (and fails due to an regex error) for the setting "pid-file-name" and defaults back to "/var/run/dhcpd.pid" (which does not exist if started by upstart). So the sysV script reports incorrectly that the isc-dhcp-server is not running and/or that it failed to stop the already running isc-dhcp- server daemon. cut-- root@d01-svi-22:/proc/1265# ps -efa | grep dhc dhcpd 1265 1 0 Apr07 ?00:00:30 dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf eth0 ntp 10244 1 0 Apr14 ?00:01:01 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -c /var/lib/ntp/ntp.conf.dhcp -u 105:112 root 21809 21382 0 09:16 pts/200:00:00 grep --color=auto dhc root@d01-svi-22:/proc/1265# bash -x /etc/init.d/isc-dhcp-server stop + PATH=/sbin:/bin:/usr/sbin:/usr/bin + test -f /usr/sbin/dhcpd + DHCPD_DEFAULT=/etc/default/isc-dhcp-server + '[' '!' -f /etc/default/isc-dhcp-server ']' + . /lib/lsb/init-functions +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)' ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']' ++ . /lib/lsb/init-functions.d/20-left-info-blocks ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)' ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']' ++ . /lib/lsb/init-functions.d/50-ubuntu-logging +++ LOG_DAEMON_MSG= ++ FANCYTTY= ++ '[' -e /etc/lsb-base-logging.sh ']' ++ true + '[' -f /etc/default/isc-dhcp-server ']' + . /etc/default/isc-dhcp-server ++ INTERFACES=eth0 + NAME=dhcpd + DESC='ISC DHCP server' + DHCPD_CONF=/etc/dhcp/dhcpd.conf + '[' -z '' ']' ++ sed -n -e 's/^[ \t]*pid-file-name[ \t]*"(.*)"[ \t]*;.*$/\1/p' ++ head -n 1 + DHCPD_PID= + DHCPD_PID=/var/run/dhcpd.pid + case "$1" in + log_daemon_msg 'Stopping ISC DHCP server' dhcpd + '[' -z 'Stopping ISC DHCP server' ']' + log_use_fancy_output + TPUT=/usr/bin/tput + EXPR=/usr/bin/expr + '[' -t 1 ']' + '[' xxterm-256color '!=' x ']' + '[' xxterm-256color '!=' xdumb ']' + '[' -x /usr/bin/tput ']' + '[' -x /usr/bin/expr ']' + /usr/bin/tput hpa 60 + /usr/bin/tput setaf 1 + '[' -z ']' + FANCYTTY=1 + case "$FANCYTTY" in + true + /usr/bin/tput xenl ++ /usr/bin/tput cols + COLS=106 + '[' 106 ']' + '[' 106 -gt 6 ']' ++ /usr/bin/expr 106 - 7 + COL=99 + log_use_plymouth + '[' n = y ']' + plymouth --ping + printf ' * Stopping ISC DHCP server dhcpd ' * Stopping ISC DHCP server dhcpd ++ /usr/bin/expr 106 - 1 + /usr/bin/tput hpa 105 + printf ' ' + start-stop-daemon --stop --quiet --pidfile /var/run/dhcpd.pid + log_end_msg 1 + '[' -z 1 ']' + '[' 99 ']' + '[' -x /usr/bin/tput ']' + log_use_plymouth + '[' n = y ']' + plymouth --ping + printf '\r' + /usr/bin/tput hpa 99 + '[' 1 -eq 0 ']' + printf '[' [+ /usr/bin/tput setaf 1 + printf fail fail+ /usr/bin/tput op + echo ']' ] + return 1 + rm -f /var/run/dhcpd.pid + exit 0 root@d01-svi-22:/proc/1265# cat /var/run/dhcpd.pid cat: /var/run/dhcpd.pid: No such file or directory root@d01-svi-22:~# status isc-dhcp-server isc-dhcp-server start/running, process 1265 root@d01-svi-22:~# stop isc-dhcp-server isc-dhcp-server stop/waiting root@d01-svi-22:~# status isc-dhcp-server isc-dhcp-server stop/waiting cut-- Even if you add the pid-file-name setting to your dhcpd.conf the sysV script fails to determine the correct pidfile due to a regex error as shown below: cut-- root@d01-svi-22:/etc/dhcp# /etc/init.d/isc-dhcp-server status Status of ISC DHCP server: dhcpd is not running. root@d01-svi-22:/etc/dhcp# sed -n -e 's/^[ \t]*pid-file-name[ \t]*"(.*)"[ \t]*;.*$/\1/p' < /etc/dhcp/dhcpd.conf sed: -e expression #1, char 49: invalid reference \1 on `s' command's RHS root@d01-svi-22:/etc/dhcp# grep pid-file-name /etc/dhcp/dhcpd.conf pid-file-name
[Touch-packages] [Bug 2044726] [NEW] no abre aplicaciones
Public bug reported: al intenar abrir whatsapp desde una cuenta instagram arroja error xorg ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Mon Nov 27 07:10:10 2023 DistUpgraded: 2023-05-05 04:55:30,841 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1019:7dd9] MachineType: Inspur Inspur Computer ProcEnviron: LANGUAGE=es_VE:es TERM=qterminal PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=015299ef-91dd-42b5-bbbc-f9da188b591e ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2023-05-05 (206 days ago) dmi.bios.date: 06/26/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.name: Inspur Computer All in one PC dmi.board.vendor: Inspur dmi.board.version: V1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/26/2014:br4.6:svnInspur:pnInspurComputer:pvr:rvnInspur:rnInspurComputerAllinonePC:rvrV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:sku: dmi.product.name: Inspur Computer dmi.sys.vendor: Inspur version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 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.2 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 xserver.bootTime: Mon Nov 27 06:50:00 2023 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:21.1.4-2ubuntu1.7~22.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2044726 Title: no abre aplicaciones Status in xorg package in Ubuntu: New Bug description: al intenar abrir whatsapp desde una cuenta instagram arroja error xorg ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Mon Nov 27 07:10:10 2023 DistUpgraded: 2023-05-05 04:55:30,841 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1019:7dd9] MachineType: Inspur Inspur Computer ProcEnviron: LANGUAGE=es_VE:es TERM=qterminal PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=015299ef-91dd-42b5-bbbc-f9da188b591e ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2023-05-05 (206 days ago) dmi.bios.date: 06/26/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.name: Inspur Computer All in one PC dmi.board.vendor: Inspur dmi.board.version: V1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/26/2014:br4.6:svnInspur:pnInspurComputer:pvr:rvnInspur:rnInspurComputerAllinonePC:rvrV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:sku: dmi.product.name: Inspur Computer dmi.sys.vendor: Inspur version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
