4 ms·

I use KDE on Wayland. It works pretty well; there's still bugs I hit once in a while (vscode especially sometimes is missing dialog windows and I have to restar

I use KDE on Wayland. It works pretty well; there's still bugs I hit once in a while (vscode especially sometimes is missing dialog windows and I have to restart it).

MayeulC 7y ago
It works quite well, but it's very crashy. I tried yesterday (5.17.3 IIRC, mind you): plasmashell crashed, then followed by systemsettings5, and konsole. Drkonqui popped up for the bug report, but crashed halfway. Then popped up again with a link for manual bug reporting. Clicked it, it crashed again. Sometimes QML applets crash (there was a bug with the CUPS one recently, if there were duplicated job IDs), and bring down plasmashell with them. But that also happens on X11, which can leave the environment quite empty, and hard to debug for my non-techie family. On Wayland, I miss primary clipboard buffer (selection), which works on sway. Also, default popup placement is wrong. Besides that, not much. I really like KDE plasma, but started using sway for Wayland, and stayed for the tiling. I might think about writing a kwin module to ingest my sway config, and only that... :)
jhoechtl 7y ago
Blurry firefox, blurry thunderbird anybody? Still plasma on wayland related fixes in the pipeline. But getting close...
- pedrocr 7y ago
  At least for Firefox that probably means it's running with X emulation. But the Firefox Wayland backend works fine, it just needs to be enabled. But sure, Wayland still has quite a few corner cases like that.
  - jhoechtl 7y ago
    I know about GDK_BACKEND=wayland firefox That works on Gnome and sway, not on plasma. Intel GPU. Still open bugs on bugs.kde.org
    - pedrocr 7y ago
      I believe the correct variable these days is: MOZ_ENABLE_WAYLAND=1 firefox This makes firefox a full wayland app. But I only use sway, so maybe there are KDE specific bugs.

4 ms·

I use KDE on Wayland. It works pretty well; there's still bugs I hit once in a while (vscode especially sometimes is missing dialog windows and I have to restar

by scrollaway 7y ago

I use KDE on Wayland. It works pretty well; there's still bugs I hit once in a while (vscode especially sometimes is missing dialog windows and I have to restart it).

MayeulC 7y ago
It works quite well, but it's very crashy. I tried yesterday (5.17.3 IIRC, mind you): plasmashell crashed, then followed by systemsettings5, and konsole. Drkonqui popped up for the bug report, but crashed halfway. Then popped up again with a link for manual bug reporting. Clicked it, it crashed again. Sometimes QML applets crash (there was a bug with the CUPS one recently, if there were duplicated job IDs), and bring down plasmashell with them. But that also happens on X11, which can leave the environment quite empty, and hard to debug for my non-techie family. On Wayland, I miss primary clipboard buffer (selection), which works on sway. Also, default popup placement is wrong. Besides that, not much. I really like KDE plasma, but started using sway for Wayland, and stayed for the tiling. I might think about writing a kwin module to ingest my sway config, and only that... :)
jhoechtl 7y ago
Blurry firefox, blurry thunderbird anybody? Still plasma on wayland related fixes in the pipeline. But getting close...
- pedrocr 7y ago
  At least for Firefox that probably means it's running with X emulation. But the Firefox Wayland backend works fine, it just needs to be enabled. But sure, Wayland still has quite a few corner cases like that.
  - jhoechtl 7y ago
    I know about GDK_BACKEND=wayland firefox That works on Gnome and sway, not on plasma. Intel GPU. Still open bugs on bugs.kde.org
    - pedrocr 7y ago
      I believe the correct variable these days is: MOZ_ENABLE_WAYLAND=1 firefox This makes firefox a full wayland app. But I only use sway, so maybe there are KDE specific bugs.