Is it kind of a serious bug or can it be ignored ? I want to switch to Fedora i3 but not doing it only beacuse of this error…I am also not sure this bug exists on all fedora spins + workstation or is it DE dependent error ?
I see, my mistake. It seems that problem started around May. It’s weird that no one find a solution over 7 months. I guess since it’s a systemd issue it effects all Linux distributions that uses systemd.
I guess it also means every fedora user is effected from this bug ? If that is the case and since I am using fedora for over a year now, using it with this bug should not be such a problem…?