Can you please verify if this is also a related bug from AppArmor? https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2156939
****************************** ### Acknowledgments to the Developers Dear developers, thank you very much for working on fixing this error. This bug report has cost me a massive amount of time and energy as a volunteer, and I am very happy and glad that my efforts were not in vain. ### Appreciation for Lukáš’s Work Furthermore, it appears that a systemd developer named Lukáš played a key role in resolving this bug. I sincerely thank this individual. He is a great person who, unlike his colleague, refrained from provocations. Surely, it works among developers just like it does everywhere else in society—there are good people and bad people. Some individuals try to cause harm, while others try to help, and that is why I am all the more grateful to the developer Lukáš, who had to smooth things over after his colleague from the same company and the same branch. ### Technical Alternatives for Fixing the Bug On the other hand, my opinion is that this bug could be fixed in several ways, or perhaps through a combination of both. It could also be addressed by fixing the code within systemd itself, or specifically within systemd-homed. There is another way to encrypt the home folder besides systemd-homed. It is an official solution from developers close to Google, and this tool is called fscrypt, with the difference being that it is an encryption manager in the Linux kernel. However, this manager itself is not part of the Linux kernel. I tested this specific solution for many years, and it worked completely without a hitch. It did not have these same bugs or these same problems. This means that if a similar approach were implemented in systemd-homed, there could not be such conflicts with FUSE or libfuse, or with AppArmor. Those conflicts simply wouldn't exist. Therefore, AppArmor itself could certainly be adapted or modified as well. That is also one of the solutions, or perhaps a combination of several. ### Importance of the Fix and Advantages of systemd-homed Furthermore, I will be very grateful if you create some sort of fix for this bug. This is because my configuration is neither useless nor is it some super exotic setup; on the contrary, it is highly rational. It is the best encryption of its kind. Fscrypt is the only encryption that operates at the filesystem level. It is the most efficient method of encryption, the least hardware-intensive, and the best in its category. For a personal computer, I believe it is the single best solution. And why did I choose the systemd-homed solution out of these two options? It is because it supports logging into the computer and simultaneously unlocking the screen using fingerprint FIDO2 hardware key. The official fscrypt manager does not support this. So for this very reason—since this is not some pointless experiment but rather a very serious, earnest, and practical use case for systemd- homed—I will be very glad for any bug fix that ensures everything works correctly, just as it truly should :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2150642 Title: systemd-homed + fscrypt: Incompatibility with fuse3. Critical bug report. Disrupted work of XDG Desktop Portal and flatpak To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/2150642/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
