homectl adopt accepts home directories/images as-is in their directories without copying them to /home.
homectl register is the same, but processes a .identity file to do the same.
So finally it supports the feature it promised it was meant for… easy portability of home directories. (And autodetection of images and directories in /home as usual)
A great step, combined with dynamic allocation of subuid/subgid with another API of systemd rather than static /etc/sub{u,g}id files, systemd-homed is actually a very promising thing to use….
I recently had an issue with taking screenshots and having an AVC Denial from SELinux every time I did that. Tracked it down to an issue with systemd-homed. After disabling that service the screenshots are now working normally again without those AVC Denials constantly pooping up. I don’t know why that was.
If you are saying that I don’t use systemd-homed then that would be because it was disabled due to the issues with SELinux. It is disabled on both computers. I tracked it down because I had the issue on both computers and then one stopped having that issue. And when I looked I saw that the systemd-homed was disabled on the computer that was not giveing the SELinux alerts when taking a screenshot. So now it is disabled on both computers.
I also don’t know why it would have been affecting screenshots but it was and it was rather annoying. The screenshots would work just fine but then there was always the extra step of dealing with those alerts for no reason at all…
Also another strange thing that I just noticed. I am trying to get to an error message that I just got this morning because my mate-settings-daemon crashed. Don’t know why that happened and things still appeared to be running OK but I rebooted anyway. I had that info in a nice graphical report on the desktop, but now I don’t know how to get back to it. So I went to a terminal and ran journalctl. The only problem with that was that I was getting messages from back around October 10. And in those messages I saw something like “systemd-homed successfully disabled”. So back when I was running 42 there was something that was disabling it. And back when I was running 42 I was not getting those SELinux alerts when taking screenshots. Just trying to post as much info about this as possible. I already have a bug report in about the SELinux alerts when taking screenshots and I put in that after disabling systemd-homed the problem went away. So there is that.
You use Fedora main distro or Atomic/Silverblue/Kinoite?
There seems to be some serious underlying problem…
“From back around Oct 10”…. could you re-invoke journalctl with -b to limit it to the current boot, after all the errors occur, pastebin or whatever, and post it here, please.
Yeah, main distro. Mate Compiz spin. I did file a bug report but nobody responded to it. But that issue is gone now. It is definitely disabled on both machines now. I have no idea why one thing would be affecting the other but just wanted to mention it here in case someone else had the same issue. We didn’t need to use journalctl to get the info that systemd-homed was involved in the problem. That info was right there when we looked at the details of the SELinux Alert. I had another thread up about it but I believe that thread is now marked as “solved”.
Just wanted to share as much info as possible here. I found the other thread where I talked about the issue. It is here… As you can see from the screenshot (which I was later told I should not post) of the SETroubleshoot Details window, systemd-homed was mentioned. Also I run two different computers and the issue had disappeared from the newer computer after an update. So we looked at that service and whether or not it was running on both computers. On the newer computer that was no longer having the issue the service was not in fact running. So we disabled it on the older computer and the issue went away there as well. No idea why but the problem was solved…