backport fix for KDE bug 422385

[kervel]

Hello,

ubuntu 20.04

When using microk8s or k3s or anything else that uses overlayfs, a lot of overlayfs mounts are being created, making various plasma applications unusable (either by long lists of volumes or by high cpu usage or by becoming unresponsive)

This bug has been fixed in solid upstream: https://bugs.kde.org/show_bug.cgi?id=422385

https://github.com/KDE/solid/commit/4231d16822655da5a8f45c94414d5114386b2140

i think this should be a candidate for backporting to ubuntu 20.04 since the impact of the fix is limited and the positive impact of the bugfix is quite high, probably for a lot of users. This bugreport has many duplicates and discussions.

https://bugs.kde.org/show_bug.cgi?id=419018
https://bugs.kde.org/show_bug.cgi?id=416972

The diff from the upstream commit applies with some very minor modifications (i put my modified version in debian/patches and included it in debian/patches/series)

greetings,
Frank

[kervel (frank-dekervel)]

with the patch applied when i do solid-hardware5 list details i get entries like below for the overlayfs mounts (note the "ignored true")

udi = '/org/kde/fstab/overlay/run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/4cbfb5221162bade0a0bf27fa771c1e89344b72b2700cf01767762e2da025f48/rootfs'
  parent = '/org/kde/fstab' (string)
  vendor = 'overlay' (string)
  product = '/run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/4cbfb5221162bade0a0bf27fa771c1e89344b72b2700cf01767762e2da025f48/rootfs' (string)
  description = '/run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/4cbfb5221162bade0a0bf27fa771c1e89344b72b2700cf01767762e2da025f48/rootfs (overlay)' (string)
  icon = 'folder' (string)
  StorageAccess.accessible = true (bool)
  StorageAccess.filePath = '/run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/4cbfb5221162bade0a0bf27fa771c1e89344b72b2700cf01767762e2da025f48/rootfs' (string)
  StorageAccess.ignored = true (bool)

this is the steps i did:

apt-get source libkf5solid-bin
cd solid-5.68.0/
# put the patch attached in debian/patches and mention the filename of the patch in debian/patches/series
dpkg-buildpackage

this will result in some .deb packages which i installed. after this i had to logout/login before the changes were visible.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "patch that i have put in debian/patches" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]