[Desktop-packages] [Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
Thanks for the great debug work so far already, I think it is "apparmor or kernel" enough that we should add those packages and subscribe a few folks we know dealing with those details - I'd start with jjohansen as he'd be the best to map us to either knowledge or a known case. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE Status in apparmor package in Ubuntu: New Status in cups package in Ubuntu: Confirmed Status in rsyslog package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Bug description: What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode. And the apparmor profile does already have rules to allow that access - only after running aa-disable can the service start fine - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/..". - When we add rules to the profile using "/systemd/" (i.e., also dropping the /run prefix), then it works - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060035] Re: [MIR] msgraph
Final state check: - FFE was approved as well. - MIR approved - Per [2] it seems was consciously (freeze) accepted 15h ago. - All dependencies are already in main (could have changed) - Seen in component mismatches due to [2] - The needed exclude needed is in place [1] Only one version in noble msgraph | 0.2.1-0ubuntu3 | noble/universe | source Override component to main msgraph 0.2.1-0ubuntu3 in noble: universe/libs -> main Override [y|N]? y 1 publication overridden. Override component to main gir1.2-msg-0 0.2.1-0ubuntu3 in noble amd64: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble arm64: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble armhf: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble i386: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble ppc64el: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble riscv64: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble s390x: universe/introspection/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble amd64: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble arm64: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble armhf: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble i386: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble ppc64el: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble riscv64: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble s390x: universe/libs/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble amd64: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble arm64: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble armhf: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble i386: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble ppc64el: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble riscv64: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble s390x: universe/doc/optional/100% -> main Override [y|N]? y 21 publications overridden. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=d5078daf38e46b458c2d308ae86f6b9630c50102 [2]: https://launchpad.net/ubuntu/+source/gvfs/1.54.0-1ubuntu1 ** Changed in: msgraph (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to msgraph in Ubuntu. https://bugs.launchpad.net/bugs/2060035 Title: [MIR] msgraph Status in msgraph package in Ubuntu: Fix Released Bug description: [Availability] The package msgraph is already in Ubuntu universe. The package msgraph build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/msgraph [Rationale] - The package msgraph is required in Ubuntu main to be able to enable Microsoft OneDrive support in GNOME - The package msgraph will generally be useful for a large part of our user base - There is no other/better way to solve this that is already in main or should go universe->main instead of this. - The binary package libmsgraph-0-1 needs to be in main to turn on the onedrive support in gnome-online-accounts - We would like to enable the onedrive support in 24.04.1 if possible but it's not an hard commitment. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Security has been kept in mind and common isolation/risk-mitigation patterns are in place utilizing the following features: TBD (add details and links/examples about things like dropping permissions, using temporary environments, restricted users/groups, seccomp, systemd isolation features, apparmor, ...) - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpadlibrarian.net/720553048/buildlog_ubuntu-noble-amd64.msgraph_0.2.1-0ubuntu1_BUILDING.txt.gz < to be updated once the infra catches up with the recent upload > - The package runs an
[Desktop-packages] [Bug 2060361] Re: Dateisysten
Nautilus Problem, möglich. Kernel problem, halte ich für unwahrscheinlich aber nicht unmöglich. Sicher ist allerdings das ohne Nachvollziehbare Schritte hier leider keine weiterhelfen kann. Ich aktualisiere den Fall dazu passend, aber ohne weitere Info wird leider nichts mehr passieren. P.S. Ich halte es auch immer noch für möglich das es eine Unsicherheit/Unklarheit bei der verwendung ist und alles eigentlich OK ist. Doch auch das kann man ohne Nachvollziehbares nicht prüfen. ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu) Status: New => Incomplete ** Changed in: cloud-images Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2060361 Title: Dateisysten Status in cloud-images: Invalid Status in nautilus package in Ubuntu: Incomplete Bug description: Wenn ich eine grosse Datei lösche wird dasDateisysten Nicht freigegeben To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2060361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057842] Re: FFe: freedp2 -> freerdp3 in main
MIR Team approval to replace freerdp2 with freerdp3 in main.
Both stay in the archive, only one will be released with noble being in main.
This comes with the discussed requirement of giving this chance a try to add at
least some QA.
Right now tests are disabled at build and no autopkgtest is present.
Jbicha said tests are fine but time is scarce.
But Seb was so kind to agree to spend efforts of the Team to add tests before
Noble is released.
To unblock things we approve "now" (to get things moved before beta
freeze), but want to hold you accountable to get the tests in place.
** Summary changed:
- FFe: freedp2 -> freerdp3 in main
+ FFe: [MIR] freedp2 -> freerdp3 in main
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2057842
Title:
FFe: [MIR] freedp2 -> freerdp3 in main
Status in gnome-remote-desktop package in Ubuntu:
Fix Committed
Status in remmina package in Ubuntu:
Fix Committed
Bug description:
Feature Freeze Exception Request
--
There are only 2 packages in Ubuntu main that use freerdp2: remmina and
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore
only one version of freerdp will be in main. freerdp2 will be demoted to
universe since many universe packages use it and are not prepared to switch to
freerdp3.
This also requests updating gnome-control-center to fully enable the
features of gnome-remote-desktop 46.
Impact
--
A headline feature of GNOME 46 is support as a Remote Desktop server without
requiring someone to already be logged in locally ("headless" mode). This
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires
freerdp3.
Impact if this does not happen
--
- We would need to patch gnome-control-center to use the older Remote Desktop
panel (or at least hide the new tab for Remote Login)
- We would need to keep using gnome-remote-desktop 45 instead of 46. The
gnome-remote-desktop upstream maintainers would be unhappy with this decision.
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may
require changes in gnome-remote-desktop for things to work well although a
simple test showed that basic remote desktop seems to work ok with the
mismatch. (See comment #1 from upstream developer.)
Why this did not land sooner
---
It required the packaging of a new source package freerdp3. And we had to do
this sooner than Debian. Sorry too many things to do before Feature Freeze and
this did not make it.
Affected Packages
-
- gnome-remote-desktop 45 -> 46
- gnome-control-center (to update the Remote Desktop settings page)
- remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not
work with freerdp 3.3 in my testing
- gnome-connections (build-dependency swap): Not required by other changes
and not in Main but makes sense to switch it also
Affected Flavors
Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center,
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships
gnome-control-center but this appears to be a bug since they ship
cinnamon-control-center and is likely already fixed in noble-proposed)
Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.
gnome-connections has no reverse dependencies or recommends.
Upstream Changes
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS
https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md
gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature
Freeze. It will be updated to 46.0. The relevant part here is whether we use
the 46~beta version of the Remote Desktop page or the 46.0 version.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS
Build Logs
--
I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA.
The PPA currently has noble-proposed disabled so that it is easily possible to
try this set of packages without dealing with the incomplete 32-bit time
transition in noble-proposed. In addition, the PPA has the affected packages
from this FFe.
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages
Testing Done
---
1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46
RC. Remote control worked.
2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
worked.
3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
control worked.
4. I added a new Remote Login test case to
[Desktop-packages] [Bug 2055198] Re: RM: please remove libmail-dkim-perl 1.20240124-1 from noble-proposed
Agreed as pre-discussed. Thanks for the paperwork here. Removing packages from noble-proposed: libmail-dkim-perl 1.20240124-1 in noble libmail-dkim-perl 1.20240124-1 in noble amd64 libmail-dkim-perl 1.20240124-1 in noble arm64 libmail-dkim-perl 1.20240124-1 in noble armhf libmail-dkim-perl 1.20240124-1 in noble i386 libmail-dkim-perl 1.20240124-1 in noble ppc64el libmail-dkim-perl 1.20240124-1 in noble riscv64 libmail-dkim-perl 1.20240124-1 in noble s390x Comment: Current approach to Ed25519 support is unmaintainable, stay at 1.20230212-1 (LP: #2055198) Remove [y|N]? y 1 package successfully removed. ** Changed in: libmail-dkim-perl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmail-dkim-perl in Ubuntu. https://bugs.launchpad.net/bugs/2055198 Title: RM: please remove libmail-dkim-perl 1.20240124-1 from noble-proposed Status in libmail-dkim-perl package in Ubuntu: Fix Released Bug description: Discussion: https://code.launchpad.net/~mirespace/ubuntu/+source/libmail-dkim- perl/+git/libmail-dkim-perl/+merge/460681 We want to ship noble with libmail-dkim-perl 1.20230212-1 which does not have Ed25519 support, and thus does not depend on libcryptx-perl which is in universe. The current situation with libmail-dkim-perl 1.20240124-1 creates a component mismatch because it depends on libcryptx-perl which is in universe. libmail-dkim-perl 1.20230212-1 which is in noble release at the moment does not depend on libcryptx-perl. The second part of this plan is to upload a no-change rebuild of libmail-dkim-perl 1.20230212-1ubuntu1 as soon as this removal is done, to block automatic syncs from debian which would just try to update it to 1.20240124-1 again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dkim-perl/+bug/2055198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
I've added a section to the release notes summing this up and linking back here and to some of the past links. ** Changed in: ubuntu-release-notes Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in cloud-images: New Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Opinion Status in irqbalance package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
FYI: updated ubuntu-meta, now in noble-proposed as version 1.532 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in cloud-images: New Status in Release Notes for Ubuntu: In Progress Status in Ubuntu on IBM z Systems: Opinion Status in irqbalance package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: In Progress Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
FYI: Seed change landed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in cloud-images: New Status in Release Notes for Ubuntu: In Progress Status in Ubuntu on IBM z Systems: Opinion Status in irqbalance package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: In Progress Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Steve was so kind reviewing and approving my proposal. Doing that now is also helpful as it should make sure it still has quite some exposure and thereby chances for people to report issues (vs if we'd land it much later like after beta freeze). Changes will: - change the seeds in regard to irqbalance, but no change to irqbalance (the package) - need an update of ubuntu-meta - IMHO we also want a release notes entry. - CPC might consider re-enabling it as image customization for some as shown in comment #39 I'm adjusting the bug tasks and state accordingly. ** Also affects: cloud-images Importance: Undecided Status: New ** Also affects: ubuntu-release-notes Importance: Undecided Status: New ** Changed in: ubuntu-release-notes Status: New => In Progress ** Changed in: ubuntu-z-systems Status: Confirmed => Opinion ** Changed in: irqbalance (Ubuntu) Status: Confirmed => Opinion ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in cloud-images: New Status in Release Notes for Ubuntu: In Progress Status in Ubuntu on IBM z Systems: Opinion Status in irqbalance package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: In Progress Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
While there was sadly neither enough time not enough resources to do all the deep dive analysis that could have been done, we succeeded by reaching out to many more parties and got their input as well. Thank you all! Since Noble feature freeze is coming we need to make a call either way. I proposed the underlying seed change [1]. And even once accepted that has to be followed by an update to ubuntu-meta. Furthermore we'd have more follow up, like enabling it in special cases like the AWS images for the reasons Fabio mentioned. Of course this is just a proposal. There are many other options left, from not changing anything to more subtle counters to my proposal like only doing so in 24.10 to give things more time, to holding back until someone found time/resource to gather more data. But for now, I feel "Not enabling it by default, but enabling selectively where identified to be wanted" seems to be the better choice - and that is what I proposed. [1]: https://code.launchpad.net/~paelzer/ubuntu- seeds/+git/platform/+merge/460904 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Interesting, that is more towards irqbalance than I heard so far. thanks Fabio! So we might end up needing to go like "Generally disabled except this list of places [...] where it stays enabled". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Hey Henry, thanks for chiming in and I agree in general that tech moved on. Myself and others said similar before, thanks for adding more details and voices - that is what such a discussion is about. > they just don't go ping-ponging around between In particular on this aspect, so much has happened with fast devices often not only "not being bottle-necked" but even I/O interaction routing smartly, I mentioned for example rps/xps on here before. Still, there are even today a few workloads - usually high utilization large scale loads that benefit. Thanks @John for carrying a few of them forward to this bug! But the more I read, the more people chime in, ... the more one pattern seems to crystallize (for me). I'll try to summarize my gut-feeling so far... (which is my opinion so far, not more): """ While it seems a few high intensity workloads still can benefit, those are of the kind that are usually hand-optimized and could easily pull-in irqbalance if needed. On the other hand the majority of workloads do not care either way - at least not in an easily provable way. And furthermore most of the need to have it in the past has been replaced by newer I/O architectures. Finally there also have been some cases that suffered from irqbalance being enabled. Those cases in particular seem to be those of end-users, often Desktop end users that might not always tune their system intensely. For consistency between Server and Desktop I'd prefer to change it in both in the same way, while the cases still benefiting all where server'ish there hasn't been a case that would need it by default. Overall that makes me think that we could indeed change it to not be enabled by default anymore in the upcoming Noble release. """ I know that Steve (@vorlon) wanted to comment on this as well, maybe we have sufficient statements, opinions and at least a bit of data so far to have a decision for Noble before Feature freeze? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
On Fri, Feb 16, 2024 at 06:51:46PM -, Philip Roche wrote: > @vorlon @jchittum @paelzer given the above findings are you still -1 on > any snap preseeding? Based on the data, I vote not to preseed any snaps. I was already leaning that way and thank you for adding the data. I agree to not to preseed any snap (in images where no mandatory snaps are present, i.e. not those agent examples you brought up above - these would stay as is right?). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
It was nice to have LXD around and ready for many test/dev workloads, and I feel it was worth it back then. But we already replaced it with lxd-installer in minimal environments and it was fine there too. I never heard someone complaining that LXD takes a bit there, but every second of boot time seems to be valued highly. Now that we had to reduce this to the lxd-installer everywhere (Due to LP #2051346) it is really worth to be re-revaluated. Thank you for driving this Phil! IMHO now that your first LXD command will take a bit longer already (due to fetching LXD snap), the exact amount of that "a bit longer" (as being more by also fetching snapd and base) seems almost irrelevant as long as it is in the same ballpark. On one hand those dev/test environments that use it most, can easily be made to tolerate the bit of extra time - they usually start with a barrage of other "install this" anyway that has the same "wait for network and install" characteristic. On the other hand reducing size and the initialization effort of it will save transfer and startup time for everyone - the guessed 3-5 seconds mentioned/assumed above would be totally worth it IMHO. --- Furthermore as Simon showed (thanks), by snapd being a baseless snap we'd not even gain something by having that around already for the latter fetch of lxd by lxd-installer. --- I further appreciate John's comment that we should back up some of our current assumptions (how much will this slow down lxc interactions, how much will the boot speed gain) with some actual data. But if that data will not totally upset what we expect, then I very much agree with Steve in comment #1 and would not optimize for it at the cost of all others and thereby I'd be fine to not preseed the other bits there. --- P.S. I wanted to mention that our perception might also be biased. I believe (no data) that the closer to Ubuntu development itself you are, the more likely you use LXD heavily in testing. But that same ratio likely does not apply to any user of Ubuntu images in the world. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
FYI, multiple parties and people promised me more input, but so far none has arrived over the last weeks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Since the discussion is no more only covering Desktop I updated the title (thanks Seb128 for suggesting) ** Summary changed: - Consider removing irqbalance from default install on desktop images + Please consider no more having irqbalance enabled by default (per image/use-case/TBD) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Etanay, I realize I maybe wrote too much :-/ So I start with a TL;DR: AFAICS you are right in all you say, but I think there can not be "one right answer" anyway. Hence I'm trying to leave all parties their freedom of defining what is important to them and try to learn from them what impact irqbalance has to that. > Yes I was not arguing strictly against irqbalance, just trying > to ascertain some discussion parameters as well as parameters for data > collection. Yeah, I see that and didn't intend to rebut your statements either. Just push them a bit into potential context and POV of others. > I have not yet seen a coherent philosophy on what it means to "optimize > performance" with default settings that serve the greatest capacity of > server or desktop scenarios. That is true, but the reason for that is that you can only optimize for something like a workload or particular HW. The defaults are usually trying to be not too crappy for any possible thing that might happen on e.g. Ubuntu which is quite a scope. > In my humble opinion, data collection is useless without this > framework of understanding what it is we are trying to achieve > and why in terms of system performance. To me this is the deeper > unresolved issue, perhaps. I can see your point and would not even argue against. But this is (this is opinion and a bit of experience, not scientific proven truth) only the problem if we'd try to solve the singular global and always valid "is irqbalance good or bad" question. Thinking about it I think I'm even of the same opinion than you, but instead of standardizing excatly what we are trying to achieve (which to me feels like selecting a workload or HW as optimization target) I was trying to reach out to as many groups as possible so we can see what HW/workloads are important to them and how irqbalance might help or interfere with that. A bit like the old case where some clouds brought it up that it is conflicting in virtio-net on their substrate and to be disabled by default there (see Debian and also some Ubuntu cloud images). I have personally no hope in reaching a general "this is good / bad" without considering it per workload or HW environment. Hence my hope is that if we manage to get this variety of preferences of different parties and only then the impact of irqbalance to that we can make compartmentalized decisions. For example as some suggested, making it no more the default in Desktop, but keeping it in other cases. And this is just me trying to be helpful and drive this from being a dormant case to something useful, I do not pretend to have the masterplan or the solution yet :-) > I fear that systems are currently optimized by default for throughput. For > users, responsiveness (which can include but is not limited to throughput) > and latency may be more important psychologically Can I just say yes here, you go into lengths explaining (thanks) but I already agreed here :-) Yet - as true as that is - it is true for a set of workloads and hardware, but not for all that Ubuntu can be (as I outlined above neither decision could be true for all) > And power saving is important in global terms, as even small gains > multiplied over hundreds or thousands of deployments can have a > significant impact True as well, yet - again - most servers are often split by some virt solution to pay off by their price running at high utilization. There to reach density often people are ok to forfeit some latency for overall throughput and thereby density which saves power by having x% less systems active at all. P.S. I'm now waiting for further input by all of you that found the thread so far as well as hopefully some of all the teams, hardware manufacturers and clouds that I have connected to please think about this question. P.P.S. I'm drifting away of seeing a big deja-vu into my decade of Linux on mainframe performance - and density and performance and interfering workloads that invalidated all you knew when looking at just one ... and you know what the answer always was and still is: "it depends" as any performance engineer will love to tell you :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in Ubuntu on IBM z Systems: New Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Pings done, in a perfect world (if all reply) that would cover more than we ever need, but then there is 0% guarantee they even have time or care about this at the moment :-) If anyone has connections as well, please ask them to participate too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Dough > If irqbalance is to be included by default, then there should be due > diligence to demonstrate a clear benefit. You are right that we should have that as well. But this would be even more ture if this would be about "making it the default when it was not before". Right now (purely opinion) the lack of data can IMHO neither be used to keep it nor to remove it - which sadly locks this up a bit. > The results were: I want to thank you a lot, this won't be enough but it is a masterpiece demonstration of dedicating time to start providing such data. Thank you. I do not know the ping pong test, but on iperf, I think that is in the noise range as far as I remember. If you'd just re-run that as-is what is the delta on your test box? Hoping that this will be extended by more contributing different workloads on different systems let me ask, what kind of system (cpu, size, nodes, ...) was that. I know you are good at writing up things, you might set the standard how others might report to this :-) Your results show no change or minimal degradation while at the same time losing a bit of power. Have you also had a chance to try the powerthresh argument that Steve mentioned above? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
I want to try to avoid that this becomes too stale, so I wondered what we can do from here. Two things came to my mind. On one hand I will try to use some indirect relations to pull in some HW manufacturer experts. They often have large performance teams tracking things like that against different workloads. And on the other hand, due to the request seemingly to close in on "please consider not making it the default on desktop" (server is more likely to have these large scaling workloads that are more likely to benefit) we need to pull in someone from Desktop a bit more. I'll do a few direct pings for that as well to ensure to get their voice too. Doing so now ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Paride > Back in the day I asked upstream their take on irqbalance usefulness with > newer kernels, here is their reply: > https://github.com/Irqbalance/irqbalance/issues/151 Thanks for this and the other extra pointers. The Debian bug was referenced before, AFAIC it is mostly around a) the kernel got smarter in many cases (true) b) bad in virtual environments (we already removed it from those) And in that discussion the upstream comments (it is good to see that they are still convinced of their code) revolved around: c) There should be no conflict with running irqbalance (with the new kernel) d) The kernel policy is driver centric (irqbalance has a full picture) Both - as I read them - are more arguments to keep it than to remove. But as all other, not with enough data to make it a clear yes/no. As I said much earlier in this case, I feel this is system and workload dependent and hence there will never be a clear generic yes/no. The best we can achieve is finding sets (like images used in virtual environments - or as suggested desktop systems) and drop it being the default there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Mike > SUSE ... says that the first step to get there is to disable irqbalance I've read the same, IMHO that is just "if you want to manually tune, disable it" which does not imply that it is bad to have it. But this is how I read it, I have not talked to the authors to get their underlaying reasoning. > Applications vendors ... currently recommend removing irqbalance The only one that does so AFAICS is cpufreq and everyone else just links to their reasoning and follows. And even some statements there like "If you are still running irqbalance, you are not getting the maximum performance your system is capable of!" are hard to believe as a general statement - especially without data across a wide variety of system types and workload. As we have seen as well in the references linked, irqbalance helps just as much for "maximum performance" in many other cases. > I found this blog (https://blogs.oracle.com/linux/post/irqbalance- design-and-internals) Thanks, every extra background we find will only help (except for those joining later to read more). > The question I have is, if Ubuntu is Debian Branch, and we long ago went > from having different kernels for desktop & server in ubuntu-base, but do > have ubuntu-server packages and ubuntu-desktop packages, where things could > be different, why is this still a broad sweep as a default install "for all"? Because there was no well-funded conclusion like "it really is bad for environment X" to remove it. You are right that there are no technical blockers to make it e.g. kept in servers but no more the default in Desktop. After all it is already dropped in cloud-images used in virtual environemnts as it had a more clear reasoning and argument there. And there are also cases where irqbalance missing caused performance impact and bug reports like the already mentioned [1] (clearly high scale server though) > I am happy that this is getting discussed properly now so that we can > relook at this, and what it means to us today. Ack, that is why I tried to compile all I've found into one place. [1]: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2038573 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Ethanay > All I can find is a recommendation not to use it on CPUs with 2 or fewer > cores as the overhead is said to be too high This isn't a real problem anyway, the service will stop immediately if only running on one core - even if running on multiple cores with the same cache (as the intended benefit is due to cache hotness by having all I/O hitting the same cache). > I can imagine it might still add undesirable or even critical latency in > applications that are highly latency sensitive I understand your line of thought, but it might even improve latency. If there is no bottleneck on the cores assigned to handle an IRQ then the improved cache hit rate will make even latency better. And if there is a strong bottleneck, then some drivers without IRQbalance would end up locked on one cpu - so again these might gain lower latency. But I have no data on this either (just like no one seems to have on almost any of this). Just like others I'd personally more expect the drawback to be on a potential lack of power saving. > This website gave me some clarity on the theory and purpose: > https://www.baeldung.com/linux/irqbalance-modern-hardware Hah, didn't find this one yet - thank you! But to me it only underlines the "it can help as much or even more often" expectation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Steve, > I see a lot of strong opinions ... I would want any decision to remove > irqbalance from the desktop to be based on evidence, not conjecture. I agree that there is plenty of opinion (often backing up each other with cyclic links) and not much data. Hence my compilation of the history to make it somehwat consumable. I wasn't entirely sure on my own but I agree that we'd need data to back up changes, thanks for empowering that branch of the decision tree. Yet on the other hand, that most likely means not much will move quickly. Which is fine, but also makes it unlikely to conclude before Noble freezes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963707] Re: [MIR] libqrtr-glib
Libqmi (which is what pulls in libqrtr-glib) is ready except for this component mismatch. While qmi is in proposed adding the depend libqrtr is only in noble- release atm libqrtr-glib | 1.2.2-1ubuntu2 | noble/universe | source libqmi | 1.32.4-2ubuntu1 | noble| source libqmi | 1.34.0-2 | noble-proposed | source Even the -dev and -doc packages are free of further conflicting dependencies and have been approved above, hence promoting it all. Override component to main libqrtr-glib 1.2.2-1ubuntu2 in noble: universe/misc -> main gir1.2-qrtr-1.0 1.2.2-1ubuntu2 in noble amd64: universe/introspection/optional/100% -> main gir1.2-qrtr-1.0 1.2.2-1ubuntu2 in noble arm64: universe/introspection/optional/100% -> main gir1.2-qrtr-1.0 1.2.2-1ubuntu2 in noble armhf: universe/introspection/optional/100% -> main gir1.2-qrtr-1.0 1.2.2-1ubuntu2 in noble i386: universe/introspection/optional/100% -> main gir1.2-qrtr-1.0 1.2.2-1ubuntu2 in noble ppc64el: universe/introspection/optional/100% -> main gir1.2-qrtr-1.0 1.2.2-1ubuntu2 in noble riscv64: universe/introspection/optional/100% -> main gir1.2-qrtr-1.0 1.2.2-1ubuntu2 in noble s390x: universe/introspection/optional/100% -> main libqrtr-glib-dev 1.2.2-1ubuntu2 in noble amd64: universe/libdevel/optional/100% -> main libqrtr-glib-dev 1.2.2-1ubuntu2 in noble arm64: universe/libdevel/optional/100% -> main libqrtr-glib-dev 1.2.2-1ubuntu2 in noble armhf: universe/libdevel/optional/100% -> main libqrtr-glib-dev 1.2.2-1ubuntu2 in noble i386: universe/libdevel/optional/100% -> main libqrtr-glib-dev 1.2.2-1ubuntu2 in noble ppc64el: universe/libdevel/optional/100% -> main libqrtr-glib-dev 1.2.2-1ubuntu2 in noble riscv64: universe/libdevel/optional/100% -> main libqrtr-glib-dev 1.2.2-1ubuntu2 in noble s390x: universe/libdevel/optional/100% -> main libqrtr-glib-doc 1.2.2-1ubuntu2 in noble amd64: universe/doc/optional/100% -> main libqrtr-glib-doc 1.2.2-1ubuntu2 in noble arm64: universe/doc/optional/100% -> main libqrtr-glib-doc 1.2.2-1ubuntu2 in noble armhf: universe/doc/optional/100% -> main libqrtr-glib-doc 1.2.2-1ubuntu2 in noble i386: universe/doc/optional/100% -> main libqrtr-glib-doc 1.2.2-1ubuntu2 in noble ppc64el: universe/doc/optional/100% -> main libqrtr-glib-doc 1.2.2-1ubuntu2 in noble riscv64: universe/doc/optional/100% -> main libqrtr-glib-doc 1.2.2-1ubuntu2 in noble s390x: universe/doc/optional/100% -> main libqrtr-glib0 1.2.2-1ubuntu2 in noble amd64: universe/libs/optional/100% -> main libqrtr-glib0 1.2.2-1ubuntu2 in noble arm64: universe/libs/optional/100% -> main libqrtr-glib0 1.2.2-1ubuntu2 in noble armhf: universe/libs/optional/100% -> main libqrtr-glib0 1.2.2-1ubuntu2 in noble i386: universe/libs/optional/100% -> main libqrtr-glib0 1.2.2-1ubuntu2 in noble ppc64el: universe/libs/optional/100% -> main libqrtr-glib0 1.2.2-1ubuntu2 in noble riscv64: universe/libs/optional/100% -> main libqrtr-glib0 1.2.2-1ubuntu2 in noble s390x: universe/libs/optional/100% -> main Override [y|N]? y 29 publications overridden. ** Changed in: libqrtr-glib (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqrtr-glib in Ubuntu. https://bugs.launchpad.net/bugs/1963707 Title: [MIR] libqrtr-glib Status in libqrtr-glib package in Ubuntu: Fix Released Bug description: [Availability] The package libqrtr-glib is already in Ubuntu universe. The package libqrtr-glib build for the architectures it is designed to work on. It currently builds and works for architetcures: amd64 armhf arm64 ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/libqrtr-glib [Rationale] - The package libqrtr-glib is required in Ubuntu main for modemmanager to support qualcomm modems. We current carry a delta over Debian to disable that option - The package libqrtr-glib will be useful only to users owning such hardware but even if that's a limited set of users it's important for us to have Ubuntu supporting the available hardware. - It would be great and useful to community/processes to have the package libqrtr-glib in Ubuntu main, but there is no definitive deadline. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu and has no bug open currently - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libqrtr-glib/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libqrtr-glib [Quality assurance - testing] - The package runs a minimal test suite on build time, if it
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
After all the history I was looking at where we are right now: - irqbalance already is not in ubuntu-cloud-minimal images - irqbalance is in normal cloud images and installed systems via the dep from ubuntu-server -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
I subscribed a few people directly to get their input. @Steve I've subscribed you after trying to find, refer and summarize all of the past to allow you and anyone else to read into this in one go. I think I'll need your input as Architect and as participant of these discussions right from when they started 14 years ago. @Phil/@John Some past discussions, especially the backpedaling of Debian referred to virtual environments and/or large cloud providers. Is irqbalance anything you got asked to disable (or keep) for their environment? No need to share names, but reasoning or data points would be helpful :-) @Dimitri Is there a more clear "this is what userspace should do in regard to this in 2024" form the kernel? I couldn#t find it, but maybe you know or know who'd know ... @Sebastien Since most problems reported have been around Desktops (to be fair, that could be an coincidence because that is where people do more experiments and have more diverse special cases). But I think it is fair to ask you if requests or discussion like the above have come up towards Desktop that are worth to refer here? Maybe one of you has more details that help to make the decision more clear and easy. Or a gut feeling that is even stronger than mine, strong enough even to pick one of the options? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
# Summary This discussion was seeminly easier to make the more dedicated to a singluar use case you are - as then you have less "but what if" cases to consider. That wide usage is great for Ubuntu but sometimes delays decisions. List of reasons to remove it from the default dependencies: - Seems to cause issues more often on Desktop environments - cpufreq, thermald and similar struggle to save energy - Impacts due to unepexcted throttling - Conflicts with enabling/disabling threads/cores - Problematic in virtual environments - It is mostly an x86 thing but we pull it in everywhere - It conflicts with manually fine tuned IRQ affinity e.g. in ultra low latency setups - It is less useful on cpus with large and wide shared caches as well as in virtual environments without fix pinning List of reasons to keep it in the set of default dependencies: - Benefits seem mostly for large scale servers - lacking irqbalance can be a performance degradation in some large scale high traffic cases I think from all I've found - old and new - it seems it still has its purpose in some scenarios, but the HW/SW world evolved and it is nowadays less often useful and more often harmful than it was in the past. On the other hand there is almost no clear cut "it is bad and that is why", most issues were individual issues and special cases, nothing that would apply to everyone. And irqbalance still has is purpose, so we should surely keep it around. In a perfect worlds this would have half a year of time or more and two people to run all kinds of workloads on all kinds of HW to compare. But let us be honest that will not happen and that would then also be not be worth the effort. We'll have to decide with what we have. Have the others that switched have more time to evaluate in depth, I do not know. But usually once a significant amount of the ecosystems changed and you lack better data it is better to also follow or common hints and optimizations will no more apply due to being the one outlier in regard to behavior. To me this seems to be a perfect case for a few special images/deployments known to match the workload profile that needs this to enable it. It is also more likely that a professional admin of such a large scale machine (or cluster thereof) can make the opt-in decision and evaluation better than expectint every user of Ubuntu to think about an opt-out. --- Options IMHO: A) Change it from an opt-out to an opt-in and remove the dependency from ubuntu-standard B) Remove it from ubuntu-standard to get rid of it in Desktops and images used in virtual environments. But try to keep it in a place that is mostly used for bare metal which tend to be closer to the kind that benefits more C) Do nothing, keep it as is D) Any of the above, but let us not touch Noble more than half way through the cycle, but do that early in 24.10 to have enough exposure before a release in an LTS. My gut feeling (and it can't be much more without much more time for much deeper investigations) would be (A). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
# Actions by Others Times have changes, as mentioned above the kernel learned many new tricks. More new I/O hardware virtual or physical appeared that tries to be smart and thereby sometimes conflict with what irqbalance does. Some are mostly based on the links referred above, the Debian disucssion was more about it being harmful (or at least not helpful) in virtual environments and hence removed from cloud images (we close in on workload specific again). Indeed many projects already removed it from the default - https://github.com/pop-os/iso/pull/288 - https://github.com/ValveSoftware/Proton/issues/3243 - https://lists.debian.org/debian-cloud/2019/04/msg00040.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
# Integration and maintenance Despite some saying it is for the past only, it is regularly updated and has multiple releases per year throughout all the time [4]. Those updates flow well into Debian and Ubuntu - so it is not a classic "old and outdated" case. And while not much changes in those updates, it means it still learns like about thermal events in 1.9.1 or about isolcpus in 1.0.9. I'm not saying it is super modern doing it all, but it gets updates. Currently this is seeded in ubuntu-standard [1], which is what makes it default installed everywhere. But it is intentionally only a recommends, so the set of people that want to remove it can do so. It was added a long time ago [3] back when multi-core was a rare thing at least for Desktop systems. This was based on a discussion [5] and was related to the kernel [6] actively delegating this to userspace. Debian did a similar change a bit later [17] for the same reasons. But again this was the time of single-core being common. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/tree/standard?h=noble#n19 [3]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/commit/?h=noble=dcd02266953547e11221979eb17eb740a76a62b5 [4]: https://github.com/Irqbalance/irqbalance/tags [5]: https://lists.ubuntu.com/archives/ubuntu-devel/2010-January/029939.html [6]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b8e8c1bf7275eca859fe551dfa484134eaf013b [17]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577788 ** Bug watch added: github.com/ValveSoftware/Proton/issues #3243 https://github.com/ValveSoftware/Proton/issues/3243 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
# Referred Arguments An argument that might not have been so strong more than a decade ago but is much more today is power savings and that is an aspect that comes up over and over. It also had reports of conflicts with power saving [10] and e.g. dynamically disabling/enabling cores which is much more a thing nowadays as long ago this was only reliably working on mainframes anyway. I don't buy the "games need 100%" as even games need their I/O to happen, but OTOH irqbalance just doesn't help much nowadays either as the kernel learned many more tricks to do well - like to name just one all the traffic aware and potentially offloaded rps/xps [2]. And irqbalance is not mutually exclusive with most of those technologies not with RSS [18] nor with kernel policies [15]. Some report about conflicting with their custom tweaking of IRQs [8][16]. It is actually a common conflict between irqbalance being smart [9] and other things like a particular device firmware being smart leading to a conflict of interest. => But TBH that is why it is removable for such rare cases. On one hand it clearly has some impact and various cases of bad impacts by it have come up as well for frame rates [11], stuttering [14] or even network traffic [12]. But on the other hand, there have been reports and cases where a broken irqbalance led to impacted high-performance network traffic [7], so it is not that it is clearly always bad [13]. While we never know how outdated any such source might be, it proves that it is most likely workload and system dependent. Many documentations also sitll refer to it only older RH, Arch [19], ... you'll find it everywhere. It is an interesting case, and the workload dependency leads many discussions to even be contradicting - in one case it saves cpu power in the other it makes it worse. In one it helps traffic in the other is degrades it. That is all a consqeuence of it being workload and system dependent. This back and forther is perfectly encapsulated in this phornix thread [15]. Which quotes interesting other POVs like kernel solutions often being "driver centric" optimizing throughput, but maybe not always the best as policy for the full system as irqbalance pilicies and tunables are configurable. An interim summary might be: """ It could cause rare issues or conflicts, especially on Desktop, but might be still wanted on Servers especially those with a high rate of I/O """ Which is interestingly quite close to the arguments floating around when it was added more than a decade ago (see further below). [2]: https://www.kernel.org/doc/html/latest/networking/scaling.html [7]: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2038573 [8]: https://groups.google.com/g/gce-discussion/c/Ns8hgOUW9GY [9]: https://docs.xilinx.com/r/en-US/ug1523-x3522-user/Interrupt-Affinity [10]: https://konkor.github.io/cpufreq/faq/#irqbalance-detected [11]: https://askubuntu.com/questions/1067866/ubuntu-18-04-steam-games-frame-rate-drop [12]: https://serverfault.com/questions/410928/irqbalance-on-linux-and-dropped-packets [13]: https://bookofzeus.com/harden-ubuntu/server-setup/disable-irqbalance/ [14]: https://www.reddit.com/r/linux_gaming/comments/emnu3k/removing_irqbalance_fixed_major_stuttering_in/ [15]: https://www.phoronix.com/forums/forum/hardware/processors-memory/1335986-amd-zen-1-linux-performance-hit-from-retbleed-accumulated-cpu-mitigation-impact/page4 [16]: https://documentation.suse.com/sbp/server-linux/pdf/SBP-performance-tuning_en.pdf [18]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/performance_tuning_guide/network-rss [19]: https://wiki.archlinux.org/title/Improving_performance#irqbalance ** Bug watch added: Debian Bug tracker #577788 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577788 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi, this was overlooked for too long but came up in bug 2046470 again which made me see this for the first time. I'd wish we'd have had that even a bit earlier e.g. to release it with mantic and not half way through noble, but still now is the time to still change the next LTS. I needed to make up my mind on this to come to a conclusion and so I wrote a summary mostly for myself, but also for others that I want to ack to the decision as well as for anyone to later be able to understand what changed and why. I must admit that I'm slightly biased, having looked at it ages ago, even before I was more active in Ubuntu development and already wondering if that should be used by default. And yes, some people had a stronger wish to get it out of the default. So as already reported, many have already asked to remove it. I'll try to break up my answers to be more easily referable. ** Also affects: irqbalance (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
The seeding [1] of it is also quite clear on why it is still there. """ # This stack is no more very relevant, but was in the early days of internet # dialin. This stack is a candidate for demotion, but OTOH received no # bugs/CVEs over the last years and therefore can stay as-is for now. # ppp itself is still recommended by network-manager and thereby has quite # an install base. """ Removing is maybe too hard as Steve outlined, but what about at least demoting to universe (to encourage it a bit less)? The seed change to the section linked above would be trivial, but it would need coordination with the Desktop variants as a dependency to network-manager-pptp is in most of the meta packages. reverse-depends --release=noble src:network-manager-pptp Reverse-Recommends == * network-manager (for network-manager-pptp) * ubuntu-budgie-desktop [amd64 arm64 armhf ppc64el] * ubuntu-budgie-desktop-minimal [amd64 arm64 armhf ppc64el] * ubuntu-budgie-desktop-raspi [arm64 armhf] * ubuntu-desktop [amd64 arm64 armhf ppc64el] * ubuntu-desktop-minimal [amd64 arm64 armhf ppc64el] * ubuntu-mate-core (for network-manager-pptp-gnome) * ubuntu-mate-desktop (for network-manager-pptp-gnome) * ubuntu-unity-desktop [amd64 arm64 armhf ppc64el] * ubuntukylin-desktop (for network-manager-pptp-gnome) * vanilla-gnome-desktop [amd64 arm64 armhf ppc64el] * xubuntu-desktop (for network-manager-pptp-gnome) * xubuntu-desktop (for network-manager-pptp) Reverse-Depends === * lomiri-indicator-network (for network-manager-pptp) It comes at a comfort loss though, since this is depended on by all those meta packages to work right away in a fresh install, which would be a behavior that will be lost. Also if there is a CVE, then only people using ubuntu pro would get a fix. Which is free for personal use, but those forced to use pptp are likely people with non-personal use of outdated infrastructure. So we'd make the world a bit less secure as likely not all would get the fixes then. Still I'd want to know from Steve and Seth which discussed so far - what would you think about that as a compromise? [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/supported-misc-servers#n190 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Incomplete Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. IPSec OpenVPN Strongswan are much better alternatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037011] Re: Can't create ovpn
I can confirm the same, neither importing nor adding a VPN via the gui works. You clock "add" after importing or configuring one, click add and then ... as if nothing had happened. I ran `gnome-control-center` directly and followed journal, no related error message shows up. It is not just visualization, `nmcli con` does also not list the connection that now should be known. It seems to be a UI only issue, as I can import a connection via: $ nmcli connection import type openvpn file myfile.conf Same for using the connection afterwars. Clicking the UI enable toggle seems to do nothing. But via cli it works: $ nmcli connection up myconection $ ip route ... shows pushed routes ... Not that it would work, even connected I still can't reach anything. But it at least connects I guess? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/2037011 Title: Can't create ovpn Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-openvpn package in Fedora: New Bug description: Settings -> Network -> Add VPN -> Import from file to import an .ovpn file does nothing after clicking Add, it just returns to the Add VPN page and no VPN connection is added. The same .ovpn file works fine in 22.04. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager-openvpn 1.10.2-3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 22:12:58 2023 InstallationDate: Installed on 2023-09-18 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/2037011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
FYI Undocked with just the laptop screen it does not trigger the issue. But docking the running system to initialize all additional screens makes it trigger up again once I leave into the activities screen (as described before). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2000644 Title: switching workspaces with shortcut sometimes freezes screen Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: The bottom panel with dots to show which workspace you are on when switching with ctrl+alt+arrow sometimes doesn't disappear and gets stuck in a half faded or not faded state. In that state the mouse appear stuck and the screen freezes until the super key is pressed to show overview or the workspace is switched again. Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand, Nvidia driver 525.60.11 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
FYI: Since the signature of bug 2035016 is quite similar I checked, but I already have the mutter components on 45.0-2ubuntu1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2000644 Title: switching workspaces with shortcut sometimes freezes screen Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: The bottom panel with dots to show which workspace you are on when switching with ctrl+alt+arrow sometimes doesn't disappear and gets stuck in a half faded or not faded state. In that state the mouse appear stuck and the screen freezes until the super key is pressed to show overview or the workspace is switched again. Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand, Nvidia driver 525.60.11 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
Considering it impossible to work with a system hanging every few hours I debugged this over the weekend a few times, but sadly to no further insight. Eventually I've given up and re-deployed Mantic on the system trying to either "help by verifying the issue still exists" or "getting out of it". I can confirm that, at least on my system, the issue is still reproducible right after new installation of Mantic. The workaround of a fix number of workspaces still does not work for me. Setups showing this: - Laptop + 2 external monitors, intel gpu - Laptop + 2 external monitors + 2 via displaylink, intel gpu I intend to undock, reboot and test if it also shows on this machine without external monitors - didn't find the time yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2000644 Title: switching workspaces with shortcut sometimes freezes screen Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: The bottom panel with dots to show which workspace you are on when switching with ctrl+alt+arrow sometimes doesn't disappear and gets stuck in a half faded or not faded state. In that state the mouse appear stuck and the screen freezes until the super key is pressed to show overview or the workspace is switched again. Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand, Nvidia driver 525.60.11 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
I see the same on Jammy, like the others it is reproducible easily by hitting the meta key and exiting from there in any way (hit ESC, select anything to start, ...). Sadly setting fixed workspaces (10) did not work around the issues for me, like it did for others. Occasionally (seems to depend if this issue races with something else as it seems more likely if the system has more apps running and me doing more things) I also get the stuck-desktop experience out of that. Usually starting with the mouse not being able to click everything anymore and a while after with a totally stuck desktop (not even ctrl-alt-f# gets me out anymore). That "stuckness" if it is still phase-I (mouse can't clock it all) sometimes resolves itself after a few minutes - no log entries in journal when that un-stucking happens. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2000644 Title: switching workspaces with shortcut sometimes freezes screen Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: The bottom panel with dots to show which workspace you are on when switching with ctrl+alt+arrow sometimes doesn't disappear and gets stuck in a half faded or not faded state. In that state the mouse appear stuck and the screen freezes until the super key is pressed to show overview or the workspace is switched again. Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand, Nvidia driver 525.60.11 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
If it would be an MP I'd set it to needs-information, but this is a debdiff in a bug. I hope my questions and confusion was clear so that you can iterate and clarify. I'll remove ubuntu-sponsors which I'll ask you to add back once this is ready for review again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Confirmed Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Confirmed Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Then the most recent applied patch says: ... Since this is a helper service that is meant to be controlled by "tracker-miner-fs", the install section shouldn't exist, as it allows the service to enabled, meaning that its execution would be controlled by systemd. But I can't see where/how: root@m:~# grep -Hn -- tracker-extract $(dpkg -L tracker-miner-fs| xargs) 2>/dev/null | grep -v copyright Would you mind clarifying that interaction on your update. Because without I'm afraid more will be confused :-/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Confirmed Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Confirmed Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
This is now the third revision of the change (3.4.3-1ubuntu1 + 3.4.3-1ubuntu2 + this) and by identifying that this also needs to go to -devel I wonder if you should not also use the chance to submit the outstanding Delta to Debian. That will help them directly and mid-term ease maintenance. 3.4.3-1ubuntu2 said "Cherry-pick patch ..." but didn't mention from where - will this be in next upstream and that way come to Debian? If so, you might still help by reminding them to use the purge mechanism to get rid of the old on-disk config. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Confirmed Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Confirmed Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
I can see why you do the purge forgetting the old state to enable them as if they were freshly installed. I'm not sure how SRUable that will be afterwards as it is affecting behavior if someone has set something else than the default. But for now, going forward to mantic I agree that it will help to get an upgrading system out of the old wrong dependencies. Given that this isn't meant to be enabled automatically (thanks for the explanation in the last patch) that should be ok'ish. You do this change even to people which installed 3.4.3-1ubuntu2 as the first (which was correct). But I think adding more code to detect that rare case won't help many real cases. Since this is juts for mantic for now, that is fine. But double think about it on SRU time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Confirmed Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Confirmed Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Some things just do not fit together. You write "... to update from default.target.wants to gnome-session.target.wants. ..." But while 3.4.3-1ubuntu1 does: + [Install] +-WantedBy=default.target ++WantedBy=gnome-session.target Then later 3.4.3-1ubuntu2 does +-[Install] +-WantedBy=default.target ++# This is a helper service that is controlled by "tracker-miner-fs-3.service". ++# It's not supposed to be enabled or started manually. So the changelog and intent doesn't match. Is it just the changelog that got confused or is there more that needs to be clarified and corrected? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Confirmed Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Confirmed Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to
[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
This in your changelog is a Debian keyword Closes: #2014954 To work on launchpad that needs to be LP: #2014954 I hope that helps and gives you a few minor things to fix. I feel too much out of my comfort zone to fully sponsor this anyway :-/ But I wondered about one more thing to ask you, given that you say this is "the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors" wouldn't you think it might be better to wait until upstream https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/tags tags 1.30 - then at least we'd have the testing of the developers there and all the code they tested it with. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: New Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Intel WWAN cards, and Lenovo are struggling to give a decent way to run the FCC unlock service without this. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Thanks for the clarification Matthew and Heitor - first I'll re-set the state of the devel release then. As it isn't completely fixed there. ** Changed in: tracker-miners (Ubuntu) Status: Fix Released => Confirmed ** Changed in: tracker-miners (Ubuntu Lunar) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Confirmed Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Confirmed Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service
[Desktop-packages] [Bug 1812456] Re: [MIR] libflatpak0
There has been not further update for too long, for now we consider it invalid. Feel free to re-open if there is effort backing it up and motivation to bring it to main. ** Changed in: flatpak (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1812456 Title: [MIR] libflatpak0 Status in flatpak package in Ubuntu: Invalid Bug description: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak0 in main so we can easily build such applications. It takes a lot of work to make these dependencies optional and sometimes that is not possible. We don't need the Flatpak functionality to work by default and do not expect any other Flatpak packages to be installed by default. Default packages that have flatpak integration: - gnome-control-center (application panel). - malcontent (parental controls) Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Multiple default packages have libflatpak as a dependency, including malcontent (LP: #1892456). Security This will need a Security review. https://security-tracker.debian.org/tracker/source-package/flatpak There have been two CVEs, both have been fixed in all supported Ubuntu releases. More recently, there is LP: #1815528 Quality Assurance = Bug subscriber: should be Ubuntu Desktop Bugs https://bugs.launchpad.net/ubuntu/+source/flatpak https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=flatpak https://github.com/flatpak/flatpak/issues tests are run as build tests (with dh_auto_test) and installed autopkgtests on Debian and Ubuntu. https://ci.debian.net/packages/f/flatpak http://autopkgtest.ubuntu.com/packages/f/flatpak UI Standards N/A Dependencies All in main except for libostree-1-1 (LP: #1892454) Standards Compliance Package uses standards version 4.5.0. Maintenance === - Actively developed upstream https://github.com/flatpak/flatpak - Maintained in Debian by the pkg-utopia team but more specifically, it is maintained by Simon McVittie (smcv) who maintains Flatpak, ostree, xdg-dbus-proxy, xdg-desktop-portal and xdg-desktop-portal-gtk. short dh7 style rules, dh compat 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1812456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite
There has been not further update for too long, for now we consider it invalid. Feel free to re-open if there is effort backing it up and motivation to bring it to main. ** Changed in: opensc (Ubuntu) Status: Incomplete => Invalid ** Changed in: pcsc-lite (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Invalid Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: Invalid Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and
[Desktop-packages] [Bug 1963707] Re: [MIR] libqrtr-glib
There has been not further update for too long, for now we consider it invalid. Feel free to re-open if there is effort backing it up and motivation to bring it to main. ** Changed in: libqrtr-glib (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqrtr-glib in Ubuntu. https://bugs.launchpad.net/bugs/1963707 Title: [MIR] libqrtr-glib Status in libqrtr-glib package in Ubuntu: Invalid Bug description: [Availability] The package libqrtr-glib is already in Ubuntu universe. The package libqrtr-glib build for the architectures it is designed to work on. It currently builds and works for architetcures: amd64 armhf arm64 ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/libqrtr-glib [Rationale] - The package libqrtr-glib is required in Ubuntu main for modemmanager to support qualcomm modems. We current carry a delta over Debian to disable that option - The package libqrtr-glib will be useful only to users owning such hardware but even if that's a limited set of users it's important for us to have Ubuntu supporting the available hardware. - It would be great and useful to community/processes to have the package libqrtr-glib in Ubuntu main, but there is no definitive deadline. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu and has no bug open currently - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libqrtr-glib/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libqrtr-glib [Quality assurance - testing] - The package runs a minimal test suite on build time, if it fails it makes the build fail, link to build log https://launchpadlibrarian.net/587268179/buildlog_ubuntu-jammy-amd64.libqrtr-glib_1.2.2-1_BUILDING.txt.gz - There is a basic build autopkgtest for the library https://autopkgtest.ubuntu.com/packages/libq/libqrtr-glib - testplan On a computer with a QRTR modem in an Ubuntu session, open the settings, check that the modem panel correctly describes the device and available SIM. Try to connect to a carrier and use the data connection. Our Desktop and oem teams don't have access to compatible hardware at the moment to go through the testplan. The Certification Team owns some IoT hardware with qualcomm modems though and we are working with them to see if those could be used to do our testing but the setup is somewhat challenging (available only via testflinger, the device are using UC20 and ubuntu server on focal and we can't revert the state remotely if needed. Also SIM card availability is limited). As a result we currently are not able to commit to be able to validate the testplan on updates, but we are working on trying to resolve the situation. [Quality assurance - packaging] - debian/watch is present and works - This package only has a minor lintian warning - Link to recent build log including a lintian run # lintian --pedantic running with root privileges is not recommended! W: libqrtr-glib source: superfluous-file-pattern debian/copyright docs/reference/meson.build (Files, line 28) - Lintian overrides are present, but only to silent warnings about gtk-doc being outside of /usr/share/doc - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions - Packaging and build is easy, link to d/rules https://salsa.debian.org/DebianOnMobile-team/libqrtr- glib/-/blob/debian/master/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be desktop-packages - Team is not yet, but will subscribe to the package before promotion - This does not use static builds - This does not use vendored code [Background information] The Package description explains the package well Upstream Name is libqrtr-glib Link to upstream project https://www.freedesktop.org/software/libqmi/libqrtr-glib/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqrtr-glib/+bug/1963707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in gtk+3.0 package in Ubuntu: New Status in qemu package in Ubuntu: Confirmed Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2000739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967593] Re: kernel modules going missing after reboot
** Changed in: cloud-initramfs-tools (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. 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) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. 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,
[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
** Changed in: cups-filters (Ubuntu) Assignee: (unassigned) => Didier Roche-Tolomelli (didrocks) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-filters package in Ubuntu: Incomplete Bug description: This is a simplified MIR for the splitting of the cups-filters source package. With the second generation (2.x) cups-filters upstream got split into 5 independent component repositories: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed See https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ braille-printer-app still needs some upstream work for getting released, the others were already released as 2.0b2. libcupsfilters, cups-filters, and cups-browsed contain mainly the code from the former cups-filters (1.x) which is already in Main. libppd contains code from CUPS (libcups and cups-ppdc) which is also in Main. As of https://github.com/canonical/ubuntu-mir -- If a new source package contains only code which is already in main (e.g. the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a MIR bug with an explanation (but without the full template) or updating/extending on the existing old MIR bug and re-opening it by setting it to "NEW" is sufficient. -- This report does not need the full template. The original packages (cups-filters and cups) are in Main already for more than a decade, so repetition of the original MIR would not be useful. cups was already in Ubuntu from the very beginning on and therefore probably in Main since the differentiation of Main and Universe got introduced. The binary packages are named as before (except SONAME of libraries being 2 instead of 1 now), binary packages for libppd added. So current dependencies and seeding should pull in everything (libppd is a library and cups-filters depends on it). libfontembed has been discontinued (folded into libcupsfilters, API removed) but no package uses it (except the components of cups-filters 1.x thenselves). braille-printer-app will be added to this report (or a new simplified MIR report created) as soon as it gets released upstream. Its binary package(s) will need to get seeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2003259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
** Description changed: + Window actions (like maximize) no more work in wayland for QEMU using + GTK backend once the guest UI is intialized. + + This can be seen by running an installed or even a trial Ubuntu from an + ISO like: + + $ qemu-system-x86_64 \ + -boot d \ + -cdrom ubuntu-22.04.1-desktop-amd64.iso \ + -m 4096M \ + -machine type=q35,accel=kvm \ + -cpu host \ + -smp 2 \ + -device qxl-vga + + The GTK UI of qemu has a feature called "fullscreen" which disables the + screen decorations and sets the window to maximize. The decorations go + away, but maximize doesn't work. + + + The following details were found so far: + - running with GDK_BACKEND=x11 works + - using sdl instead of gtk backend works + - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) + - host UI widgets (the square at the window top) do not work either + - hotkeys (super-up) do not work either + + It seems that once the guest has enabled the desktop something changes + and the maximize/minimize/... actions are no more processed. Not sure + were to debug next in regard to the gnome/wayland UI handling of this - + any idea? + + P.S. We can reproduce this in git builds of qemu, so we can debug of + modify the code as needed. The code for this is mostly in [1] + + [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c + + --- original report --- + Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ - -boot d \ - -cdrom ubuntu-22.04.1-desktop-amd64.iso \ - -m 4096M \ - -machine type=q35,accel=kvm \ - -cpu host \ - -smp 2 \ - -device qxl-vga + -boot d \ + -cdrom ubuntu-22.04.1-desktop-amd64.iso \ + -m 4096M \ + -machine type=q35,accel=kvm \ + -cpu host \ + -smp 2 \ + -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in qemu package in Ubuntu: Confirmed Status in wayland package in Ubuntu: New Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04
[Desktop-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite
** Changed in: pcsc-lite (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: Incomplete Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] Dependency of pcsc-tools; this library
[Desktop-packages] [Bug 1989359] Re: [UIFe] Kinetic wallpapers updates
@Seb FYI This [1] upload is in the NEW queue right now. But it refers to the old UIFe, not this one here - so I'm not accepting it right now in csae you want to fix this up. [1]: https://launchpadlibrarian.net/625301973/ubuntu- wallpapers_22.10.1-0ubuntu1_amd64.changes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1989359 Title: [UIFe] Kinetic wallpapers updates Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-wallpapers package in Ubuntu: In Progress Status in ubuntustudio-default-settings package in Ubuntu: Fix Committed Status in ubuntustudio-look package in Ubuntu: Fix Committed Bug description: The Canonical design team isn't going to have the new default wallpapers ready by UIF but target end of September so we are requesting an exception to upload those once they are available. The community wallpapers are also going to be available after UIF since the competition was not organized early enough https://discourse.ubuntu.com/t/kinetic-kudu-22-10-wallpaper-competition The results will be published on Sep 23th so we ask for permission to refresh our package with the new content by the next monday (26th) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1989359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624485] Re: Nettle: Enable AES-NI instructions on amd64.
Indeed (thanks Richard) that is enabled since 3.6-1. It is unlikely though due to the associated symbol changes (see e.g. the old changelogs) that this can be provided as an SRU for older releases. I'm not saying impossible, just unlikely as that evaluation has to be done and checked in depth for potential side-effects in regard to an SRU. ** Also affects: nettle (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nettle (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: nettle (Ubuntu) Status: Confirmed => Fix Released ** Changed in: nettle (Ubuntu Bionic) Status: New => Confirmed ** Changed in: nettle (Ubuntu Focal) Status: New => Confirmed ** Changed in: nettle (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: nettle (Ubuntu Focal) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1624485 Title: Nettle: Enable AES-NI instructions on amd64. Status in nettle package in Ubuntu: Fix Released Status in nettle source package in Bionic: Confirmed Status in nettle source package in Focal: Confirmed Bug description: The current build of libnettle6 does not have AES-NI enabled. There's two configure options for enabling it: --enable-x86-aesni: Use AES-NI instructions instead of the standard implementation. This will break on systems that don't have AES-NI. --enable-fat: Build a "fat" library that has the standard implementation and the AES-NI implementation. This allows the library to continue working on older systems while providing faster performance on systems that have AES-NI. Note that Nettle's AES-NI implementation as of v3.2 is only supported on amd64, not i386, so this would only affect the 64-bit package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1624485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964600] Re: [MIR] gnome-bluetooth3
Ok, it is there now: https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html gnome-bluetooth3: gir1.2-gnomebluetooth-3.0 gnome-bluetooth-3-common libgnome-bluetooth-3.0-13 libgnome-bluetooth-3.0-dev libgnome-bluetooth-doc libgnome-bluetooth-ui-3.0-13 libgnome-bluetooth-ui-3.0-dev [Reverse-Depends: Rescued from gnome-bluetooth3 (Uploader: jbicha), gir1.2-gnomebluetooth-3.0, gnome-shell (Uploader: 3v1n0) (MAIN), libgnome-bluetooth-3.0-13, libgnome-bluetooth-ui-3.0-dev] All Acks are present, no further dependencies, subscription present. Resolving this to get migrations done and have less noise left towards the release week. Override component to main gnome-bluetooth3 42.0-5 in jammy: universe/misc -> main gir1.2-gnomebluetooth-3.0 42.0-5 in jammy amd64: universe/introspection/optional/100% -> main gir1.2-gnomebluetooth-3.0 42.0-5 in jammy arm64: universe/introspection/optional/100% -> main gir1.2-gnomebluetooth-3.0 42.0-5 in jammy armhf: universe/introspection/optional/100% -> main gir1.2-gnomebluetooth-3.0 42.0-5 in jammy ppc64el: universe/introspection/optional/100% -> main gir1.2-gnomebluetooth-3.0 42.0-5 in jammy riscv64: universe/introspection/optional/100% -> main gir1.2-gnomebluetooth-3.0 42.0-5 in jammy s390x: universe/introspection/optional/100% -> main gnome-bluetooth-3-common 42.0-5 in jammy amd64: universe/gnome/optional/100% -> main gnome-bluetooth-3-common 42.0-5 in jammy arm64: universe/gnome/optional/100% -> main gnome-bluetooth-3-common 42.0-5 in jammy armhf: universe/gnome/optional/100% -> main gnome-bluetooth-3-common 42.0-5 in jammy i386: universe/gnome/optional/100% -> main gnome-bluetooth-3-common 42.0-5 in jammy ppc64el: universe/gnome/optional/100% -> main gnome-bluetooth-3-common 42.0-5 in jammy riscv64: universe/gnome/optional/100% -> main gnome-bluetooth-3-common 42.0-5 in jammy s390x: universe/gnome/optional/100% -> main libgnome-bluetooth-3.0-13 42.0-5 in jammy amd64: universe/libs/optional/100% -> main libgnome-bluetooth-3.0-13 42.0-5 in jammy arm64: universe/libs/optional/100% -> main libgnome-bluetooth-3.0-13 42.0-5 in jammy armhf: universe/libs/optional/100% -> main libgnome-bluetooth-3.0-13 42.0-5 in jammy ppc64el: universe/libs/optional/100% -> main libgnome-bluetooth-3.0-13 42.0-5 in jammy riscv64: universe/libs/optional/100% -> main libgnome-bluetooth-3.0-13 42.0-5 in jammy s390x: universe/libs/optional/100% -> main libgnome-bluetooth-3.0-dev 42.0-5 in jammy amd64: universe/libdevel/optional/100% -> main libgnome-bluetooth-3.0-dev 42.0-5 in jammy arm64: universe/libdevel/optional/100% -> main libgnome-bluetooth-3.0-dev 42.0-5 in jammy armhf: universe/libdevel/optional/100% -> main libgnome-bluetooth-3.0-dev 42.0-5 in jammy ppc64el: universe/libdevel/optional/100% -> main libgnome-bluetooth-3.0-dev 42.0-5 in jammy riscv64: universe/libdevel/optional/100% -> main libgnome-bluetooth-3.0-dev 42.0-5 in jammy s390x: universe/libdevel/optional/100% -> main libgnome-bluetooth-doc 42.0-5 in jammy amd64: universe/doc/optional/100% -> main libgnome-bluetooth-doc 42.0-5 in jammy arm64: universe/doc/optional/100% -> main libgnome-bluetooth-doc 42.0-5 in jammy armhf: universe/doc/optional/100% -> main libgnome-bluetooth-doc 42.0-5 in jammy i386: universe/doc/optional/100% -> main libgnome-bluetooth-doc 42.0-5 in jammy ppc64el: universe/doc/optional/100% -> main libgnome-bluetooth-doc 42.0-5 in jammy riscv64: universe/doc/optional/100% -> main libgnome-bluetooth-doc 42.0-5 in jammy s390x: universe/doc/optional/100% -> main libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy amd64: universe/libs/optional/100% -> main libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy arm64: universe/libs/optional/100% -> main libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy armhf: universe/libs/optional/100% -> main libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy ppc64el: universe/libs/optional/100% -> main libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy riscv64: universe/libs/optional/100% -> main libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy s390x: universe/libs/optional/100% -> main libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy amd64: universe/libdevel/optional/100% -> main libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy arm64: universe/libdevel/optional/100% -> main libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy armhf: universe/libdevel/optional/100% -> main libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy ppc64el: universe/libdevel/optional/100% -> main libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy riscv64: universe/libdevel/optional/100% -> main libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy s390x: universe/libdevel/optional/100% -> main Override [y|N]? y 45 publications overridden. ** Changed in: gnome-bluetooth3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth3 in Ubuntu. https://bugs.launchpad.net/bugs/1964600 Title: [MIR]
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I can't test this reliably (as stated in the SRU description), but at least I can say I haven't seen it in the last 24h :-) I think this is on @gjolly to try to reproduce it in the mentioned azure test environment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08
[Desktop-packages] [Bug 1712223] Re: open-vm-tools does not work under wayland
Thanks for the ping on this old case Alexander!
Can you confirm that this is what you see on 22.04 with the there recent
2:11.3.5-1ubuntu4 version of open-vm-tools?
I have subscribed John Wolfe who looks after open-vm-tools from VMwares
side and might have more details.
Further I added a bug task for "wayland" so that the Desktop team can
have a look as well.
** Also affects: wayland (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1712223
Title:
open-vm-tools does not work under wayland
Status in open-vm-tools package in Ubuntu:
Confirmed
Status in wayland package in Ubuntu:
New
Bug description:
At first I thought this bug was caused with the recent changes in
open-vm-tools 10.1.10; however, after restoring my VM to the snapshot
that had 17.04 and re-performing the dist-upgrade with open-vm-tools
and open-vm-tools-desktop held at 10.1.5 I am experiencing the same
issue where VMWare Workstation no longer can interact with display
resolution detection of the host monitor(s). Multiple monitor support
is also lost in the update process.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 21 17:09:59 2017
DistUpgraded: 2017-08-07 09:05:02,559 DEBUG found components:
{'artful-updates': {'multiverse', 'restricted', 'universe', 'main'}, 'artful':
{'multiverse', 'restricted', 'universe', 'main'}, 'artful-security':
{'multiverse', 'restricted', 'universe', 'main'}}
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 5.1.26, 4.10.0-30-generic, x86_64: installed
virtualbox, 5.1.26, 4.12.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2016-11-30 (264 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic
root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-08-07 (14 days ago)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Aug 21 16:27:55 2017
xserver.configfile: default
xserver.devices:
inputPower Button KEYBOARD, id 6
inputAT Translated Set 2 keyboard KEYBOARD, id 7
inputVirtualPS/2 VMware VMMouse MOUSE, id 8
inputVirtualPS/2 VMware VMMouse MOUSE, id 9
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: vmware
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5
Fixed in https://launchpad.net/ubuntu/+source/adsys/0.8ubuntu1 via the quick fix by Michael (thanks). AFAIU you wanted to keep the bug open for a better solution down the road? ** Tags removed: server-todo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: New Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
FYI the re-upload of a fuse3 open-vm-tools happened yesterday and it migrated to jammy-release. Any issues with the images? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: Fix Released Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
@aakef - while I said unionfs-fuse might not be a blocker I'd still recommend to upload the change switching to fuse3. On comment #12 it seemed you are close. Any chance to get this done or did unexpected blockers show up while trying? The unionfs-fuse task here is assigned to Graham; @ginggs - did you make any progress on that yourself or together with Bernd? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: Fix Released Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
FYI according to https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse3 This should no more be an issue now, so open-vm-tools will switch to fuse3 again in the next few days. This is a heads up in case it breaks again some way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: Fix Released Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936907] Re: [MIR] ADSys
It seems this is important for the 20.04.4 point release, so while we try to prioritize all the cases in the queue for security review let us set this to Critical + 20.04.4 Milestone. ** Changed in: adsys (Ubuntu) Importance: Undecided => Critical ** Changed in: adsys (Ubuntu) Milestone: None => ubuntu-20.04.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1936907 Title: [MIR] ADSys Status in adsys package in Ubuntu: New Bug description: [Availability] Available on all archs, available starting hirsute. It will be backported to Focal once an FFe has been accepted. [Rationale] We are supporting GPO Active Directory support on ubuntu starting hirsute. This features allows for an administrator to configure their Active Directory server to deploy per-machine and per-user configurations, enforce rules and other domain policies. Right now, dconf keys are supported. This feature is built and use the krb5 tickets which are provided by SSSD. Basically: - SSSD is dealing with user and machine registration/authentification and enforce password policies - ADSys is handling GPO enforcement and support. The Ubuntu specific policies needs to be installed on the Active Directory server (they are contained in the daemon). [Security] The daemon is started is running as a root user to be able to enforce machine policies, like rebuilding dconf databases, setting profiles. User only interacts with the client side (both sides communicates over GRPC), which can be ran as any user. Polkit is used to restrain access to some part of the API. There is a PAM module to build on demand per-user policy once authenticated with SSSD. They are rejected if the authentication or not all affected policies could be downloaded. [Quality assurance] Joining a domain in the ubiquity desktop installer makes the machine joining the AD domain and install adsys functionality. The package will be seeded directly on the desktop ISO. An extensive testsuite (more than 700) is included and available as autopkgtests for rdepends. The whole stack is tested (even the client/daemon interaction) and coverage is measured (including in the small python script). However, tests with a real Active Directory server can only be done manually as there is no setup available in the autopkgtests infrastructure. [Dependencies] Main dependencies are libsmbclient, python3 (an embeeded script allows, via samba, connecting to AD LDAP) and SSSD/KRB5. This is a Go package, and all dependencies are vendored, and versions are controlled via go.mod. We are using dependabot (from Github) to automatically get notified of any dependencies updates (and security issues), which opens a PR, rebuild and run all tests to report it there. We are thus able to quickly merge them. [Standards compliance] Standard debhelper packaging, including a systemd service. [Maintenance] The desktop team will maintain it. * we commit to test no-change-rebuilds triggered by a dependent library/compiler and to fix any issues found for the lifetime of the release (including ESM when included) * we will provide timely testing of no-change-rebuilds from the security team, fixing the rebuilt package as necessary * we commit to provide updates to the security team for any affected vendored code for the lifetime of the release (including ESM when included) * we will provide timely, high quality updates for the security team to sponsor to fix issues in the affected vendored code [Background information] ADSys is composed of: - a daemon, named adsysd, running as root. This one will shutdown after a period of inactivity without any active request. It is socket activated. - a client, named adsysctl (which is a symlink to adsysd and only differ behavior from its executable name), which is running as the user (or root on boot for machine update). This ones optionally wakes up adsysd, connect through an Unix socket with SO_PEERCRED to communicate current user running the process. We are using grpc to communicate between the client and service. Each client request is validated through polkit, matching user name and permissions. The daemon will reject any unauthorized client connections. Note that all actions are always performed from executing the client, even the scheduled one by a cron. The daemon contains a python embeeded script to reuse samba utilities to connect with GSSAPI to the AD LDAP server and list available GPOs. GPOs are then downloaded in a cache directory which isn’t accessible to users. The daemon also contains all GPOs policies to install on the Active Directory side to reflect them in the UI. This could be accessed online or dumped directly via the command line tool. Finally, those are automatically refreshed for
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
Hi Bernd, I'm glad to heard that as we were not sure it would work well with fuse3. As a reminder, the libs are co-installable it is "bin:fuse" vs "bin:fuse3" that are conflicting. So when you change that remember to also change fuse->fuse3. In the meantime it was found that unionfs-fuse isn't seeded (anymore) - it is only a comment in the Ubuntu seeds nowadays. So it will be great to move it to fuse3, but not resolve the issue discussed here. That must have been due to one of the other dependencies in the image. Anyone looking at this - please coordinate with ginggs, trevinho, paride on #ubuntu-devel for the timing of related Ubuntu uploads if they are seeded (or even in general). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Status in open-vm-tools package in Ubuntu: Incomplete Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
FYI - I uploaded a revert to the open-vm-tools change to un-block image builds for now. But maybe this was a good wake-up call. Please have a look at gvfs, union-fuse (here) and grub2, s390-tools, snapd, xdg-desktop-portal in bug 1934510. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Status in open-vm-tools package in Ubuntu: Incomplete Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
@Marco Trevisan - I subscribed you in case you want to steal the Desktop POV to this from Didier. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Status in open-vm-tools package in Ubuntu: Incomplete Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
Also see https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1934510/comments/24 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Status in open-vm-tools package in Ubuntu: Incomplete Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935668] Re: xdg-desktop-portal FTBFS when built with libfuse3-dev
Hi, some (qemu, open-vm-tools, fuse3 itself) started to land. We'd need to have this fixed and ready as well now. But do not do this in a rush, in bug 1956949 it was found that we need to coordinate this more precisely to move "all at once" to avoid conflicts between fuse <-> fuse3. Therefore the question, would this be ready for upload now? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1935668 Title: xdg-desktop-portal FTBFS when built with libfuse3-dev Status in xdg-desktop-portal package in Ubuntu: In Progress Bug description: Fuse3 is a requirement for qemu 6 (LP: #1934510). Since we don't want to support two versions of fuse in main, we'd like reverse- dependencies of fuse to switch to fuse3. xdg-desktop-portal FTBFS in a test rebuild changing the build- dependency on libfuse-dev to libfuse3-dev. Excerpt from the build log: checking for fuse... no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1935668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
#1 - Package: gvfs-fuse This build for Desktop already switched to the version3 as you see in "libfuse3-3 (>= 3.2.3)". But it still depends on the v2 user-tools. That mismatch needs to be resolved for 22.04 and it will need to switch to fuse3. I'm adding a src:gvfs task for that to switch to fuse3 (assigning to Didier, please reassign in *Desktop accordingly) #2 Package: unionfs-fuse This wasn't yet tried with fuse3 AFAIC as it was missed on the initial analysis for bug 1934510. I'll add a bug task for it here and ping bug 1934510 about it. We will have to move this to fuse3 as well, and the others of the formerly identified packages. I'll assign that to Ginggs as he has taken the initial archive wide check, maybe Foundations has this and more prepared to have all of them move at once. If it turns out that not all are ready yet, then we need to tune back open-vm-tools "for now" until they are ready. Therefore I'll add an open-vm-tools tasks assigned to myself, but set to incomplete until we know from the others if everything could move now or if we have to wait. P.S. There might be others like grub, s390x-tools, ... (see initial mail I linked above) which might trigger the same issue for this or other images, see bug 1934510 and the links from there. ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Also affects: unionfs-fuse (Ubuntu) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: open-vm-tools (Ubuntu) Status: New => Incomplete ** Changed in: gvfs (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: unionfs-fuse (Ubuntu) Assignee: (unassigned) => Graham Inggs (ginggs) ** Changed in: open-vm-tools (Ubuntu) Assignee: (unassigned) => Christian Ehrhardt (paelzer) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: New Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Status in open-vm-tools package in Ubuntu: Incomplete Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1548486 Title: Sleep hook in a subdirectory ignored but causes double execution of previous hook Status in pm-utils: Won't Fix Status in pm-utils package in Ubuntu: Confirmed Bug description: The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes one (95packagekit/95packagekit) that is stored in a subdirectory. This has two effects: 1the hook is not run; 2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is run for a second time instead. Presumably #1 is wrong, and results from an installation fault in packagekit, separately reported as bug 1548480. #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm- functions computes a list of to-be-executed hooks that includes directories but neither fully validates each such hook as a regular file nor handles a set of to-be-executed hooks in a subdirectory. At lines 243 on, there is a code path with no else clause through which the $hook from the previous iteration can be accidentally reused: if [ -f "$syshooks/$base" ]; then hook="$syshooks/$base" elif [ -f "$phooks/$base" ]; then hook="$phooks/$base" fi An easy fix is to insert the missing else clause before the fi line so that the script skips the subdirectory or other non-regular file and carries on with the next correctly specified hook: if [ -f "$syshooks/$base" ]; then hook="$syshooks/$base" elif [ -f "$phooks/$base" ]; then hook="$phooks/$base" else continue fi Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2. However the relevant pm-utils code dates back to 2008, pm-utils upstream version 1.1.0. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions] ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Mon Feb 22 17:10:53 2016 InstallationDate: Installed on 2016-02-21 (0 days ago) InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pm-utils/+bug/1548486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook
** Tags removed: server-todo ** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1548486 Title: Sleep hook in a subdirectory ignored but causes double execution of previous hook Status in pm-utils: Won't Fix Status in pm-utils package in Ubuntu: Confirmed Bug description: The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes one (95packagekit/95packagekit) that is stored in a subdirectory. This has two effects: 1the hook is not run; 2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is run for a second time instead. Presumably #1 is wrong, and results from an installation fault in packagekit, separately reported as bug 1548480. #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm- functions computes a list of to-be-executed hooks that includes directories but neither fully validates each such hook as a regular file nor handles a set of to-be-executed hooks in a subdirectory. At lines 243 on, there is a code path with no else clause through which the $hook from the previous iteration can be accidentally reused: if [ -f "$syshooks/$base" ]; then hook="$syshooks/$base" elif [ -f "$phooks/$base" ]; then hook="$phooks/$base" fi An easy fix is to insert the missing else clause before the fi line so that the script skips the subdirectory or other non-regular file and carries on with the next correctly specified hook: if [ -f "$syshooks/$base" ]; then hook="$syshooks/$base" elif [ -f "$phooks/$base" ]; then hook="$phooks/$base" else continue fi Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2. However the relevant pm-utils code dates back to 2008, pm-utils upstream version 1.1.0. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions] ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Mon Feb 22 17:10:53 2016 InstallationDate: Installed on 2016-02-21 (0 days ago) InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pm-utils/+bug/1548486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
FYI triggered again for me due to unattended upgrades. The time in the journal when things go down matches the unpack/configuee/install phase of - accountsservice:amd64 0.6.55-0ubuntu12~20.04.5 - libaccountsservice0:amd64 0.6.55-0ubuntu12~20.04.5 - dbus:amd64 1.12.16-2ubuntu2.1 I - again - had the usual suspect entries: systemd[1]: Starting Daily apt upgrade and clean activities... dbus-daemon[2266]: [system] Reloaded configuration dbus-daemon[2266]: Unknown group "power" in message bus configuration file systemd[1]: Reloading. systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated I didn't see anything in the log we didn't have before, but for completeness I'm attaching journal of the issue and a few hours before it ** Attachment added: "journal entries around the issues happening on unattended-upgrades" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+attachment/5541619/+files/fail-18Nov-6-24-07.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Incomplete Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached
[Desktop-packages] [Bug 1950470] [NEW] crashed shells in all tabs by pasting huge content and closing the tab
Public bug reported: By accident I did paste a lot (~80 pages) of content into a terminal tab in Tilix that was not in an editor as I thought. It started to handle all that input and I wanted to abort it. CTRL+C didn't change anything (as nothing was running, it was all text no commands). So I closed the tab that was getting all the input. This got tilix and essentially every VTE terminal stuck. This is how it looks: 0 1000 1854698 1854697 20 0 1941816 577108 -Rl ? 80:55 | \_ tilix --action=app-new-window 0 1000 1867343 1854698 20 0 50440 42188 poll_s Ss+ pts/3 0:05 | \_ /bin/bash 0 1000 1764144 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 1962053 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 3036766 1854698 20 0 50452 42240 poll_s Ss+ pts/6 0:00 | \_ /bin/bash 0 1000 3180194 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 3180305 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 3434428 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 3532625 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 3533476 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 3534456 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 3534954 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 3535210 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 1635392 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 1389820 1854698 20 0 63880 55680 poll_s Ss+ pts/8 0:05 | \_ /bin/bash 0 1000 2077655 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 2078150 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 210 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 2107834 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 2107997 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 2181005 1854698 20 0 50428 42544 do_wai Ss pts/0 0:00 | \_ /bin/bash 0 1000 3712709 2181005 20 0 63044 21284 poll_s S+ pts/0 0:00 | | \_ vim 0 1000 2182293 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 2182732 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 2205687 1854698 20 0 50432 43052 poll_s Ss+ pts/10 0:00 | \_ /bin/bash 0 1000 3393623 1854698 20 0 50548 42476 poll_s Ss+ pts/13 0:01 | \_ /bin/bash 0 1000 3531324 1854698 20 0 50548 43044 poll_s Ss+ pts/16 0:00 | \_ /bin/bash 0 1000 3535548 1854698 20 0 50548 42420 poll_s Ss+ pts/18 0:00 | \_ /bin/bash 0 1000 3701275 1854698 20 0 50564 44212 poll_s Ss+ pts/2 0:00 | \_ /bin/bash Also yakuake (using VTE Terminal as well) is stuck. Opening new tabs or new instances of tilix does not work either, all are stuck. Using a different terminal like one using gnome-terminal-server still works, so it really seems to be all VTE users that are affected. ** Affects: tilix (Ubuntu) Importance: Undecided Status: New ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Also affects: vte2.91 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1950470 Title: crashed shells in all tabs by pasting huge content and closing the tab Status in tilix package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: By accident I did paste a lot (~80 pages) of content into a terminal tab in Tilix that was not in an editor as I thought. It started to handle all that input and I wanted to abort it. CTRL+C didn't change anything (as nothing was running, it was all text no commands). So I closed the tab that was getting all the input. This got tilix and essentially every VTE terminal stuck. This is how it looks: 0 1000 1854698 1854697 20 0 1941816 577108 -Rl ? 80:55 | \_ tilix --action=app-new-window 0 1000 1867343 1854698 20 0 50440 42188 poll_s Ss+ pts/3 0:05 | \_ /bin/bash 0 1000 1764144 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 1962053 1854698 20 0 0 0 - Z? 0:00 | \_ [sh] 0 1000 3036766 1854698 20 0 50452
[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
As outlined in #55 unless we identify a smaller set of fixes I'm unsure what we could do for Focal. I'm out of ideas, the only one good thing is that it seems better in later versions and got more rare. But I hate when I do not understand all of a problem, here I might need help from Desktop-oriented thinking - hence I'll subscribe the desktop team if they might know better. ** Changed in: spice-protocol (Ubuntu Focal) Status: Triaged => Won't Fix ** Changed in: spice-gtk (Ubuntu Focal) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-gtk package in Ubuntu: Fix Released Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-gtk source package in Focal: Won't Fix Status in spice-protocol source package in Focal: Won't Fix Status in spice-vdagent source package in Focal: Invalid Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909665] Re: [MIR] ibus-libpinyin dependencies
As per the discussion on https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1910372/comments/9 We should down the road consider and recheck if we can move all to 5.4 then. I'll re-open the task, but since it isn't waiting on the MIR Team as "incomplete" for now. Next steps (suggested): - Evaluate lua using programs if now we could move them all to 5.4. If not file upstream issues (this could be done in 22.04). - Then later once those hopefully resolved (>=22.10) one could do the actual change to packages. Anyone can step up to start tackling those steps. So far this is just a bit of help for getting this into the right path, not a commitment. ** Changed in: lua5.4 (Ubuntu) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to opencc in Ubuntu. https://bugs.launchpad.net/bugs/1909665 Title: [MIR] ibus-libpinyin dependencies Status in lua5.4 package in Ubuntu: Incomplete Status in opencc package in Ubuntu: Fix Released Bug description: Please include these packages in Ubuntu's component main: * lua5.4 * opencc ibus-libpinyin provides the default method for inputting simplified Chinese, and is shipped with the desktop ISO. The latest Debian version of ibus-libpinyin couldn't migrate in hirsute, though, since it depends on liblua5.4-0 and libopencc1.1 which are both in universe. For now I built ibus-libpinyin in Ubuntu with lua5.3 and without opencc support. However, it would be preferable to be able to sync the fully featured package from Debian. lua5.2 and lua5.3 are already in main. opencc is a library for converting characters between traditional Chinese and simplified Chinese, and has been in main previously (trusty). As regards bug subscribing, I assume that ~ubuntu-server is a suitable candidate for lua5.4 and that ~desktop-packages should be subscribed to opencc bugs. Bugs lua5.4 --- There are no open bugs in version 5.4.2 Bugs opencc --- https://github.com/byvoid/opencc/issues https://bugs.launchpad.net/ubuntu/+source/opencc No open Debian bugs. I have read https://wiki.ubuntu.com/MainInclusionProcess#Main_Inclusion_requirements and haven't found any issues that would prevent the proposed main inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua5.4/+bug/1909665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794997] Re: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available
I've dupped another case onto this, it stays an issue that from the libvirt side has been handled by https://gitlab.com/libvirt/libvirt/-/commit/8c70d04bab7278c96390a913fa949a17cd3124f9 which is in >=Bionic. AFAIU remaining issues as outlined in comment #2 are still considered more an libnl/driver than a libvirt issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1794997 Title: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available Status in libnl3 package in Ubuntu: Expired Status in libvirt package in Ubuntu: Expired Bug description: We are observing the following error while creating VMs Sep 27 14:25:47 xpl-dvt-41 libvirtd[4927]: 2018-09-27 21:25:47.387+: 4927: error : virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available This message is observed with latest Bionic libvirt packages. lab@xpl-dvt-35:~$ dpkg -l | grep libvirt ii gir1.2-libvirt-glib-1.0:amd64 1.0.0-1 amd64GObject introspection files for the libvirt-glib library ii libsys-virt-perl 4.0.0-1 amd64Perl module providing an extension for the libvirt library ii libvirt-bin 4.0.0-1ubuntu8.5 amd64programs for the libvirt library ii libvirt-clients 4.0.0-1ubuntu8.5 amd64Programs for the libvirt library ii libvirt-daemon4.0.0-1ubuntu8.5 amd64Virtualization daemon ii libvirt-daemon-system 4.0.0-1ubuntu8.5 amd64Libvirt daemon configuration files ii libvirt-glib-1.0-0:amd64 1.0.0-1 amd64libvirt GLib and GObject mapping library ii libvirt0:amd644.0.0-1ubuntu8.5 amd64library for interfacing with different virtualization systems ii python-libvirt4.0.0-1 amd64libvirt Python bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1794997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Tags added: server-todo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt
Since Debian is also affected I filed it there as well:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248
** Bug watch added: Debian Bug tracker #995248
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248
** Also affects: umockdev (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bolt in Ubuntu.
https://bugs.launchpad.net/bugs/1945321
Title:
umockdev 0.16.3-1 breaks autopkgtest of bolt
Status in bolt package in Ubuntu:
Invalid
Status in umockdev package in Ubuntu:
In Progress
Status in umockdev package in Debian:
Unknown
Bug description:
The test of bolt fails with the new version due to a crash:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz
...
Trace/breakpoint trap (core dumped)
The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
python3-dbusmock and the new version causes this.
Retrying autopkgtest locally with no, all and just umockdev from proposed
and it seems reproducible.
- impish-release - works
- impish-all-proposed - crashes
- impish-release + umockdev+libc6 from proposed - crashes
Repro:
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
FYI:
Downgrading to umockdev 0.16.2-1 in the same environment does not
eliminate the issue. So it might happen at the bolt test-build time.
Debian has the same issue in:
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz
The new mockdev fails to create /sys/bus which is requested by the test.
From there the error path is what crashes, but the root cause is why we enter
the error-path in the first place.
One should be aware, this fail is "normal" if the environment is not mocked.
Even in the good case the different calls with/without umockdev lead to
exactly the same crash.
# good
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
# same crash as the new version has with umockdev-wrapper
$ gdb /usr/libexec/installed-tests/bolt/test-power
This is based on ldpreload.
$ cat /usr/bin/umockdev-wrapper
#!/bin/sh
# Wrapper program to preload the libumockdev library, so that test programs
can
# set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"
Gut feeling: it seems the mocking no more happens, and due to that
it runs into the non-mocked crash
Debugging with that:
$ pull-lp-source bolt
$ cd bolt-0.9.1/tests
$ gdb /usr/libexec/installed-tests/bolt/test-power
(gdb) set environment LD_PRELOAD libumockdev-preload.so.0
(gdb) b mock_sysfs_init
(gdb) run
With that we can see that while the crash is somewhere inside g_warning the
reason is in the g_mkdir failing with the new umockdev.
Good-case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 11444)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 11445)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = 0
(gdb) n
188 cls = g_build_filename (sys, "class", NULL);
Bad-Case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 17082)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 17083)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = -1
(gdb) n
186 g_warning ("could not create %s", bus);
(gdb) n
[Desktop-packages] [Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt
** Changed in: bolt (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bolt in Ubuntu.
https://bugs.launchpad.net/bugs/1945321
Title:
umockdev 0.16.3-1 breaks autopkgtest of bolt
Status in bolt package in Ubuntu:
Invalid
Status in umockdev package in Ubuntu:
In Progress
Bug description:
The test of bolt fails with the new version due to a crash:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz
...
Trace/breakpoint trap (core dumped)
The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
python3-dbusmock and the new version causes this.
Retrying autopkgtest locally with no, all and just umockdev from proposed
and it seems reproducible.
- impish-release - works
- impish-all-proposed - crashes
- impish-release + umockdev+libc6 from proposed - crashes
Repro:
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
FYI:
Downgrading to umockdev 0.16.2-1 in the same environment does not
eliminate the issue. So it might happen at the bolt test-build time.
Debian has the same issue in:
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz
The new mockdev fails to create /sys/bus which is requested by the test.
From there the error path is what crashes, but the root cause is why we enter
the error-path in the first place.
One should be aware, this fail is "normal" if the environment is not mocked.
Even in the good case the different calls with/without umockdev lead to
exactly the same crash.
# good
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
# same crash as the new version has with umockdev-wrapper
$ gdb /usr/libexec/installed-tests/bolt/test-power
This is based on ldpreload.
$ cat /usr/bin/umockdev-wrapper
#!/bin/sh
# Wrapper program to preload the libumockdev library, so that test programs
can
# set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"
Gut feeling: it seems the mocking no more happens, and due to that
it runs into the non-mocked crash
Debugging with that:
$ pull-lp-source bolt
$ cd bolt-0.9.1/tests
$ gdb /usr/libexec/installed-tests/bolt/test-power
(gdb) set environment LD_PRELOAD libumockdev-preload.so.0
(gdb) b mock_sysfs_init
(gdb) run
With that we can see that while the crash is somewhere inside g_warning the
reason is in the g_mkdir failing with the new umockdev.
Good-case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 11444)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 11445)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = 0
(gdb) n
188 cls = g_build_filename (sys, "class", NULL);
Bad-Case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 17082)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 17083)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = -1
(gdb) n
186 g_warning ("could not create %s", bus);
(gdb) n
** (/usr/libexec/installed-tests/bolt/test-power:17078): WARNING **:
15:11:06.614: could not create /tmp/umockdev.TK2VA1/sys/bus
Thread 1 "test-power" received signal SIGTRAP, Trace/breakpoint trap.
I'll tag this update-excuse and FYI-subscribe Martin who has done the Debian
upload and the Ubuntu sync of this on 16th Sept (post
[Desktop-packages] [Bug 1945321] [NEW] umockdev 0.16.3-1 breaks autopkgtest of bolt
Public bug reported:
The test of bolt fails with the new version due to a crash:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz
...
Trace/breakpoint trap (core dumped)
The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
python3-dbusmock and the new version causes this.
Retrying autopkgtest locally with no, all and just umockdev from proposed
and it seems reproducible.
- impish-release - works
- impish-all-proposed - crashes
- impish-release + umockdev+libc6 from proposed - crashes
Repro:
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
FYI:
Downgrading to umockdev 0.16.2-1 in the same environment does not
eliminate the issue. So it might happen at the bolt test-build time.
Debian has the same issue in:
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz
The new mockdev fails to create /sys/bus which is requested by the test.
>From there the error path is what crashes, but the root cause is why we enter
the error-path in the first place.
One should be aware, this fail is "normal" if the environment is not mocked.
Even in the good case the different calls with/without umockdev lead to
exactly the same crash.
# good
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
# same crash as the new version has with umockdev-wrapper
$ gdb /usr/libexec/installed-tests/bolt/test-power
This is based on ldpreload.
$ cat /usr/bin/umockdev-wrapper
#!/bin/sh
# Wrapper program to preload the libumockdev library, so that test programs can
# set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"
Gut feeling: it seems the mocking no more happens, and due to that
it runs into the non-mocked crash
Debugging with that:
$ pull-lp-source bolt
$ cd bolt-0.9.1/tests
$ gdb /usr/libexec/installed-tests/bolt/test-power
(gdb) set environment LD_PRELOAD libumockdev-preload.so.0
(gdb) b mock_sysfs_init
(gdb) run
With that we can see that while the crash is somewhere inside g_warning the
reason is in the g_mkdir failing with the new umockdev.
Good-case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 11444)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 11445)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = 0
(gdb) n
188 cls = g_build_filename (sys, "class", NULL);
Bad-Case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 17082)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 17083)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = -1
(gdb) n
186 g_warning ("could not create %s", bus);
(gdb) n
** (/usr/libexec/installed-tests/bolt/test-power:17078): WARNING **:
15:11:06.614: could not create /tmp/umockdev.TK2VA1/sys/bus
Thread 1 "test-power" received signal SIGTRAP, Trace/breakpoint trap.
I'll tag this update-excuse and FYI-subscribe Martin who has done the Debian
upload and the Ubuntu sync of this on 16th Sept (post FF).
** Affects: bolt (Ubuntu)
Importance: Undecided
Status: New
** Affects: umockdev (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Also affects: bolt (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- 0.16.3-1 breaks autopkgtest of bolt
+ umockdev 0.16.3-1 breaks autopkgtest of bolt
** Tags added: update-excuse
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bolt in Ubuntu.
https://bugs.launchpad.net/bugs/1945321
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
The DNSmasq change is in impish as well. Since we (intentionally) referenced but not closed the bug by the upload I'll have to tag that manually. ** Changed in: dnsmasq (Ubuntu Impish) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Fix Released Status in network-manager source package in Impish: Fix Released Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
dnsmasq tested all fine with the new NM. Only the odd systemd blocker holds us back now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Triaged Status in network-manager source package in Impish: New Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Merge] ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel
This is in proposed and working fine there. -- https://code.launchpad.net/~paelzer/ubuntu/+source/network-manager/+git/network-manager/+merge/405081 Your team Desktop Packages is requested to review the proposed merge of ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
The new NM tests were fine (even against the old dnsmasq due to the or in the regex). NM hit a few non related systemd test issues - I re-triggered those. Finally I did now start the new NM tests against the blocked dnsmasq. Overall that should hopefully resolve both and let them migrate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Triaged Status in network-manager source package in Impish: New Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Merge] ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel
The proposal to merge ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel has been updated. Status: Needs review => Approved For more details, see: https://code.launchpad.net/~paelzer/ubuntu/+source/network-manager/+git/network-manager/+merge/405081 -- Your team Desktop Packages is requested to review the proposed merge of ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Merge] ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel
I wasn't aware of that tree - thanks for the hint, I cloned rebased and pushed the change there as well. To ssh://git.launchpad.net/ubuntu/+source/network-manager * [new tag] upload/1.30.0-1ubuntu4 -> upload/1.30.0-1ubuntu4 Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading network-manager_1.30.0-1ubuntu4.dsc: done. Uploading network-manager_1.30.0-1ubuntu4.debian.tar.xz: done. Uploading network-manager_1.30.0-1ubuntu4_source.buildinfo: done. Uploading network-manager_1.30.0-1ubuntu4_source.changes: done. Successfully uploaded packages. And to also cover this extra repo: To git+ssh://git.launchpad.net/network-manager 87d561d6..9996e637 ubuntu/master -> ubuntu/master -- https://code.launchpad.net/~paelzer/ubuntu/+source/network-manager/+git/network-manager/+merge/405081 Your team Desktop Packages is requested to review the proposed merge of ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Merge] ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel
Hi, I thought about dropping dynamic - but not ALL test cases switch to forever. There were a few that still returned dynamic (something with a wireless connection for example). I decided against a massive matrix of testcase->output and went for the simple yet reasonable change. -- https://code.launchpad.net/~paelzer/ubuntu/+source/network-manager/+git/network-manager/+merge/405081 Your team Desktop Packages is requested to review the proposed merge of ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
Ok, as planned I can reproduce this in local autopkgtest. Multiple hits on: AssertionError: Regex didn't match: 'inet6 2600::[0-9a-f:]+/64 scope global (?:tentative )?(?:mngtmpaddr )?(?:noprefixroute )?dynamic' not found in '14: eth42@veth42: mtu 1500 qdisc noqueue state UP group default qlen 1000\nlink/ether d6:77:5c:e0:6e:89 brd ff:ff:ff:ff:ff:ff\ninet6 2600::19/128 scope global dynamic noprefixroute \n valid_lft 86399sec preferred_lft 86399sec\ninet6 2600::4d67:83f1:60b3:9385/64 scope global noprefixroute \n valid_lft forever preferred_lft forever\ninet6 fe80::892a:6b8:c86a:50a2/64 scope link noprefixroute \n valid_lft forever preferred_lft forever\n' Due to the changes this is dynamic->forever for some, but not all, of the cases. An MP has been proposed here [1] which in local VM based autopkgtest already succeeded. @Iain/Desktop-team - would you have a look and if you agree upload that NM update? [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/network- manager/+git/network-manager/+merge/405081 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Triaged Status in network-manager source package in Impish: New Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Merge] ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel
Christian Ehrhardt has proposed merging
~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior
into ubuntu/+source/network-manager:ubuntu/impish-devel.
Requested reviews:
Desktop Packages (desktop-packages)
Iain Lane (laney)
Canonical Server Team (canonical-server)
Canonical Server packageset reviewers (canonical-server-packageset-reviewers)
Ubuntu Server Dev import team (usd-import-team)
Related bugs:
Bug #1894619 in dnsmasq (Ubuntu): "[2.82 regression] router announcements
have 'forever' lifetime by default"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619
For more details, see:
https://code.launchpad.net/~paelzer/ubuntu/+source/network-manager/+git/network-manager/+merge/405081
--
Your team Desktop Packages is requested to review the proposed merge of
~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior
into ubuntu/+source/network-manager:ubuntu/impish-devel.
diff --git a/debian/changelog b/debian/changelog
index ec1fe7b..31ddee8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+network-manager (1.30.0-1ubuntu4) impish; urgency=medium
+
+ * d/t/nm.py: adapt to changes dnsmasq behavior (LP: #1894619)
+
+ -- Christian Ehrhardt Fri, 02 Jul 2021 11:13:46 +0200
+
network-manager (1.30.0-1ubuntu3) hirsute; urgency=medium
* SECURITY UPDATE: crash via setting match.path
diff --git a/debian/tests/nm.py b/debian/tests/nm.py
index f4fe46d..529f4cb 100755
--- a/debian/tests/nm.py
+++ b/debian/tests/nm.py
@@ -357,7 +357,7 @@ class NetworkManagerTest(network_test_base.NetworkTestBase):
expected_ip_a.append('inet6 2600::[0-9a-f]+/')
else:
# has address with our prefix and MAC
-expected_ip_a.append('inet6 2600::[0-9a-f:]+/64 scope global (?:tentative )?(?:mngtmpaddr )?(?:noprefixroute )?dynamic')
+expected_ip_a.append('inet6 2600::[0-9a-f:]+/64 scope global (?:tentative )?(?:mngtmpaddr )?(?:noprefixroute )?(dynamic|\n\s*valid_lft forever preferred_lft forever)')
# has address with our prefix and random IP (Privacy
# Extension), if requested
priv_re = 'inet6 2600:[0-9a-f:]+/64 scope global temporary (?:tentative )?(?:mngtmpaddr )?dynamic'
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
As expected this is now ready in proposed and blocked on the NM test, example: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/n/network-manager/20210701_151447_a29ef@/log.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Triaged Status in network-manager source package in Impish: New Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
According to the discussion dnsmasq will revert to the upstream intended behavior. I added an open impish task to reflect that. At the same time this makes network-mamager expose the test issue we initially found it with. An example can already be seen in PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4595/+packages TestLog: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4595/impish/amd64/n/network-manager/20 Note: I'm not sure if all of the test fails there are due to this change. ** Also affects: dnsmasq (Ubuntu Impish) Importance: High Status: Fix Released ** Also affects: dnsmasq (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: dnsmasq (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: dnsmasq (Ubuntu Groovy) Status: New => Fix Released ** Changed in: dnsmasq (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: dnsmasq (Ubuntu Impish) Status: Fix Released => Triaged ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Groovy) Status: New => Invalid ** Changed in: network-manager (Ubuntu Hirsute) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Triaged Status in network-manager source package in Impish: New Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
I have not found any other test issues than the expected NM one. So I'm uploading since - to some extend - we want to see if anything else breaks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Triaged Status in network-manager source package in Impish: New Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812456] Re: [MIR] libflatpak0
** Changed in: flatpak (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1812456 Title: [MIR] libflatpak0 Status in flatpak package in Ubuntu: Incomplete Bug description: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak0 in main so we can easily build such applications. It takes a lot of work to make these dependencies optional and sometimes that is not possible. We don't need the Flatpak functionality to work by default and do not expect any other Flatpak packages to be installed by default. Default packages that have flatpak integration: - gnome-control-center (application panel). - malcontent (parental controls) Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Multiple default packages have libflatpak as a dependency, including malcontent (LP: #1892456). Security This will need a Security review. https://security-tracker.debian.org/tracker/source-package/flatpak There have been two CVEs, both have been fixed in all supported Ubuntu releases. More recently, there is LP: #1815528 Quality Assurance = Bug subscriber: should be Ubuntu Desktop Bugs https://bugs.launchpad.net/ubuntu/+source/flatpak https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=flatpak https://github.com/flatpak/flatpak/issues tests are run as build tests (with dh_auto_test) and installed autopkgtests on Debian and Ubuntu. https://ci.debian.net/packages/f/flatpak http://autopkgtest.ubuntu.com/packages/f/flatpak UI Standards N/A Dependencies All in main except for libostree-1-1 (LP: #1892454) Standards Compliance Package uses standards version 4.5.0. Maintenance === - Actively developed upstream https://github.com/flatpak/flatpak - Maintained in Debian by the pkg-utopia team but more specifically, it is maintained by Simon McVittie (smcv) who maintains Flatpak, ostree, xdg-dbus-proxy, xdg-desktop-portal and xdg-desktop-portal-gtk. short dh7 style rules, dh compat 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1812456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932537] Re: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem)
Cups rightfully includes nameservices like: #include After our analysis in bug 1890858 I think it is fair to request an SRU update apparmor in Focal (only needed there, see bug 1890858 for details). As it would fix this element in Cups and actually in many other potential places as well. Adding "unix (bind) type=dgram addr=@userdb-*," in abstractions/nameservice in Focal seems right to me. --- Furthermore abstractions/nameservice already wants to allow sssd: 37 # When using sssd, the passwd and group files are stored in an alternate path 38 # and the nss plugin also needs to talk to a pipe 39 /var/lib/sss/mc/group r, 40 /var/lib/sss/mc/initgroups r, 41 /var/lib/sss/mc/passwd r, 42 /var/lib/sss/pipes/nss rw, I don't know if /var/lib/sss/pipes/private/pam rw, is a default configuration nor if it would be a safe path to allow. But it could pretty much be. If ok this one would likely be needed/wanted in >=Bionic into abstractions/nameservice --- Both changes IMHO would have to be done by the security Team in regard to the apparmor package, therefore I'll add a bug task for this and assign them to have a look. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1932537 Title: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem) Status in apparmor package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: [Summary] My domain user can not access the local CUPS web interface due to apparmor denials. Adding the following two lines to /etc/apparmor.d/local/usr.sbin.cupsd fixes it: /var/lib/sss/pipes/private/pam rw, unix (bind) type=dgram addr=@userdb-*, [Details] I have a (relatively) clean install of Ubuntu 20.04 (no upgrade), which is joined to a Windows AD-domain via sssd, but currently used off site with cached credentials. When I try to log in with my domain user (who is in the lpadmingroup) at the local cups web interface (localhost:631 ...> Add Printer) with the default apparmor config for cupsd I get a: AVC apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd" name="/var/lib/sss/pipes/private/pam" pid=189759 comm="cupsd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 This already existed in Bionic and my workaround was to add '/var/lib/sss/pipes/private/pam rw,' to /etc/apparmor.d/local/usr.sbin.cupsd and reload the profile: # echo '/var/lib/sss/pipes/private/pam rw,' > /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd This worked in Bionic, but leads to a crash of cupsd in Focal when I try to log in as domain user with a the following log message nearby: AVC apparmor="DENIED" operation="bind" profile="/usr/sbin/cupsd" pid=189759 comm="cupsd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-7625b1ef65396344ef05f0a8aeda870e" This looks very similar to https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858 , so I applied the same fix and added 'unix (bind) type=dgram addr=@userdb-*,' to /etc/apparmor.d/local/usr.sbin.cupsd: # echo 'unix (bind) type=dgram addr=@userdb-*,' >> /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd Which fixed my problem. I am not an expert on apparmor, so I have no idea, if the first line gives too broad permissions. I think that there are two unrelated issues: 1) Cupsd cannot access sssd at all. This already existed in Bionic (but I failed to report the issue -- sorry for that). 2) Once the login succeeds, cups tries to resolve a uid/gid as it isn't known locally. To resolve it it needs to bind a unix socket. See: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/comments/37 I will attach a full log with added comments on what I did. [Infos] 1) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 2) apt-cache policy cups-daemon cups-daemon: Installiert: 2.3.1-9ubuntu1.1 Installationskandidat: 2.3.1-9ubuntu1.1 Versionstabelle: *** 2.3.1-9ubuntu1.1 500 500 http://ftp.uni-hannover.de/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://ftp.uni-hannover.de/ubuntu focal/main amd64 Packages 3)
[Desktop-packages] [Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Also blocking isc-dhcp now, added a task ** Also affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Changed in: isc-dhcp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1931088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931088] [NEW] boot-and-services tests fails in impish on armhf (248.3)
Public bug reported: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: glibc (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Also affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: glibc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86
[Desktop-packages] [Bug 1868116] Re: QEMU monitor no longer works
@Thomas - there is a leftover task here and I've filed [1] for it in the new tracker. What is the right state to move this bug here into now? [1]: https://gitlab.com/qemu-project/qemu/-/issues/137 ** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #137 https://gitlab.com/qemu-project/qemu/-/issues/137 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works Status in QEMU: Incomplete Status in qemu package in Ubuntu: Invalid Status in vte2.91 package in Ubuntu: Fix Released Status in qemu package in Debian: Fix Released Bug description: Repro: VTE $ meson _build && ninja -C _build && ninja -C _build install qemu: $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user --disable-linux-user --disable-docs --disable-guest-agent --disable-sdl --enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt --disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi --disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir --disable-seccomp --disable-glusterfs --disable-tpm --disable-numa --disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs --disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma --disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock --disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user --disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs --disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat --disable-qed --disable-parallels --disable-sheepdog --disable-avx2 --disable-nettle --disable-gnutls --disable-capstone --disable-tools --disable-libpmem --disable-iconv --disable-cap-ng $ make Test: $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso - switch to monitor with CTRL+ALT+2 - try to enter something Affects head of both usptream git repos. --- original bug --- It was observed that the QEMU console (normally accessible using Ctrl+Alt+2) accepts no input, so it can't be used. This is being problematic because there are cases where it's required to send commands to the guest, or key combinations that the host would grab (as Ctrl-Alt-F1 or Alt-F4). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu 1:4.2-3ubuntu2 Uname: Linux 5.6.0-rc6+ x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 12:16:31 2020 Dependencies: InstallationDate: Installed on 2017-06-13 (1009 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 1000 1000 34275 25235 29.2 qemu-system-x86_64 -m 4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel kvm -device nec-usb-xhci -serial vc -serial stdio -hda /home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio kvm-nx-lpage-re S0 0 34284 2 0.0 [kvm-nx-lpage-re] kvm-pit/34275 S0 0 34286 2 0.0 [kvm-pit/34275] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: qemu UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 To manage notifications about this bug go to:
Re: [Desktop-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite
On Mon, May 3, 2021 at 10:20 AM Ludovic Rousseau <1892...@bugs.launchpad.net> wrote: > > opensc-pkcs11.so is a PKCS#11 lib so the its API conforms to the > standard defined in https://docs.oasis- > open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html Thanks Ludovic for adding the expert details! And that makes me re-consider this to "yes we should add .symbols". > If you really need to move opensc-pkcs11.so & pkcs11-spy.so in a subdir > I would recommand to use /usr/lib/*/pkcs11/ as it is already the case. Well, since there are external users it will be much harder to move things. As they all need to be compatible (or adapted) to the new place. Still worth having a look to move them, but more complex and more potential impact than what I expected before your explanation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during
[Desktop-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite
Thank you Marco and Sebastien, > * the launchpad buglist has been triaged a bit and fixed issues closed Thanks! >From your bug cleanup did you spot any kind of setup/HW that you want to >restrict/exclude? Was there any common pattern that makes up most of the formerly seen bad reports? > * the dh_missing has been reported to Debian now, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987817 Yeah, I think that is enough for now. > the libraries are private (no .so provided, other softwares can't really build with it), ideally they would move it to a subdir but do we really need .symbols added in such cases? I agree this is a case where it is a tough decision if it is strictly required due to them being "meant" private. But I'd not agree that there are no .so files provided. root@h:~# dpkg -L opensc opensc-pkcs11 | grep '\.so' /usr/lib/x86_64-linux-gnu/libopensc.so.7.0.0 /usr/lib/x86_64-linux-gnu/libsmm-local.so.7.0.0 /usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11-spy.so /usr/lib/x86_64-linux-gnu/libopensc.so.7 /usr/lib/x86_64-linux-gnu/libsmm-local.so.7 /usr/lib/x86_64-linux-gnu/pkcs11/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/pkcs11-spy.so $ nm --dynamic $(dpkg -L opensc-pkcs11 | grep '\.so' | xargs) | pastebinit https://paste.ubuntu.com/p/7SpfQ5gW26/ So there are in theory symbols, but I agree it still is not really usable (or meant to be used). As there are for example no headers for it :-) And OTOH adding symbols files is a rather trivial task that protects against some bad breakage. So is it strictly mandatory: hmm, debatable ... I guess no. I'd say as prereq add symbols OR move to subdir - of which the latter is the much more useful and correct thing to do. And as there are no other users you won't have to touch any other package for that change. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards
