Menu
▾
▴
#557 AppImage doesn't start up in wayland
I've tried to start up the AppImage under wayland (kde plasma) unfortunately that doesn't work.
There is no error message or anything, it just directly returns to the terminal.
Starting it with GDK_BACKEND="x11" also didn't help. Is there any known way to make it work with wayland? It's the last application left stopping me from migrating to wayland (And so far I didn't find an replacement for it. So, Good Job :-) ).
Assigning to Jerome since I don't know. I could test but have too many other priorities. I'm still using xwindows in KDE Neon personally. I will have a huge hassle to shift to Wayland in the future if I have to finally move away from Task Coach. Currently, it's still working with my current setup…
If Jerome assigns back to me or ignores this, I'll leave it open to look into more sometime. Not sure if I will be able to figure anything out though.
ok, i've got more details.
As it seems, it does start up under wayland, but only, if I didn't start it up before under X.org using a different user. I'm guessing that the AppImage leaves some fixed-path-temporary files, with wrong permissions, or something similar. (I also can't start it up under x, if before I started it under wayland)
So the good news is. It starts up under wayland.
It is necessary to use GDK_BACKEND="x11".
The bad news is that the idle detection doesn't work under wayland.
The console's full with:
"Xlib: extension MIT-SCREEN-SAVER missing on display :2."
messages.
My best guess is, that taskcoach uses some screen saver functions for the idle detection.
And as it seems that will not get into xwayland. And since I don't think anybody will fix the idle detection in TaskCoach to work with wayland, you can't use Taskcoach under wayland. If you depend on the idle detection :-(.
I guess next year I start searching for an alternative, again, argh...
Thanks for the update, too bad about the issue. Maybe it can be fixed ever, but yeah, I wouldn't expect it.