Thanks. After downloading and trying to install the 6 .deb files, there is a dependency error with gvfs-backends, that relies on libgcrypt20 >= 1.11.0, while I only have 1.10.3-2build1:
$ sudo dpkg -i *.deb (Lecture de la base de données... 352980 fichiers et répertoires déjà installés.) Préparation du dépaquetage de gvfs_1.56.0-2ppa3_amd64.deb ... Dépaquetage de gvfs:amd64 (1.56.0-2ppa3) sur (1.54.0-1ubuntu2) ... Préparation du dépaquetage de gvfs-backends_1.56.0-2ppa3_amd64.deb ... Dépaquetage de gvfs-backends (1.56.0-2ppa3) sur (1.54.0-1ubuntu2) ... Préparation du dépaquetage de gvfs-common_1.56.0-2ppa3_all.deb ... Dépaquetage de gvfs-common (1.56.0-2ppa3) sur (1.54.0-1ubuntu2) ... Préparation du dépaquetage de gvfs-daemons_1.56.0-2ppa3_amd64.deb ... Dépaquetage de gvfs-daemons (1.56.0-2ppa3) sur (1.54.0-1ubuntu2) ... Préparation du dépaquetage de gvfs-fuse_1.56.0-2ppa3_amd64.deb ... Dépaquetage de gvfs-fuse (1.56.0-2ppa3) sur (1.54.0-1ubuntu2) ... Préparation du dépaquetage de gvfs-libs_1.56.0-2ppa3_amd64.deb ... Dépaquetage de gvfs-libs:amd64 (1.56.0-2ppa3) sur (1.54.0-1ubuntu2) ... dpkg: des problèmes de dépendances empêchent la configuration de gvfs-backends : gvfs-backends dépend de libgcrypt20 (>= 1.11.0); cependant : La version de libgcrypt20:amd64 sur le système est 1.10.3-2build1. dpkg: erreur de traitement du paquet gvfs-backends (--install) : problèmes de dépendances - laissé non configuré Paramétrage de gvfs-common (1.56.0-2ppa3) ... Paramétrage de gvfs-libs:amd64 (1.56.0-2ppa3) ... Paramétrage de gvfs-daemons (1.56.0-2ppa3) ... Paramétrage de gvfs:amd64 (1.56.0-2ppa3) ... Paramétrage de gvfs-fuse (1.56.0-2ppa3) ... Traitement des actions différées (« triggers ») pour libglib2.0-0t64:amd64 (2.80.0-6ubuntu3.2) ... Traitement des actions différées (« triggers ») pour man-db (2.12.0-4build2) ... Des erreurs ont été rencontrées pendant l'exécution : gvfs-backends -- 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/2047356 Title: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload Status in gvfs package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04.3 desktop, when running a k3s workload that uses volumes (using default local-path storageClass), process gvfs-disks2-volume-monitor can take around 100% of one CPU core, and process gsd-housekeeping around 25% of one CPU core. Even if the actual k3s workload is idle. Steps To Reproduce: - Use or install a desktop Ubuntu 22.04.3 (with default settings) - Install K3s on it (current version is "v1.28.4+k3s2"), with default settings: "curl -sfL https://get.k3s.io | sh -" - Deploy k8s manifests with many volumes, like https://gitlab.com/-/snippets/3634487: "wget https://gitlab.com/-/snippets/3634487/raw/main/deployment-with-many-volumes.yaml && sudo k3s kubectl apply -f deployment-with-many-volumes.yaml" - Check CPU consumption on the host, with top, gnome-system-monitor or anything else Expected behavior: Gnome desktop tools should not interfere with k3s. Actual behavior: Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of CPU, at least at provisioning time. Same CPU consumption if you then remove the workload ("sudo k3s kubectl delete -f deployment-with-many-volumes.yaml"), until the PVs are deleted by k3s. I have other workloads (with data in PVs) where this CPU consumption is always there, when the workload is running (even if idle) Additional context: The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522, but the workaround of comment https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev rule to ignore some loopback devices) does not help. Executing "systemctl stop --user gvfs-udisks2-volume-monitor" can be a temporary workaround Technical details: k3s uses containerd to run containers. The local-path storageClass mounts local volumes (physically stored in /var/lib/rancher/k3s/storage subfolders) in these containers. I suppose gnome applications try to scan these mount points. In this case, the solution might be to make them ignore them, a bit like https://github.com/moby/moby/blob/master/contrib/udev/80-docker.rules does for docker NB: Was initially reported on https://github.com/k3s-io/k3s/issues/9093 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+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
