-
the thread had no solution when I wrote, I assumed it was flatpak
-
You seem to have found a reason now, and it indeed seems to be flatpak again
And the reason is always the same, flatpak runs as intended and breaks stuff by default, people find issues, write a thread here to ask for proper flags and settings for stuff that works natively out of the box 90% of the time when installed from the native repos in serious distros.
Which brings us back to my point: it solves the wrong problem for the wrong people. Provides sandboxing and isolation for people that use it as a covenient software source unaware of its quirks.
For those aware of them it is useless because they will know enough to do the isolation and sanboxing were it matters themselves.
To be fair you did some good work understanding what was happening, so I ask you: why do you use flatpak?
I ain’t your brah mate.
Look, I am not that antagonistic man, no need to be this riled up. My main issue is that I lurk these threads to help people with their linux issues to help adoption, but we really have a lot of threads were flatpak is the issue, you can check the history.
I am sorry you did check to see if the native one works and reproduced the issue, I somehow understood the exact contrary, I apologize.
The next time I will ask the user to reproduce te issue with the native version before I start my rant.
My usecase is to turn on my machine in the morning, edit some text files and run a browser and some command line tools. Then i turn it off in the evening, nothing special. I got no beef with wayland and especially nothing against systemd btw.
Is there any chanche that your reboot aversion is due to wayland’s issues with session restoration?