https://community.kde.org/api.php?action=feedcontributions&user=Mgraesslin&feedformat=atomKDE Community Wiki - User contributions [en]2024-03-29T05:47:52ZUser contributionsMediaWiki 1.40.2https://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=82368Plasma/Wayland Known Significant Issues2018-12-27T11:40:56Z<p>Mgraesslin: /* Key repeat not working */</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== No vertical / horizontal maximize of Wayland native clients ===<br />
KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling).<br />
<br />
=== No Drag and Drop between Wayland native and Xwayland clients ===<br />
From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
'''Partly fixed''' since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input.<br />
<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== <s>QT_QPA_PLATFORM</s> ===<br />
<s>QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.</s><br />
<br />
'''Fixed'''<br />
by not setting the variable in system, but let every app decide on itself. With 5.11 setting this variable is not needed at all anymore, because it autodetects the windowing system.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys. See [https://github.com/xkbcommon/libxkbcommon/issues/40 xkbcommon-issue40] --> Explain how this issue is related?<br />
<br />
== Plasma ==<br />
=== <s>Virtual Desktops</s> ===<br />
<s>We don't have an API yet for virtual desktops, so pager is not working</s><br />
<br />
'''Fixed''' in Plasma 5.15<br />
<br />
=== Native Wayland windows are not restored ===<br />
Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has according to [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession their wiki] an own implementation for some time.<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== <s>wl_proxy_create_wrapper</s> ===<br />
<s>http://bugs.kde.org/381630</s><br />
<br />
'''Fixed''' in Qt 5.9.5<br />
<br />
=== <s>Key repeat not working</s> ===<br />
<s>See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]</s><br />
<br />
'''Fixed''' in Qt 5.13<br />
<br />
=== <s>Compose key not working</s> ===<br />
<s>See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]</s><br />
<br />
'''Fixed''' in Qt 5.11<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== <s>Fullscreen does not work</s> ===<br />
<s>see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]</s><br />
<br />
'''Fixed''' in Qt 5.12</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=82367Plasma/Wayland Known Significant Issues2018-12-27T11:40:37Z<p>Mgraesslin: /* Fullscreen does not work */</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== No vertical / horizontal maximize of Wayland native clients ===<br />
KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling).<br />
<br />
=== No Drag and Drop between Wayland native and Xwayland clients ===<br />
From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
'''Partly fixed''' since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input.<br />
<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== <s>QT_QPA_PLATFORM</s> ===<br />
<s>QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.</s><br />
<br />
'''Fixed'''<br />
by not setting the variable in system, but let every app decide on itself. With 5.11 setting this variable is not needed at all anymore, because it autodetects the windowing system.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys. See [https://github.com/xkbcommon/libxkbcommon/issues/40 xkbcommon-issue40] --> Explain how this issue is related?<br />
<br />
== Plasma ==<br />
=== <s>Virtual Desktops</s> ===<br />
<s>We don't have an API yet for virtual desktops, so pager is not working</s><br />
<br />
'''Fixed''' in Plasma 5.15<br />
<br />
=== Native Wayland windows are not restored ===<br />
Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has according to [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession their wiki] an own implementation for some time.<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== <s>wl_proxy_create_wrapper</s> ===<br />
<s>http://bugs.kde.org/381630</s><br />
<br />
'''Fixed''' in Qt 5.9.5<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
'''Fixed''' in Qt 5.13<br />
<br />
=== <s>Compose key not working</s> ===<br />
<s>See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]</s><br />
<br />
'''Fixed''' in Qt 5.11<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== <s>Fullscreen does not work</s> ===<br />
<s>see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]</s><br />
<br />
'''Fixed''' in Qt 5.12</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=82366Plasma/Wayland Known Significant Issues2018-12-27T11:40:20Z<p>Mgraesslin: /* Compose key not working */</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== No vertical / horizontal maximize of Wayland native clients ===<br />
KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling).<br />
<br />
=== No Drag and Drop between Wayland native and Xwayland clients ===<br />
From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
'''Partly fixed''' since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input.<br />
<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== <s>QT_QPA_PLATFORM</s> ===<br />
<s>QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.</s><br />
<br />
'''Fixed'''<br />
by not setting the variable in system, but let every app decide on itself. With 5.11 setting this variable is not needed at all anymore, because it autodetects the windowing system.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys. See [https://github.com/xkbcommon/libxkbcommon/issues/40 xkbcommon-issue40] --> Explain how this issue is related?<br />
<br />
== Plasma ==<br />
=== <s>Virtual Desktops</s> ===<br />
<s>We don't have an API yet for virtual desktops, so pager is not working</s><br />
<br />
'''Fixed''' in Plasma 5.15<br />
<br />
=== Native Wayland windows are not restored ===<br />
Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has according to [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession their wiki] an own implementation for some time.<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== <s>wl_proxy_create_wrapper</s> ===<br />
<s>http://bugs.kde.org/381630</s><br />
<br />
'''Fixed''' in Qt 5.9.5<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
'''Fixed''' in Qt 5.13<br />
<br />
=== <s>Compose key not working</s> ===<br />
<s>See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]</s><br />
<br />
'''Fixed''' in Qt 5.11<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]<br />
<br />
'''Fixed''' in Qt 5.12</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=82365Plasma/Wayland Known Significant Issues2018-12-27T11:39:52Z<p>Mgraesslin: /* wl_proxy_create_wrapper */</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== No vertical / horizontal maximize of Wayland native clients ===<br />
KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling).<br />
<br />
=== No Drag and Drop between Wayland native and Xwayland clients ===<br />
From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
'''Partly fixed''' since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input.<br />
<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== <s>QT_QPA_PLATFORM</s> ===<br />
<s>QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.</s><br />
<br />
'''Fixed'''<br />
by not setting the variable in system, but let every app decide on itself. With 5.11 setting this variable is not needed at all anymore, because it autodetects the windowing system.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys. See [https://github.com/xkbcommon/libxkbcommon/issues/40 xkbcommon-issue40] --> Explain how this issue is related?<br />
<br />
== Plasma ==<br />
=== <s>Virtual Desktops</s> ===<br />
<s>We don't have an API yet for virtual desktops, so pager is not working</s><br />
<br />
'''Fixed''' in Plasma 5.15<br />
<br />
=== Native Wayland windows are not restored ===<br />
Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has according to [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession their wiki] an own implementation for some time.<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== <s>wl_proxy_create_wrapper</s> ===<br />
<s>http://bugs.kde.org/381630</s><br />
<br />
'''Fixed''' in Qt 5.9.5<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
'''Fixed''' in Qt 5.13<br />
<br />
=== Compose key not working ===<br />
Will be fixed in Qt 5.11, [https://wiki.qt.io/Qt_5.11_Release expected May 2018]. See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
'''Fixed''' in Qt 5.11<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]<br />
<br />
'''Fixed''' in Qt 5.12</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=82364Plasma/Wayland Known Significant Issues2018-12-27T11:39:30Z<p>Mgraesslin: /* Virtual Desktops */</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== No vertical / horizontal maximize of Wayland native clients ===<br />
KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling).<br />
<br />
=== No Drag and Drop between Wayland native and Xwayland clients ===<br />
From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
'''Partly fixed''' since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input.<br />
<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== <s>QT_QPA_PLATFORM</s> ===<br />
<s>QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.</s><br />
<br />
'''Fixed'''<br />
by not setting the variable in system, but let every app decide on itself. With 5.11 setting this variable is not needed at all anymore, because it autodetects the windowing system.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys. See [https://github.com/xkbcommon/libxkbcommon/issues/40 xkbcommon-issue40] --> Explain how this issue is related?<br />
<br />
== Plasma ==<br />
=== <s>Virtual Desktops</s> ===<br />
<s>We don't have an API yet for virtual desktops, so pager is not working</s><br />
<br />
'''Fixed''' in Plasma 5.15<br />
<br />
=== Native Wayland windows are not restored ===<br />
Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has according to [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession their wiki] an own implementation for some time.<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
'''Fixed''' in Qt 5.9.5<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
'''Fixed''' in Qt 5.13<br />
<br />
=== Compose key not working ===<br />
Will be fixed in Qt 5.11, [https://wiki.qt.io/Qt_5.11_Release expected May 2018]. See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
'''Fixed''' in Qt 5.11<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]<br />
<br />
'''Fixed''' in Qt 5.12</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=82363Plasma/Wayland Known Significant Issues2018-12-27T11:38:32Z<p>Mgraesslin: /* QT_QPA_PLATFORM */</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== No vertical / horizontal maximize of Wayland native clients ===<br />
KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling).<br />
<br />
=== No Drag and Drop between Wayland native and Xwayland clients ===<br />
From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
'''Partly fixed''' since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input.<br />
<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== <s>QT_QPA_PLATFORM</s> ===<br />
<s>QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.</s><br />
<br />
'''Fixed'''<br />
by not setting the variable in system, but let every app decide on itself. With 5.11 setting this variable is not needed at all anymore, because it autodetects the windowing system.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys. See [https://github.com/xkbcommon/libxkbcommon/issues/40 xkbcommon-issue40] --> Explain how this issue is related?<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== Native Wayland windows are not restored ===<br />
Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has according to [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession their wiki] an own implementation for some time.<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
'''Fixed''' in Qt 5.9.5<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
'''Fixed''' in Qt 5.13<br />
<br />
=== Compose key not working ===<br />
Will be fixed in Qt 5.11, [https://wiki.qt.io/Qt_5.11_Release expected May 2018]. See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
'''Fixed''' in Qt 5.11<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]<br />
<br />
'''Fixed''' in Qt 5.12</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=82362Plasma/Wayland Known Significant Issues2018-12-27T11:35:59Z<p>Mgraesslin: /* Qt */</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== No vertical / horizontal maximize of Wayland native clients ===<br />
KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling).<br />
<br />
=== No Drag and Drop between Wayland native and Xwayland clients ===<br />
From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
'''Partly fixed''' since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input.<br />
<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
'''Fixed'''<br />
by not setting the variable in system, but let every app decide on itself. With 5.11 setting this variable is not needed at all anymore, because it autodetects the windowing system.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys. See [https://github.com/xkbcommon/libxkbcommon/issues/40 xkbcommon-issue40] --> Explain how this issue is related?<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== Native Wayland windows are not restored ===<br />
Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has according to [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession their wiki] an own implementation for some time.<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
'''Fixed''' in Qt 5.9.5<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
'''Fixed''' in Qt 5.13<br />
<br />
=== Compose key not working ===<br />
Will be fixed in Qt 5.11, [https://wiki.qt.io/Qt_5.11_Release expected May 2018]. See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
'''Fixed''' in Qt 5.11<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]<br />
<br />
'''Fixed''' in Qt 5.12</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=82361Plasma/Wayland Known Significant Issues2018-12-27T11:30:45Z<p>Mgraesslin: /* No vertical / horizontal maximize of Wayland native clients */</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== No vertical / horizontal maximize of Wayland native clients ===<br />
KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling).<br />
<br />
=== No Drag and Drop between Wayland native and Xwayland clients ===<br />
From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
'''Partly fixed''' since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input.<br />
<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
'''Fixed'''<br />
by not setting the variable in system, but let every app decide on itself. With 5.11 setting this variable is not needed at all anymore, because it autodetects the windowing system.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys. See [https://github.com/xkbcommon/libxkbcommon/issues/40 xkbcommon-issue40] --> Explain how this issue is related?<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== Native Wayland windows are not restored ===<br />
Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has according to [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession their wiki] an own implementation for some time.<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
'''Fixed''' in Qt 5.9.5<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
=== Compose key not working ===<br />
Will be fixed in Qt 5.11, [https://wiki.qt.io/Qt_5.11_Release expected May 2018]. See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
'''Fixed''' in Qt 5.11<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]<br />
<br />
'''Fixed''' in Qt 5.12</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.13_Errata&diff=80140Plasma/5.13 Errata2018-05-19T07:05:07Z<p>Mgraesslin: /* Wayland */</p>
<hr />
<div>Known issues in the Plasma 5.13 release.<br />
<br />
==Wayland==<br />
=== Plasma ===<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* No support for primary selection (middle-click to paste) [http://bugreports.qt.io/browse/QTBUG-66008 Qt Bug 66008]<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* No focus stealing prevention for Wayland windows<br />
* Task Switcher Uis displayed in the top-left corner of the screen instead of the center [https://bugs.kde.org/show_bug.cgi?id=386304 KDE Bug 386304]<br />
* System hangs when logging out [https://bugs.kde.org/show_bug.cgi?id=372789 KDE Bug 372789]<br />
=== Qt ===<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
=== GTK ===<br />
* GTK: windows don't have decorations (neither client nor server side)<br />
* GTK: windows are incorrectly placed<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=79086Plasma/Wayland Known Significant Issues2018-01-22T15:05:00Z<p>Mgraesslin: Middle click paste is a corner case feature and thus not a showstopper.</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== NVIDIA + XWayland ===<br />
XWayland also uses the DRM/GBM mechanism. Due to that XWayland is not supporting OpenGL on NVIDIA even if KWin would support NVIDIA's eglstream. This would result in a terrible experience for all gamers.<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys.<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630 (Fixed in Qt 5.9.5)<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
=== Compose key not working ===<br />
Will be fixed in Qt 5.11, [https://wiki.qt.io/Qt_5.11_Release expected May 2018]. See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.12_Errata&diff=79053Plasma/5.12 Errata2018-01-18T20:24:15Z<p>Mgraesslin: </p>
<hr />
<div>Known issues in the Plasma 5.12 release.<br />
<br />
==Kicker==<br />
Favourite system actions are no longer removable via right click menu - breaks/prevents sidebar hiding<br />
https://bugs.kde.org/show_bug.cgi?id=385463<br />
<br />
==Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* No support for primary selection (middle-click to paste)<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.19 lacks features or has bugs, we recommend XWayland 1.19<br />
* No focus stealing prevention for Wayland windows<br />
* Only partial window rules support for Wayland windows<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
* Large Icons Task Switcher UI displayed in the top-left corner of the screen instead of the center [https://bugs.kde.org/show_bug.cgi?id=386304 KDE Bug 386304]<br />
* System hangs when logging out [https://bugs.kde.org/show_bug.cgi?id=372789 KDE Bug 372789]<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons (fixed in 5.13)</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.12_Errata&diff=79010Plasma/5.12 Errata2018-01-15T17:00:53Z<p>Mgraesslin: </p>
<hr />
<div>Known issues in the Plasma 5.11 release.<br />
<br />
==Kicker==<br />
Favourite system actions are no longer removable via right click menu - breaks/prevents sidebar hiding<br />
https://bugs.kde.org/show_bug.cgi?id=385463<br />
<br />
==Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* No support for primary selection (middle-click to paste)<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.19 lacks features or has bugs, we recommend XWayland 1.19<br />
* No focus stealing prevention for Wayland windows<br />
* Only partial window rules support for Wayland windows<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=78938Plasma/Wayland Known Significant Issues2017-12-26T21:10:41Z<p>Mgraesslin: Remove DRM parts, it's implemented now</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== NVIDIA + XWayland ===<br />
XWayland also uses the DRM/GBM mechanism. Due to that XWayland is not supporting OpenGL on NVIDIA even if KWin would support NVIDIA's eglstream. This would result in a terrible experience for all gamers.<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys.<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
There's a crash I know (but fixing properly break X)<br />
Might be more stuff with SDDM, needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
=== Compose key not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=78756Plasma/Wayland Known Significant Issues2017-10-31T11:48:30Z<p>Mgraesslin: </p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]<br />
<br />
=== NVIDIA + XWayland ===<br />
XWayland also uses the DRM/GBM mechanism. Due to that XWayland is not supporting OpenGL on NVIDIA even if KWin would support NVIDIA's eglstream. This would result in a terrible experience for all gamers.<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys.<br />
<br />
== DRM ==<br />
<br />
=== Modes cannot be configured ===<br />
It's not yet possible to switch modes. Implemented with https://phabricator.kde.org/D8398<br />
<br />
=== Output cannot be rotated ===<br />
It's not yet possible to rotate the screen.<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
There's a crash I know (but fixing properly break X)<br />
Might be more stuff with SDDM, needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
=== Compose key not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=78708Plasma/Wayland Known Significant Issues2017-10-21T13:23:04Z<p>Mgraesslin: </p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not]<br />
<br />
=== NVIDIA + XWayland ===<br />
XWayland also uses the DRM/GBM mechanism. Due to that XWayland is not supporting OpenGL on NVIDIA even if KWin would support NVIDIA's eglstream. This would result in a terrible experience for all gamers.<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys.<br />
<br />
== DRM ==<br />
<br />
=== Modes cannot be configured ===<br />
It's not yet possible to switch modes. Implemented with https://phabricator.kde.org/D8398<br />
<br />
=== Output cannot be rotated ===<br />
It's not yet possible to rotate the screen.<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
There's a crash I know (but fixing properly break X)<br />
Might be more stuff with SDDM, needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
=== Compose key not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=78657Plasma/Wayland Known Significant Issues2017-10-12T19:41:34Z<p>Mgraesslin: </p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not]<br />
<br />
=== NVIDIA + XWayland ===<br />
XWayland also uses the DRM/GBM mechanism. Due to that XWayland is not supporting OpenGL on NVIDIA even if KWin would support NVIDIA's eglstream. This would result in a terrible experience for all gamers.<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys.<br />
<br />
== DRM ==<br />
<br />
=== Modes cannot be configured ===<br />
It's not yet possible to switch modes.<br />
<br />
=== Output cannot be rotated ===<br />
It's not yet possible to rotate the screen.<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
There's a crash I know (but fixing properly break X)<br />
Might be more stuff with SDDM, needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
=== Compose key not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.<br />
<br />
=== Fullscreen does not work ===<br />
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=78656Plasma/Wayland Known Significant Issues2017-10-12T15:53:14Z<p>Mgraesslin: </p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not]<br />
<br />
=== NVIDIA + XWayland ===<br />
XWayland also uses the DRM/GBM mechanism. Due to that XWayland is not supporting OpenGL on NVIDIA even if KWin would support NVIDIA's eglstream. This would result in a terrible experience for all gamers.<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys.<br />
<br />
== DRM ==<br />
<br />
=== Modes cannot be configured ===<br />
It's not yet possible to switch modes.<br />
<br />
=== Output cannot be rotated ===<br />
It's not yet possible to rotate the screen.<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
There's a crash I know (but fixing properly break X)<br />
Might be more stuff with SDDM, needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
=== Compose key not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=78655Plasma/Wayland Known Significant Issues2017-10-12T15:22:11Z<p>Mgraesslin: Remove multi-monitor section, this is already covered in the DRM section</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not]<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No configurable gestures ===<br />
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys.<br />
<br />
== DRM ==<br />
<br />
=== Modes cannot be configured ===<br />
It's not yet possible to switch modes.<br />
<br />
=== Output cannot be rotated ===<br />
It's not yet possible to rotate the screen.<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
=== Logout ===<br />
There's a crash I know (but fixing properly break X)<br />
Might be more stuff with SDDM, needs investigation<br />
<br />
=== No activities ===<br />
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
=== wl_proxy_create_wrapper ===<br />
http://bugs.kde.org/381630<br />
<br />
=== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
=== Compose key not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
=== No tablet support ===<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&diff=78643Plasma/Wayland Known Significant Issues2017-10-11T19:50:46Z<p>Mgraesslin: Created page with "This page tracks the Wayland showstoppers through out the stack == General issues == === NVIDIA === The NVIDIA blob is not supported as it uses a custom EGL extension. It wou..."</p>
<hr />
<div>This page tracks the Wayland showstoppers through out the stack<br />
<br />
== General issues ==<br />
=== NVIDIA ===<br />
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not]<br />
<br />
=== QT_QPA_PLATFORM ===<br />
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.<br />
<br />
=== No remote support ===<br />
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.<br />
<br />
== Input ==<br />
=== No (wacom) Tablet support ===<br />
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.<br />
<br />
=== No XModmap ===<br />
We lack a functionality like XModmap to remap keys.<br />
<br />
== DRM ==<br />
<br />
=== Modes cannot be configured ===<br />
It's not yet possible to switch modes.<br />
<br />
=== Output cannot be rotated ===<br />
It's not yet possible to rotate the screen.<br />
<br />
== Plasma ==<br />
=== Virtual Desktops ===<br />
We don't have an API yet for virtual desktops, so pager is not working<br />
<br />
=== No window thumbnails ===<br />
We don't have an API yet for window thumbnails.<br />
<br />
=== No window move on empty area in breeze ===<br />
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.<br />
<br />
== Qt ==<br />
=== No animated cursors ===<br />
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]<br />
<br />
== Key repeat not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]<br />
<br />
== Compose key not working ===<br />
See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]<br />
<br />
== No tablet support ==<br />
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma&diff=78642Plasma2017-10-11T19:36:24Z<p>Mgraesslin: </p>
<hr />
<div>[[Image:plasma-logo-transparent.png]]<br />
[[File:Mascot konqi-base-plasma.png|thumbnail|right|Build Plasma with [[Konqi]]!]]<br />
<br />
== Documentation ==<br />
;[[Plasma/Vision | Vision Statement]]<br />
;[[Plasma/RepeatedDiscussions | Topics which come up again and again (RepeatedDiscussions)]]<br />
;[[Plasma/Vocabulary|Vocabulary]] (extra information in [[Plasma/Terminology|Terminology]], pages should be merged in)<br />
;[http://techbase.kde.org/Development/Tutorials/Plasma Tutorials] and [https://projects.kde.org/projects/kde/kdeexamples/repository/revisions/master/show/plasma examples]<br />
;[http://techbase.kde.org/KDE_System_Administration/PlasmaDesktopScripting Plasma Desktop Scripting]<br />
;[[Plasma/PlasmoidGuidelines|Guidelines for Plasma widgets creation]]<br />
;[[Plasma/Architecture|Plasma Architecture Overview]]<br />
;[[Plasma/QMLStyle|QML Style guide]]<br />
;[[Plasma/Package|Plasmoid and other Plasma plugin packaging]]<br />
;[[Plasma/DefensivePublication|Defensive publication of innovations and implementations]]<br />
;[[Plasma/ShareLikeConnect|Share Like Connect]]<br />
;[[Guidelines_and_HOWTOs/Build_from_source|Building and running Plasma 5]]<br />
;[[Plasma/Convergence_Overview|Convergence Overview]]<br />
<br />
== Developer Coordination ==<br />
<br />
===Integration Branch Tracking===<br />
;[[Plasma/IntegrationBranches/GeneralPolicy|General Policy]]<br />
<br />
=== Interface Standards and Research ===<br />
;[[Plasma/PURP|Plasma User Research Profile]]<br />
;[[Plasma/TheWaysOfThePlasma|The ways of the Plasma]]<br />
;[[Plasma/RecommendedReading|Recommended Reading on interaction design]]<br />
;[[Plasma/QMLStyle|QML Coding Style Guidelines]]<br />
<br />
=== Planning ===<br />
[[Plasma/BugtrackerCleanup]]<br />
<br />
==== Current ====<br />
;[http://techbase.kde.org/Schedules/Plasma_5 Plasma 5 Release Schedule]<br />
;[[Plasma/bugdays|Plasma Bug Days]]<br />
;[[Plasma/plasma-mobile-sorting|Organizing the contents of plasma-mobile repo]]<br />
;[[Plasma/Classroom|Classroom]]<br />
;[[Plasma/Education|Education Set Proposals]]<br />
;[[Plasma/Mobile|Plasma Mobile]]<br />
;[http://techbase.kde.org/Projects/Plasma/Plasma_Media_Center Plasma Media Center]<br />
;[[Plasma/Multiscreen|Multiscreen and PDV]]<br />
;[[Plasma/Activities|Activities]]<br />
;[[Plasma/TakingAdvantageOfCompositing|Plotting the plans for world domination via compositing]]<br />
;[[Plasma/Multihead|Multihead]]<br />
;[[Plasma/4.7-Kiosk| Kiosk]]<br />
<br />
====Plasma 5 ====<br />
;[[Plasma/PlasmaShellFeatures]]<br />
;[[Plasma/PortingQMLPlasmoids|Porting your Plasma QML code to Plasma 5]]<br />
;[[Plasma/PortingTolibplasma2|Documenting API changes in libplasma2 for porting things from libplasma1]]<br />
;[[Plasma/libplasma2|Planning for libplasma2, documenting issues with libplasma1]]<br />
;[[Plasma/libplasma2/API_Review|Api review of libplasma2 classes, method by method]]<br />
;[[Plasma/screenlocker|Screenlocker planning]]<br />
;[[Plasma/shellswitching|Platform state and kded module]]<br />
;[[Plasma/shellPackage|Package for shell definition]]<br />
;[[Plasma/lookAndFeelPackage|Package for shell look and feel]]<br />
;[https://userbase.kde.org/Plasma/Create_a_Look_and_Feel_Package How to create Look and Feel Package ]<br />
;[[Plasma/DesktopScripting|Plasma Shell Scripting]]<br />
;[[Plasma/StepBack|Step Back]]<br />
;[[Plasma/5.5 Errata|5.5 Errata]]<br />
;[[Plasma/Packages|Distro Packages]]<br />
;[[Plasma/Live Images|Live Images]]<br />
;[[Plasma/Docker Images|Docker Images]]<br />
;[[Plasma/Wayland Showstoppers|Wayland Showstoppers]]<br />
<br />
==== Ongoing ====<br />
;[[Plasma/Components|Coordination for work on Plasma QtComponents]]<br />
;[[Plasma/PlasmoidScripting|Plasmoid Javascript Roadmap and TODO]]<br />
;[[Plasma/Documentation|Documentation Coordination on Userbase]]<br />
;[[Plasma/PlasMate|PlasMate]]<br />
;[[Plasma/Tasks|Open Tasks List]]<br />
;[[Plasma/Bindings|Bindings TODOs]]<br />
;[[Plasma/Plasma UX improvement project|Plasma UX improvement project (Norwegian School of Information Technology)]]<br />
<br />
==== Past ====<br />
;[[Plasma/NewSystemTray|The new system tray protocol]]<br />
;[[Plasma/Polish|4.5 Polish]]<br />
;[[Plasma/Plasma-Netbook|Plasma-Netbook]]<br />
;[[Plasma/4.4-Kiosk|Kiosk Settings for 4.4]]<br />
;[[Plasma/Kiosk|Plasma::Kiosk]]<br />
;[[Plasma/JolieServices|Plasma::Service <-> Jolie Integration]]<br />
;[[Plasma/DBusInterface|Plasma (plasma-desktop) D-Bus interface planning]]<br />
;[[Plasma/2011|Development roadmap for 4.7 and 4.8]]<br />
;[[Plasma/Coinstallability|Coinstallability with Plasma 1]]<br />
;[[Plasma/PW2Todo|Plasma 5 Status & Todo]]<br />
<br />
== Individual Plasmoid Planning ==<br />
<br />
== Meetings ==<br />
Summaries and logs of scheduled plasma meetings can be found on the following pages:<br />
;[[Plasma/Affenfels|Affenfels Sprint]]<br />
;[[Plasma/Akademy2k14|Akademy 2014]]<br />
;[[Plasma/Tokamak6|Tokamak6]]<br />
;[[Plasma/Workspace Sprint|Workspace Sprint 2012]]<br />
;[[Plasma/Tokamak5|Tokamak5]]<br />
;[[Plasma/20101125|Nov 25, 2010, irc meeting to discuss the move to git]]<br />
;[[Plasma/20100912|Sept 12, 2010, irc meeting for 4.6 coordination]]<br />
;[[Plasma/20100715|July 15, 2010, irc meeting for 4.6 coordination]]<br />
;[[Plasma/Akademy2010|Akademy 2010]]<br />
;[[Plasma/Tokamak4|Tokamak4]]<br />
;[[Plasma/Tokamak3|Tokamak3]]<br />
;[[Plasma/Tokamak2|Tokamak2]]<br />
;[[Plasma/Akademy2k8|Akademy 2008]]<br />
;[[Plasma/Tokamak1|Tokamak1]]<br />
;[[Plasma/20090627|June 27, 2009, irc meeting for 4.4 coordination]]<br />
;[[Plasma/20080209|February 9, 2008]]<br />
;[[Plasma/20070207|February 21, 2007]]<br />
;[[Plasma/20100306|March 6 2010, irc meeting for 4.5 coordination]]<br />
<br />
=== Pages of Historical Interest ===<br />
;[[Plasma/ZUI|The ZUI. (Zooming User Interface)]]</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.11_Errata&diff=78619Plasma/5.11 Errata2017-10-05T18:04:14Z<p>Mgraesslin: </p>
<hr />
<div>Known issues in the Plasma 5.11 release.<br />
<br />
==KGlobalAccel==<br />
The KDE Framework KGlobalAccel includes a regression in its 5.38.0 release. Please use the 5.38.1 release.<br />
<br />
==Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* No support for primary selection (middle-click to paste)<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.19 lacks features or has bugs, we recommend XWayland 1.19<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* (Multi-)Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
* GTK: latest version requires newer xdg-shell version which is not yet supported<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.10_Errata&diff=76583Plasma/5.10 Errata2017-04-23T19:40:25Z<p>Mgraesslin: Initial import based on Plasma/5.9 errata</p>
<hr />
<div>Known issues in the Plasma 5.10 release.<br />
<br />
==Wayland==<br />
* '''Not functional with Qt 5.8.0''' (see [https://bugreports.qt.io/browse/QTBUG-58423 Qt Bug 58423])<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* No support for primary selection (middle-click to paste)<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.19 lacks features or has bugs, we recommend XWayland 1.19<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* (Multi-)Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
* GTK: latest version requires newer xdg-shell version which is not yet supported<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Affenfels&diff=76124Plasma/Affenfels2017-02-01T15:53:38Z<p>Mgraesslin: </p>
<hr />
<div>Plasma's 2017 Sprint, Stuttgart<br />
<br />
https://reimbursements.kde.org/events/25<br />
<br />
This Plasma sprint will be hosted at [http://www.vonaffenfels.de von Affenfels GmbH], Kronenstraße 40, 70174 Stuttgart, Germany. <br />
<br />
[https://notes.kde.org/p/plasma_affenfels Topics to discuss]<br />
<br />
Monday 6 February 2017 - Sunday 12 February 2017<br />
== Directions ==<br />
From Stuttgart Hauptbahnhof (main station) it is a less than 10 minutes walk to get there. <br />
<br />
The airport Flughafen Stuttgart (STR) has train connections to the main station (S2 and S3, look for the green circle with a white S in it), running roughly every 15 minutes.<br />
<br />
You can find public transport information here: http://en.vvs.de/home/ (they also have an app for Android (runs on BB10 just find and should on Sailfish too), iOS, Windows Phone)<br />
<br />
Ticket from airport to main station is 4,10 € (3 zones, child fare: 2,00 €)<br />
Ticket from the ibis budget hotel is 2,90 € (2 zones, child fare: 1,40 €) - you could buy a "4er Ticket" which allows to stamp for four rides. (10,60 € ie. 2,65 € per ride)<br />
<br />
There's currently Feinstaubalarm ("fein dust alert") in Stuttgart. When this is in effect you can pay child fare (Kinderticket) for buses, trams and trains within VVS (also applies to the S-Bahn from/to the airport and U Stadtbahn to the Ibis).<br />
<br />
Check the City of Stuttgart website for whether it's in effect: https://www.stuttgart.de/feinstaubalarm/ (orange = yes, pay child fare; green = no, "clean" air)<br />
<br />
Unfortunately, week pass is subscription-only, i.e. you can't just buy it at a ticket machine.<br />
<br />
Regional and long-distance trains arrive at Stuttgart Hauptbahnhof (oben) which is at the surface.<br />
U Stadtbahn (blue square with a "U") arrives Hauptbahnhof "Arnulf-Klett-Platz" which is one level underground<br />
S-Bahn (green circle with an "S") arrives Hauptbahnhof (tief) which is two levels underground<br />
<br />
== Accommodation ==<br />
Recommended accommodation I guess is [http://www.ibis.com/de/hotel-5441-ibis-budget-stuttgart-city-nord/index.shtml ibis budget Hotel Stuttgart Nord], roughly 350 € for a double room Monday through Sunday.<br />
<br />
There's a frequent Stadtbahn ("U Stadtbahn", look for the blue square with a white U in it) connection at "Maybachstraße" (line U6) going to Hauptbahnhof (main station) main station, taking less than 10 minutes.<br />
<br />
== Communications ==<br />
<br />
[https://telegram.me/joinchat/A36wiAoJgD9Tz9mP_9Q4LA Telegram Group]<br />
<br />
== People ==<br />
<br />
{| border="1"<br />
|-<br />
! Name <br />
! When?<br />
! Accommodation<br />
! Mobile<br />
! Transport<br />
! Dietary needs<br />
|-<br />
| Kai Uwe Broulik (host)<br />
| Mon, 6 Feb – Sun, 12 Feb<br />
| At Home ;)<br />
| +49 173 184 3 987<br />
| Car / Train<br />
| None<br />
|-<br />
| Jonathan Riddell<br />
| Sun 5 Feb – Sun, 12 Feb<br />
| Ibis Budget Nord<br />
| +44 7941 938912<br />
| Doing a road trip from FOSDEM with David E, arriving Sunday 5 late, leaving Sunday 12 early<br />
| <br />
|-<br />
| David Edmundson<br />
| Sun 5 Feb – Sun, 12 Feb<br />
| Ibis Budget Nord<br />
| +44 7481923182<br />
| Doing a road trip from FOSDEM with Jonathan R, arriving Sunday 5 late, leaving Sunday 12 early<br />
| <br />
|-<br />
| Marco Martin<br />
| Mon 6 Feb – Sun, 12 Feb<br />
| Ibis Budget Nord<br />
| +39 3492547165<br />
| Plane/Train<br />
| None<br />
|-<br />
| Sebastian Kügler<br />
| Mon 6 Feb – Sun, 12 Feb<br />
| Ibis Budget Nord<br />
| +31 48370928<br />
| Train<br />
| None<br />
|-<br />
| Aleix Pol<br />
| Mon 6 Feb – Fri, 10 Feb<br />
| Wherever you tell me<br />
| <br />
| Will be coming from FOSDEM, leaving by plane<br />
| None<br />
|-<br />
| Bhushan Shah<br />
| Mon 6 Feb - Sun 12 Feb<br />
| ibis Budget Nord<br />
|<br />
| Arrival train/Depart flight<br />
| Vegetarian<br />
|-<br />
| Roman Gilg<br />
| Mon 6 Feb - Sun 12 Feb<br />
| ibis Budget Nord<br />
|<br />
| Train or car (probably from Munich if someone is interested in ride sharing )<br />
| None<br />
|-<br />
| Ken Vermette<br />
| Mon 5-6 Feb - Sun 12 Feb<br />
| Novum Hotel Rieker Stuttgart Hauptbahnhof<br />
| +1-613-483-0556<br />
| Train, Plane, Pair of shoes<br />
| None<br />
|-<br />
| Dan Leinir Turthra Jensen<br />
| Mon 6 Feb - Sun 12 Feb<br />
| ibis Budget Nord<br />
| +44 7402 160 469<br />
| Plane<br />
| None<br />
|-<br />
| Martin Graesslin<br />
| Fri 10 Feb - Sat 11 Feb<br />
| at home<br />
| <br />
| Train<br />
| None<br />
|}</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.9_Errata&diff=76090Plasma/5.9 Errata2017-01-26T17:35:58Z<p>Mgraesslin: /* Wayland */</p>
<hr />
<div>Known issues in the Plasma 5.9 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 or Qt 5.7.1 instead.<br />
<br />
== Plasma Discover With Qt 5.7.1 ==<br />
<br />
Discover [https://bugs.kde.org/show_bug.cgi?id=375083 375083] crashes with Qt 5.7, use Qt 5.7.1 instead.<br />
<br />
== Intel GPUs ==<br />
We recommend the Xorg modesetting DDX for use with Intel hardware. This is the default in many distributions nowadays. Using the Intel Xorg DDX can result in various graphical glitches and freezes.<br />
<br />
==Wayland==<br />
* '''Not functional with Qt 5.8.0''' (see [https://bugreports.qt.io/browse/QTBUG-58423 Qt Bug 58423])<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* Multiple issues with Qt 5.8.0 (weird plasma behavior, missing window decorations) [https://bugreports.qt.io/browse/QTBUG-58423 Qt Bug 58423]<br />
* No support for primary selection (middle-click to paste)<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.19 lacks features or has bugs, we recommend XWayland 1.19<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* (Multi-)Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
* GTK: latest version requires newer xdg-shell version which is not yet supported<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.9_Errata&diff=75942Plasma/5.9 Errata2017-01-12T18:07:05Z<p>Mgraesslin: </p>
<hr />
<div>Known issues in the Plasma 5.9 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.7 instead.<br />
<br />
== Intel GPUs ==<br />
We recommend the Xorg modesettings ddx for use with Intel hardware. This is the default in many distributions nowadays. Using the Intel Xorg ddx can result in various graphical glitches and freezes.<br />
<br />
==Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* No support for primary selection (middle-click to paste)<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.19 lacks features or has bugs, we recommend XWayland 1.19<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* (Multi-)Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
* GTK: latest version requires newer xdg-shell version which is not yet supported<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.9_Errata&diff=75939Plasma/5.9 Errata2017-01-12T17:11:51Z<p>Mgraesslin: /* Wayland */</p>
<hr />
<div>Known issues in the Plasma 5.9 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.7 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by an [http://bugs.freedesktop.org/show_bug.cgi?id=86281 Intel driver bug]. A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
==Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* No support for primary selection (middle-click to paste)<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.19 lacks features or has bugs, we recommend XWayland 1.19<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* (Multi-)Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
* GTK: latest version requires newer xdg-shell version which is not yet supported<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Live_Images&diff=75748Plasma/Live Images2016-12-17T14:30:41Z<p>Mgraesslin: Remove Kubuntu due to dead link "This is the default web page for this server"</p>
<hr />
<div>Try and install Plasma from a live medium provided by several Linux distributions.<br />
<br />
== Chakra ==<br />
[https://chakralinux.org/ Chakra] is a GNU/Linux distribution with an emphasis on KDE and Qt that focuses on simplicity from a technical standpoint and free software. The downloadable ISO features a bootable environment that allows you to test the system before installing it.<br />
<br />
== Fedora ==<br />
The [https://spins.fedoraproject.org/kde/ Fedora KDE Spin] comes with Plasma. New minor Plasma versions are pushed as regular updates for Fedora installations but live media may contain a slightly older release (depending on Fedora’s release cycle).<br />
<br />
== KaOS ==<br />
* [https://kaosx.us/ KaOS] is a rolling, independent, built from scratch distribution, focused on Qt and KDE. It makes regular ISO releases available, so any (new) user is not confronted with a large or complicated first update.<br />
<br />
==KDE neon==<br />
KDE neon builds Frameworks and Plasma on a continuous integration system for its Developer Edition.<br />
<br />
You can use the stable version for builds from Plasma/5.x branches or unstable version for builds from master branches.<br />
The user edition has builds from released software.<br />
<br />
http://neon.kde.org/download<br />
<br />
== openSUSE ==<br />
* [https://en.opensuse.org/openSUSE:Tumbleweed_installation#LiveCDs.2FRescue_CD openSUSE Tumbleweed] ships the latest stable Plasma 5 release.<br />
* [https://en.opensuse.org/Portal:Leap openSUSE Leap] ships Plasma 5 but without live images.<br />
* [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Argon.x86_64*.iso Argon] and [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Krypton.*.iso Krypton] are openSUSE live images shipping the latest KDE software from git (unreleased) for Leap and Tumbleweed, respectively.<br />
* While Argon and Krypton ship unreleased software build from git, [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Krypton_*.iso Krypton stable] provides builds of the latest released version (Alpha, Beta)<br />
* [https://susestudio.com/search?order=date&per_page=50&q=KDE SUSE Studio Gallery] contains various appliances with KDE Plasma desktop.<br />
<br />
== Slackware ==<br />
[http://alien.slackbook.org/blog/tag/live/ Alien BOB] (Eric Hameleers) provides an installable [http://bear.alienbase.nl/mirrors/slackware-live/ Live image for Plasma 5] based on the development tree "slackware64-current". Login account/password are both "live". Use ''su'' or ''sudo'' to become root (using the "live" password).</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.8_Errata&diff=73982Plasma/5.8 Errata2016-09-13T07:33:43Z<p>Mgraesslin: /* Wayland */</p>
<hr />
<div>Known issues in the Plasma 5.8 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
== Bugs marked Critical ==<br />
<br />
The following bugs are marked critical<br />
<br />
* [https://bugs.kde.org/368078 Plasma-Task Manager and Wine issues]<br />
* [https://bugs.kde.org/361140 After resume from Suspend / Compositing and/or PlasmaShell Failure?]<br />
<br />
==Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* Touchpad configuration module not yet ported and crashes<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for primary selection (middle-click to paste)<br />
* No support for relative pointer events<br />
* No support for pointer confinement<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* X11 windows don't have an icon in the task bar<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.8_Errata&diff=73980Plasma/5.8 Errata2016-09-13T07:22:58Z<p>Mgraesslin: /* KWin Wayland */</p>
<hr />
<div>Known issues in the Plasma 5.8 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
== Bugs marked Critical ==<br />
<br />
The following bugs are marked critical<br />
<br />
* [https://bugs.kde.org/368078 Plasma-Task Manager and Wine issues]<br />
* [https://bugs.kde.org/361140 After resume from Suspend / Compositing and/or PlasmaShell Failure?]<br />
<br />
==Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* Touchpad configuration module not yet ported and crashes<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for primary selection (middle-click to paste)<br />
* No support for relative pointer events<br />
* No support for pointer confinement<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.8_Errata&diff=73979Plasma/5.8 Errata2016-09-13T07:22:32Z<p>Mgraesslin: /* KWin Wayland */</p>
<hr />
<div>Known issues in the Plasma 5.8 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
== Bugs marked Critical ==<br />
<br />
The following bugs are marked critical<br />
<br />
* [https://bugs.kde.org/368078 Plasma-Task Manager and Wine issues]<br />
* [https://bugs.kde.org/361140 After resume from Suspend / Compositing and/or PlasmaShell Failure?]<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* Touchpad configuration module not yet ported and crashes<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for primary selection (middle-click to paste)<br />
* No support for relative pointer events<br />
* No support for pointer confinement<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* No clipboard history (e.g. klipper and clipboard plasmoid)<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.8_Errata&diff=73978Plasma/5.8 Errata2016-09-12T19:47:30Z<p>Mgraesslin: /* Bugs marked Critical */</p>
<hr />
<div>Known issues in the Plasma 5.8 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
== Bugs marked Critical ==<br />
<br />
The following bugs are marked critical<br />
<br />
* [https://bugs.kde.org/368078 Plasma-Task Manager and Wine issues]<br />
* [https://bugs.kde.org/361140 After resume from Suspend / Compositing and/or PlasmaShell Failure?]<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* Touchpad configuration module not yet ported and crashes<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for primary selection (middle-click to paste)<br />
* No support for relative pointer events<br />
* No support for pointer confinement<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.8_Errata&diff=73977Plasma/5.8 Errata2016-09-12T19:43:42Z<p>Mgraesslin: /* Bugs marked Critical */</p>
<hr />
<div>Known issues in the Plasma 5.8 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
== Bugs marked Critical ==<br />
<br />
The following bugs are marked critical<br />
<br />
* [https://bugs.kde.org/368078 Plasma-Task Manager and Wine issues]<br />
* [https://bugs.kde.org/357800 Huge leak on X on Kate/Kwrite etc]<br />
* [https://bugs.kde.org/361140 After resume from Suspend / Compositing and/or PlasmaShell Failure?]<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* Touchpad configuration module not yet ported and crashes<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for primary selection (middle-click to paste)<br />
* No support for relative pointer events<br />
* No support for pointer confinement<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.8_Errata&diff=73976Plasma/5.8 Errata2016-09-12T19:40:08Z<p>Mgraesslin: /* Bugs marked Critical */</p>
<hr />
<div>Known issues in the Plasma 5.8 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
== Bugs marked Critical ==<br />
<br />
The following bugs are marked critical<br />
<br />
* [https://bugs.kde.org/368078 Plasma-Task Manager and Wine issues]<br />
* [https://bugs.kde.org/357800 Huge leak on X on Kate/Kwrite etc]<br />
* [https://bugs.kde.org/361140 After resume from Suspend / Compositing and/or PlasmaShell Failure?]<br />
* [https://bugs.kde.org/361211 Missing Letters]<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* Touchpad configuration module not yet ported and crashes<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for primary selection (middle-click to paste)<br />
* No support for relative pointer events<br />
* No support for pointer confinement<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.7_Errata&diff=73975Plasma/5.7 Errata2016-09-12T19:38:32Z<p>Mgraesslin: Undo revision 73971 by Mgraesslin (talk)</p>
<hr />
<div>Known issues in the Plasma 5.6 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No support for xdg_shell which means GTK+ applications cannot be started on Wayland<br />
* No Copy/Paste from X11 to Wayland windows and vice versa<br />
* No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
<br />
== Tech Previews ==<br />
* Plasma Media Center is in tech preview and misses features compared to Plasma Media Center 1<br />
* Breeze Plymouth Theme is in tech preview<br />
* Breeze Grub Theme is in tech preview<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.7_Errata&diff=73974Plasma/5.7 Errata2016-09-12T19:38:14Z<p>Mgraesslin: Undo revision 73972 by Mgraesslin (talk)</p>
<hr />
<div>Known issues in the Plasma 5.6 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
<br />
== Tech Previews ==<br />
* Breeze Plymouth Theme is in tech preview<br />
* Breeze Grub Theme is in tech preview<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.8_Errata&diff=73973Plasma/5.8 Errata2016-09-12T19:37:16Z<p>Mgraesslin: </p>
<hr />
<div>Known issues in the Plasma 5.8 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
== Bugs marked Critical ==<br />
<br />
The following bugs are marked critical<br />
<br />
* [https://bugs.kde.org/368078 Plasma-Task Manager and Wine issues]<br />
* [https://bugs.kde.org/357800 Huge leak on X on Kate/Kwrite etc]<br />
* [https://bugs.kde.org/361140 After resume from Suspend / Compositing and/or PlasmaShell Failure?]<br />
* [https://bugs.kde.org/361211 Missing Letters]<br />
* [https://bugs.kde.org/364709 Activating desktop grid sometimes freezes X11]<br />
<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* Touchpad configuration module not yet ported and crashes<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for primary selection (middle-click to paste)<br />
* No support for relative pointer events<br />
* No support for pointer confinement<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.7_Errata&diff=73972Plasma/5.7 Errata2016-09-12T14:20:26Z<p>Mgraesslin: /* KWin Wayland */</p>
<hr />
<div>Known issues in the Plasma 5.6 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* Touchpad configuration module not yet ported and crashes<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Support for per-screen DPI is missing<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for primary selection (middle-click to paste)<br />
* No support for relative pointer events<br />
* No support for pointer confinement<br />
* No support for tablet devices (e.g. wacom tablets)<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
* QtWebEngine crashes when used on Wayland [https://bugreports.qt.io/browse/QTBUG-55384 Qt Bug 55384]<br />
* QtWayland: No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* QtWayland: Dropdown windows closes on key presses [https://bugreports.qt.io/browse/QTBUG-55403 Qt Bug 55403]<br />
* QtWayland: Missing compose key support [https://bugreports.qt.io/browse/QTBUG-54792 Qt Bug 54792]<br />
* QtWayland: Key repeat settings ignored [https://bugreports.qt.io/browse/QTBUG-55615 Qt Bug 55615]<br />
* QtWayland: Sub-menus may be placed incorrectly [https://bugreports.qt.io/browse/QTBUG-50458 Qt Bug 50458]<br />
* GTK: windows don't have a minimize and maximize button<br />
* GTK: windows are incorrectly placed<br />
<br />
== Tech Previews ==<br />
* Breeze Plymouth Theme is in tech preview<br />
* Breeze Grub Theme is in tech preview<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.7_Errata&diff=73971Plasma/5.7 Errata2016-09-12T14:08:36Z<p>Mgraesslin: </p>
<hr />
<div>Known issues in the Plasma 5.6 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
=== Modesettings ===<br />
To circumvent the issues mentioned above it's also possible to switch the Xorg ddx driver from Intel to modesettings. Many distributions do so by default nowadays.<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No Drag and Drop from X11 to Wayland windows and vice versa<br />
* Pasting only works as long as not copied from same window (fixed in Frameworks 5.27)<br />
* No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug. Recommendation is XWayland 1.18.4 or 1.19<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
<br />
== Tech Previews ==<br />
* Breeze Plymouth Theme is in tech preview<br />
* Breeze Grub Theme is in tech preview<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=KWin/Environment_Variables&diff=73353KWin/Environment Variables2016-08-18T05:53:02Z<p>Mgraesslin: </p>
<hr />
<div>= Available Environment Variables =<br />
KWin supports a number of environment variables to overwrite some settings or checks. The following variables are supported:<br />
<br />
== KWIN_COMPOSE ==<br />
The environment variable '''KWIN_COMPOSE''' enforces a compositing backend or forces compositing completely off. The following values are supported:<br />
* ''O'': OpenGL backend (either OpenGL 1, OpenGL 2 or OpenGL ES 2.0)<br />
* ''O1'': OpenGL 1 backend (only 4.x)<br />
* ''O2'': OpenGL 2 backend<br />
* ''O2ES'': OpenGL ES 2 backend (since 5.5)<br />
* ''X'': XRender backend (only X11)<br />
* ''Q'': QPainter backend (only Wayland)<br />
* ''N'': No Compositing (only X11)<br />
<br />
== KWIN_NVIDIA_HACK ==<br />
By default KWin uses an NVIDIA specific hack to set '''__GL_YIELD''' to ''NOTHING''. By setting "KWIN_NVIDIA_HACK" to "0" this behavior can be disabled.<br />
This environment variable is uneffective since at least 4.8.<br />
<br />
== KWIN_DIRECT_GL ==<br />
KWin determines whether '''LIBGL_ALWAYS_INDIRECT''' has to be set by an external helper application and a driver whitelist of the drivers known to perform well with direct rendering. By setting the environment variable '''KWIN_DIRECT_GL''' to ''1'' the checks are not performed and '''LIBGL_ALWAYS_INDIRECT''' is not set.<br />
<br />
This environment variable is only supported in 4.x.<br />
<br />
== KWIN_GL_DEBUG ==<br />
By setting '''KWIN_GL_DEBUG''' to ''1'' the OpenGL rendering can be debugged visually. All geometries which are rendered are overlayed by a wireframe. The wireframe is not available in OpenGL ES 2.0. The environment variable is supported since 4.7.<br />
<br />
== KWIN_FORCE_LANCZOS ==<br />
The lanczos filter is controlled by the scale method in the advanced compositing settings and a blacklist of drivers known to break with this filter. The setting and the blacklist can be overruled by setting '''KWIN_FORCE_LANCZOS''' to ''1''. This environment variable is supported since 4.8.<br />
<br />
== KWIN_OPENGL_INTERFACE ==<br />
By setting '''KWIN_OPENGL_INTERFACE''' to ''egl'' the OpenGL based compositor uses the EGL platform interface instead of the GLX. This environment variable is supported since 4.10.<br />
<br />
== KWIN_USE_BUFFER_AGE ==<br />
More recent GL drivers allow to re-use the (n-)last frontbuffer as current backbuffer, what means that only a fraction of the screen has to be painted which was really changed. This adds quite some performance and is enabled by default (if your driver supports it ("glxinfo | grep GLX_EXT_buffer_age", needs to be matched at least twice!)<br />
It may cause artifacts, so you can try to disable it:<br />
* ''0'': disabled<br />
<br />
== KWIN_EXPLICIT_SYNC ==<br />
The GL_EXT_x11_sync_object extension (check "glxinfo | grep GL_EXT_x11_sync_object", needs to be matched at least twice!) allows to synchronize X11 and OpenGL command streams (guarantee X11 "foo" happend before GL "bar" is executed)<br />
If supported it's enabled by default but is prone to cause "lockups", so you might try to disable it:<br />
* ''0'': disabled<br />
<br />
== KWIN_TRIPLE_BUFFER ==<br />
KWin tries to detect whether triple buffering is available by measuring the invocation of glSwapBuffers (during the initial frames) - this is heuristic and can result in a wrong assumption of the condition, thus the wrong swapping strategy.<br />
* ''0'': override detection as unavailable<br />
* ''1'': override detection as available<br />
<br />
NOTICE: this does NOT enable triple buffering in the driver!<br />
Forcing KWin into the wrong strategy will usually cause inferior performance ("laggy" behavior)!<br />
<br />
UNDOCUMENTED: as of end 2015, the binary nvidia driver does '''not''' block on doublebuffered swapping, thus it is "safe" to make kwin falsely believe this is a triple buffering system. The behavior may change anytime with a driver update.<br />
See https://bugs.kde.org/show_bug.cgi?id=346275<br />
<br />
== KWIN_USE_INTEL_SWAP_EVENT ==<br />
This is a fairly new feature of the intel driver. It's only available with Qt >= 5.4<br />
As it caused major issues (freeze, compositing simply never updates) it's currently disabled by default and must be explicitly enabled (on your own risk) - see https://bugs.kde.org/show_bug.cgi?id=342582<br />
* ''1'': enforce usage<br />
<br />
== KWIN_PERSISTENT_VBO ==<br />
Performance feature that requires GL_ARB_sync and GL_ARB_buffer_storage extension to use a ring buffer instead of reallocating vertex buffer objects.<br />
* "0" explicitly disable it<br />
<br />
== KWIN_DBUS_SERVICE_SUFFIX ==<br />
Suffix for the DBus-Service name "org.kde.KWin". If set, the name will be changed to "org.kde.KWin.${KWIN_DBUS_SERVICE_SUFFIX}". This environment variable is supported since 5.2. In a multi-head environment on the non-primary heads a ".head-${number}" will be appended, so overall e.g. "org.kde.KWin.${KWIN_DBUS_SERVICE_SUFFIX}.head-1".<br />
<br />
== KWIN_NO_XI2 ==<br />
Set to disables X11 XInput2 integration. This environment variable is supported since 5.6.<br />
<br />
== KWIN_EFFECTS_FORCE_ANIMATIONS ==<br />
Allows to force override whether animations should be forced on or off. The recommendation of the compositor will be override. This environment variable is supported since 5.8.<br />
* "0" explicitly disable animations<br />
* "1" explicitly enable animations<br />
<br />
== KWIN_XKB_DEFAULT_KEYMAP ==<br />
This environment variable forces the xkb integration on Wayland to use a default keymap instead of using the configured one. Mostly required for testing. This environment variable is supported since 5.8.<br />
<br />
----<br />
----<br />
<br />
= Related, maybe usable variables =<br />
<br />
== __GL_YIELD ==<br />
Not yielding can cause quite some CPU overhead, so on systems that do NOT provide triple buffering, V'Sync will be turned off except for __GL_YIELD=USLEEP<br />
* "": By default, OpenGL will call sched_yield() to yield. This can cause the process to be scheduled out for a relatively long period of time or never yield (sched_yield can easily end up being NOOP)<br />
* "USLEEP": OpenGL will call usleep(0) to yield.<br />
* "NOTHING": OpenGL will never yield.<br />
<br />
== __GL_SYNC_DISPLAY_DEVICE ==<br />
Consumer GPUs can only sync to one monitor. This variable allows to control which that will be (default is primary)<br />
Lookup valid identifiers (eg. LVDS1, HDMI-0 or DVI-I-1) with eg. "xrandr -q"<br />
<br />
== LIBGL_DEBUG ==<br />
* ''1'': enable libgl debug messages<br />
<br />
== XLIB_SKIP_ARGB_VISUALS ==<br />
This isn't relevant for KWin, but maybe some clients. You have to set it for such client process (eg. "XLIB_SKIP_ARGB_VISUALS=1 xmms")<br />
It prevents them from using ARGB windows (ie. partial transparency) - especially gtk-1 (the original gnome toolkit) used them "wrongly"<br />
* ''1'': enforce 24bit windows<br />
<br />
= Set variables at session start =<br />
* Create a script file "kwin_env.sh" with the variables you wish to set .<br />
<br />
----<br />
<br />
<nowiki><br />
#!/bin/sh<br />
</nowiki><br />
<br />
export FOO=bar<br />
<br />
export BAR=foo<br />
<br />
----<br />
<br />
* Make the script executable (file properties or "chmod +x kwin_vars.sh")<br />
* Place the script in a sourced path <br />
== KDE SC 4 ==<br />
~/.kde/env/<br />
This is ~/.kde4/env/ on some distributions - compare the output of "kde4-config --path config"<br />
== KF 5 ==<br />
~/.config/plasma-workspace/env/</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Live_Images&diff=72541Plasma/Live Images2016-07-05T12:48:46Z<p>Mgraesslin: Remove Altlinux - I didn't understand how I can download a Plasma iso there. It says somewhere "KDE5" under experimetnal but link takes back to this page. Weird. If I as an upstream dev doesn't understand this, users won't. Please get the download easy.</p>
<hr />
<div>Try and install Plasma from a live CD provided by several Linux distributions.<br />
<br />
= Plasma 5.7 =<br />
<br />
* [http://files.kde.org/neon/images/neon-useredition/current/ KDE neon User Edition]<br />
<br />
= In General =<br />
== Fedora ==<br />
The [https://spins.fedoraproject.org/kde/ Fedora KDE Spin] comes with Plasma. New minor Plasma versions are pushed as regular updates for Fedora installations but live media may contain a slightly older release (depending on Fedora’s release cycle).<br />
<br />
==KDE neon==<br />
KDE neon builds Frameworks and Plasma on a continuous integration system for its Developer Edition.<br />
<br />
You can use the stable version for builds from Plasma/5.x branches or unstable version for builds from master branches.<br />
The user edition has builds from released software.<br />
<br />
http://neon.kde.org/download<br />
<br />
== Kubuntu ==<br />
* [http://wire.kubuntu.org/?p=954 Kubuntu 16.04] supports Plasma 5.6.5 through Backports.<br />
<br />
== openSUSE ==<br />
* [https://en.opensuse.org/openSUSE:Tumbleweed_installation#LiveCDs.2FRescue_CD openSUSE Tumbleweed] ships the latest stable Plasma 5 release.<br />
* [https://en.opensuse.org/Portal:Leap openSUSE Leap] ships Plasma 5 but without live images.<br />
* [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Argon.x86_64*.iso Argon] and [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Krypton.x86_64*.iso Krypton] are openSUSE live images shipping the latest KDE software from git (unreleased) for Tumbleweed and Leap, respectively.<br />
* [https://susestudio.com/search?order=date&per_page=50&q=KDE SUSE Studio Gallery] contains various appliances with KDE Plasma desktop.<br />
<br />
== Slackware ==<br />
[http://alien.slackbook.org/blog/tag/live/ Alien BOB] (Eric Hameleers) provides an installable [http://bear.alienbase.nl/mirrors/slackware-live/ Live image for Plasma 5] based on the development tree "slackware64-current". Login account/password are both "live". Use ''su'' or ''sudo'' to become root (using the "live" password).</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Live_Images&diff=72540Plasma/Live Images2016-07-05T12:46:11Z<p>Mgraesslin: Remove KubuntuCI - link is dead</p>
<hr />
<div>Try and install Plasma from a live CD provided by several Linux distributions.<br />
<br />
= Plasma 5.7 =<br />
<br />
* [http://files.kde.org/neon/images/neon-useredition/current/ KDE neon User Edition]<br />
<br />
= In General =<br />
== Fedora ==<br />
The [https://spins.fedoraproject.org/kde/ Fedora KDE Spin] comes with Plasma. New minor Plasma versions are pushed as regular updates for Fedora installations but live media may contain a slightly older release (depending on Fedora’s release cycle).<br />
<br />
==KDE neon==<br />
KDE neon builds Frameworks and Plasma on a continuous integration system for its Developer Edition.<br />
<br />
You can use the stable version for builds from Plasma/5.x branches or unstable version for builds from master branches.<br />
The user edition has builds from released software.<br />
<br />
http://neon.kde.org/download<br />
<br />
== Kubuntu ==<br />
* [http://wire.kubuntu.org/?p=954 Kubuntu 16.04] supports Plasma 5.6.5 through Backports.<br />
<br />
== openSUSE ==<br />
* [https://en.opensuse.org/openSUSE:Tumbleweed_installation#LiveCDs.2FRescue_CD openSUSE Tumbleweed] ships the latest stable Plasma 5 release.<br />
* [https://en.opensuse.org/Portal:Leap openSUSE Leap] ships Plasma 5 but without live images.<br />
* [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Argon.x86_64*.iso Argon] and [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Krypton.x86_64*.iso Krypton] are openSUSE live images shipping the latest KDE software from git (unreleased) for Tumbleweed and Leap, respectively.<br />
* [https://susestudio.com/search?order=date&per_page=50&q=KDE SUSE Studio Gallery] contains various appliances with KDE Plasma desktop.<br />
<br />
== ALT Linux ==<br />
* Weekly updated [http://en.altlinux.org/regular Regular builds] include both KDE4 and KDE5 ones (installable LiveCDs built upon our unstable development branch dubbed Sisyphus).<br />
<br />
<br />
== Slackware ==<br />
[http://alien.slackbook.org/blog/tag/live/ Alien BOB] (Eric Hameleers) provides an installable [http://bear.alienbase.nl/mirrors/slackware-live/ Live image for Plasma 5] based on the development tree "slackware64-current". Login account/password are both "live". Use ''su'' or ''sudo'' to become root (using the "live" password).</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Live_Images&diff=72539Plasma/Live Images2016-07-05T12:43:06Z<p>Mgraesslin: Remove Alt linux Plasma 4 as it's Plasma 4</p>
<hr />
<div>Try and install Plasma from a live CD provided by several Linux distributions.<br />
<br />
= Plasma 5.7 =<br />
<br />
* [http://files.kde.org/neon/images/neon-useredition/current/ KDE neon User Edition]<br />
<br />
= In General =<br />
== Fedora ==<br />
The [https://spins.fedoraproject.org/kde/ Fedora KDE Spin] comes with Plasma. New minor Plasma versions are pushed as regular updates for Fedora installations but live media may contain a slightly older release (depending on Fedora’s release cycle).<br />
<br />
==KDE neon==<br />
KDE neon builds Frameworks and Plasma on a continuous integration system for its Developer Edition.<br />
<br />
You can use the stable version for builds from Plasma/5.x branches or unstable version for builds from master branches.<br />
The user edition has builds from released software.<br />
<br />
http://neon.kde.org/download<br />
<br />
== Kubuntu ==<br />
* [http://wire.kubuntu.org/?p=954 Kubuntu 16.04] supports Plasma 5.6.5 through Backports.<br />
* [http://files.kde.org/snapshots/ Kubuntu CI] is a Kubuntu image plus the [https://community.kde.org/Kubuntu/PPAs#Kubuntu_Continuous_Integration_.28CI.29 Kubuntu CI packages] using the latest software from Frameworks, Plasma and Applications Git.<br />
<br />
== openSUSE ==<br />
* [https://en.opensuse.org/openSUSE:Tumbleweed_installation#LiveCDs.2FRescue_CD openSUSE Tumbleweed] ships the latest stable Plasma 5 release.<br />
* [https://en.opensuse.org/Portal:Leap openSUSE Leap] ships Plasma 5 but without live images.<br />
* [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Argon.x86_64*.iso Argon] and [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Krypton.x86_64*.iso Krypton] are openSUSE live images shipping the latest KDE software from git (unreleased) for Tumbleweed and Leap, respectively.<br />
* [https://susestudio.com/search?order=date&per_page=50&q=KDE SUSE Studio Gallery] contains various appliances with KDE Plasma desktop.<br />
<br />
== ALT Linux ==<br />
* Weekly updated [http://en.altlinux.org/regular Regular builds] include both KDE4 and KDE5 ones (installable LiveCDs built upon our unstable development branch dubbed Sisyphus).<br />
<br />
<br />
== Slackware ==<br />
[http://alien.slackbook.org/blog/tag/live/ Alien BOB] (Eric Hameleers) provides an installable [http://bear.alienbase.nl/mirrors/slackware-live/ Live image for Plasma 5] based on the development tree "slackware64-current". Login account/password are both "live". Use ''su'' or ''sudo'' to become root (using the "live" password).</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Live_Images&diff=72538Plasma/Live Images2016-07-05T12:42:24Z<p>Mgraesslin: remove opensuse 13.2 as it's Plasma 4</p>
<hr />
<div>Try and install Plasma from a live CD provided by several Linux distributions.<br />
<br />
= Plasma 5.7 =<br />
<br />
* [http://files.kde.org/neon/images/neon-useredition/current/ KDE neon User Edition]<br />
<br />
= In General =<br />
== Fedora ==<br />
The [https://spins.fedoraproject.org/kde/ Fedora KDE Spin] comes with Plasma. New minor Plasma versions are pushed as regular updates for Fedora installations but live media may contain a slightly older release (depending on Fedora’s release cycle).<br />
<br />
==KDE neon==<br />
KDE neon builds Frameworks and Plasma on a continuous integration system for its Developer Edition.<br />
<br />
You can use the stable version for builds from Plasma/5.x branches or unstable version for builds from master branches.<br />
The user edition has builds from released software.<br />
<br />
http://neon.kde.org/download<br />
<br />
== Kubuntu ==<br />
* [http://wire.kubuntu.org/?p=954 Kubuntu 16.04] supports Plasma 5.6.5 through Backports.<br />
* [http://files.kde.org/snapshots/ Kubuntu CI] is a Kubuntu image plus the [https://community.kde.org/Kubuntu/PPAs#Kubuntu_Continuous_Integration_.28CI.29 Kubuntu CI packages] using the latest software from Frameworks, Plasma and Applications Git.<br />
<br />
== openSUSE ==<br />
* [https://en.opensuse.org/openSUSE:Tumbleweed_installation#LiveCDs.2FRescue_CD openSUSE Tumbleweed] ships the latest stable Plasma 5 release.<br />
* [https://en.opensuse.org/Portal:Leap openSUSE Leap] ships Plasma 5 but without live images.<br />
* [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Argon.x86_64*.iso Argon] and [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Krypton.x86_64*.iso Krypton] are openSUSE live images shipping the latest KDE software from git (unreleased) for Tumbleweed and Leap, respectively.<br />
* [https://susestudio.com/search?order=date&per_page=50&q=KDE SUSE Studio Gallery] contains various appliances with KDE Plasma desktop.<br />
<br />
== ALT Linux ==<br />
* Plasma 4 is included with ALT Linux [http://linux.softpedia.com/get/System/Operating-Systems/Linux-Distributions/ALT-Linux-KDesktop-30571.shtml KDesktop] official distribution since [http://distrowatch.com/?newsid=05742 5.0];<br />
* Weekly updated [http://en.altlinux.org/regular Regular builds] include both KDE4 and KDE5 ones (installable LiveCDs built upon our unstable development branch dubbed Sisyphus).<br />
<br />
<br />
== Slackware ==<br />
[http://alien.slackbook.org/blog/tag/live/ Alien BOB] (Eric Hameleers) provides an installable [http://bear.alienbase.nl/mirrors/slackware-live/ Live image for Plasma 5] based on the development tree "slackware64-current". Login account/password are both "live". Use ''su'' or ''sudo'' to become root (using the "live" password).</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Live_Images&diff=72537Plasma/Live Images2016-07-05T12:41:58Z<p>Mgraesslin: Remove Kubuntu 15.04 and 15.10 because EOL</p>
<hr />
<div>Try and install Plasma from a live CD provided by several Linux distributions.<br />
<br />
= Plasma 5.7 =<br />
<br />
* [http://files.kde.org/neon/images/neon-useredition/current/ KDE neon User Edition]<br />
<br />
= In General =<br />
== Fedora ==<br />
The [https://spins.fedoraproject.org/kde/ Fedora KDE Spin] comes with Plasma. New minor Plasma versions are pushed as regular updates for Fedora installations but live media may contain a slightly older release (depending on Fedora’s release cycle).<br />
<br />
==KDE neon==<br />
KDE neon builds Frameworks and Plasma on a continuous integration system for its Developer Edition.<br />
<br />
You can use the stable version for builds from Plasma/5.x branches or unstable version for builds from master branches.<br />
The user edition has builds from released software.<br />
<br />
http://neon.kde.org/download<br />
<br />
== Kubuntu ==<br />
* [http://wire.kubuntu.org/?p=954 Kubuntu 16.04] supports Plasma 5.6.5 through Backports.<br />
* [http://files.kde.org/snapshots/ Kubuntu CI] is a Kubuntu image plus the [https://community.kde.org/Kubuntu/PPAs#Kubuntu_Continuous_Integration_.28CI.29 Kubuntu CI packages] using the latest software from Frameworks, Plasma and Applications Git.<br />
<br />
== openSUSE ==<br />
* Plasma 4 is included with [https://en.opensuse.org/Portal:13.2 openSUSE 13.2]<br />
* [https://en.opensuse.org/openSUSE:Tumbleweed_installation#LiveCDs.2FRescue_CD openSUSE Tumbleweed] ships the latest stable Plasma 5 release.<br />
* [https://en.opensuse.org/Portal:Leap openSUSE Leap] ships Plasma 5 but without live images.<br />
* [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Argon.x86_64*.iso Argon] and [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Krypton.x86_64*.iso Krypton] are openSUSE live images shipping the latest KDE software from git (unreleased) for Tumbleweed and Leap, respectively.<br />
* [https://susestudio.com/search?order=date&per_page=50&q=KDE SUSE Studio Gallery] contains various appliances with KDE Plasma desktop.<br />
<br />
== ALT Linux ==<br />
* Plasma 4 is included with ALT Linux [http://linux.softpedia.com/get/System/Operating-Systems/Linux-Distributions/ALT-Linux-KDesktop-30571.shtml KDesktop] official distribution since [http://distrowatch.com/?newsid=05742 5.0];<br />
* Weekly updated [http://en.altlinux.org/regular Regular builds] include both KDE4 and KDE5 ones (installable LiveCDs built upon our unstable development branch dubbed Sisyphus).<br />
<br />
<br />
== Slackware ==<br />
[http://alien.slackbook.org/blog/tag/live/ Alien BOB] (Eric Hameleers) provides an installable [http://bear.alienbase.nl/mirrors/slackware-live/ Live image for Plasma 5] based on the development tree "slackware64-current". Login account/password are both "live". Use ''su'' or ''sudo'' to become root (using the "live" password).</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/Live_Images&diff=72531Plasma/Live Images2016-07-05T06:22:47Z<p>Mgraesslin: </p>
<hr />
<div>Try and install Plasma from a live CD provided by several Linux distributions.<br />
<br />
= Plasma 5.7 =<br />
<br />
= In General =<br />
== Fedora ==<br />
The [https://spins.fedoraproject.org/kde/ Fedora KDE Spin] comes with Plasma. New minor Plasma versions are pushed as regular updates for Fedora installations but live media may contain a slightly older release (depending on Fedora’s release cycle).<br />
<br />
==KDE neon==<br />
KDE neon builds Frameworks and Plasma on a continuous integration system for its Developer Edition.<br />
<br />
You can use the stable version for builds from Plasma/5.x branches or unstable version for builds from master branches.<br />
The user edition has builds from released software.<br />
<br />
http://neon.kde.org/download<br />
<br />
== Kubuntu ==<br />
* [http://cdimage.ubuntu.com/kubuntu/releases/vivid/ Kubuntu 15.04] was the first Kubuntu release to offer Plasma 5 as a default.<br />
* [http://www.kubuntu.org/news/plasma-5-5-3-and-frameworks-5-18-0-backported-to-kubuntu-15-10/ Kubuntu 15.10] supported Plasma 5.5.3 through Backports.<br />
* [http://wire.kubuntu.org/?p=954 Kubuntu 16.04] supports Plasma 5.6.5 through Backports.<br />
* [http://files.kde.org/snapshots/ Kubuntu CI] is a Kubuntu image plus the [https://community.kde.org/Kubuntu/PPAs#Kubuntu_Continuous_Integration_.28CI.29 Kubuntu CI packages] using the latest software from Frameworks, Plasma and Applications Git.<br />
<br />
== openSUSE ==<br />
* Plasma 4 is included with [https://en.opensuse.org/Portal:13.2 openSUSE 13.2]<br />
* [https://en.opensuse.org/openSUSE:Tumbleweed_installation#LiveCDs.2FRescue_CD openSUSE Tumbleweed] ships the latest stable Plasma 5 release.<br />
* [https://en.opensuse.org/Portal:Leap openSUSE Leap] ships Plasma 5 but without live images.<br />
* [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Argon.x86_64*.iso Argon] and [http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=openSUSE_Krypton.x86_64*.iso Krypton] are openSUSE live images shipping the latest KDE software from git (unreleased) for Tumbleweed and Leap, respectively.<br />
* [https://susestudio.com/search?order=date&per_page=50&q=KDE SUSE Studio Gallery] contains various appliances with KDE Plasma desktop.<br />
<br />
== ALT Linux ==<br />
* Plasma 4 is included with ALT Linux [http://linux.softpedia.com/get/System/Operating-Systems/Linux-Distributions/ALT-Linux-KDesktop-30571.shtml KDesktop] official distribution since [http://distrowatch.com/?newsid=05742 5.0];<br />
* Weekly updated [http://en.altlinux.org/regular Regular builds] include both KDE4 and KDE5 ones (installable LiveCDs built upon our unstable development branch dubbed Sisyphus).<br />
<br />
<br />
== Slackware ==<br />
[http://alien.slackbook.org/blog/tag/live/ Alien BOB] (Eric Hameleers) provides an installable [http://bear.alienbase.nl/mirrors/slackware-live/ Live image for Plasma 5] based on the development tree "slackware64-current". Login account/password are both "live". Use ''su'' or ''sudo'' to become root (using the "live" password).</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.7_Errata&diff=72256Plasma/5.7 Errata2016-06-15T09:35:58Z<p>Mgraesslin: </p>
<hr />
<div>Known issues in the Plasma 5.6 release.<br />
<br />
== Freezes Using Qt 5.6.0 ==<br />
<br />
*http://bugreports.qt.io/browse/QTBUG-51676<br />
*https://bugs.kde.org/show_bug.cgi?id=359611<br />
When using Qt 5.6.0 Plasma loads itself incompletely and with long delays. Deadlocks occur in kded5.<br />
Use Qt 5.6.1 instead.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a ([http://bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug]). A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet)<br />
* No support for xdg_shell which means GTK+ applications cannot be started on Wayland<br />
* No Copy/Paste from X11 to Wayland windows and vice versa<br />
* No support for animated mouse cursors [http://bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181]<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
<br />
== Tech Previews ==<br />
* Plasma Media Center is in tech preview and misses features compared to Plasma Media Center 1<br />
* Breeze Plymouth Theme is in tech preview<br />
* Breeze Grub Theme is in tech preview<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=KWin/Wayland&diff=66187KWin/Wayland2016-04-28T06:00:05Z<p>Mgraesslin: /* Starting a nested KWin */</p>
<hr />
<div>= What is Wayland? =<br />
[http://wayland.freedesktop.org Wayland] is a small display server protocol and IPC library which is considered to have the chance to replace X11 as primary windowing system. But Wayland is not a direct successor of X and does not follow the design of X. The display server is directly moved into the Compositor (that is KWin) and clients connect to this server through a Unix socket.<br />
<br />
= Why Plasma needs Wayland? =<br />
<br />
X has some serious issues and is rather old. The protocol is designed for the usecases three decades ago. Over the last years more and more functionality has been moved from X either into the kernel or into the compositors. The X server is more or less only a proxy between kernel, compositor and the X clients.<br />
<br />
Today the compositor does everything the X server used to do. There are some remaining features not yet moved into the compositor (e.g. input handling) but those would make most sense in the compositor. The best situation would be to let the compositor directly work together with the kernel for rendering and input handling and manage the clients directly, which means to remove the Proxy. This is what Wayland is about. More reasons for Wayland in the [http://wayland.freedesktop.org/faq.html FAQ].<br />
<br />
In Plasma we need Wayland support as we are hitting the limitations of X all the time. Wayland will simplify our architecture and allow us to composite the screen in the way we consider as most useful.<br />
<br />
= Wayland Support in Plasma =<br />
<br />
Wayland support in the KDE Plasma Workspaces is in a tech-preview state. The workspaces have been developed for X11 and much functionality relies on X11. To be able to make proper use of Wayland these bits have to be rewritten.<br />
<br />
The most complex task is to implement Wayland support in KWin, KDE Plasma's Compositor and Window Manager. Since 5.4 KWin is able to manage Wayland clients and this allows to start a Plasma session on Wayland.<br />
<br />
= Why not a new Compositor? =<br />
<br />
Given that KWin was designed as a X11 Window Manager and later as a X11 compositor the question is valid, why not to implement a new Wayland compositor from scratch. Most parts of KWin are X11 independent. E.g. the Desktop Effect system is able to integrate Wayland clients without any change, the same is true for Window Decorations and other parts.<br />
<br />
Another reason is that the KWin development team does not have the manpower to maintain an independent X11 window manager and a Wayland compositor. Starting a new Wayland compositor would mean to stop the work on the X11 window manager, which would be a bad move as we cannot know yet whether Wayland will succeed and will be supported on all hardware. Also in future KDE will have to provide an X11 window manager.<br />
<br />
KWin is known as one of the most feature complete and most stable window managers. More than a decade of development effort has gone into this Window Manager. Reaching feature parity in a new Wayland compositor seems hardly possible if rewritten from scratch.<br />
<br />
Writing a new Wayland Compositor would require to rewrite the complete X11 workspace in one go. This includes not only the Window Manager, but also parts of Plasma, Screen Locker and many, many more. This would take a long development time and the transition would not be smooth, very likely buggy and with regressions like the 4.0 introduction. We do not want to break the desktop!<br />
<br />
= Starting a nested KWin =<br />
Since 5.3 it is possible to start a nested KWin instance under either X11 or Wayland:<br />
{{Input|1=export $(dbus-launch)<br />
kwin_wayland --xwayland<br />
}}<br />
<br />
The option "--xwayland" is required to start a nested X server. The id of the created X11 Display is printed to stdout, e.g.:<br />
{{Input|1=<br />
X-Server started on display :1<br />
}}<br />
<br />
Normally it picks the next free id, e.g. if the system X is on display ":0", it will pick ":1".<br />
<br />
With that it's possible to start an application on the nested X Server, e.g.:<br />
{{Input|1=DISPLAY=:1 kwrite<br />
}}<br />
<br />
The nested KWin is started on your primary windowing system. E.g. if the DISPLAY environment variable is defined it will start on X11, if the WAYLAND_DISPLAY environment variable is defined it will start on Wayland. It is also possible to explicitly set the system to use by passing command line argument "--x11-display" or "--wayland-display".<br />
<br />
To run a Qt application as a Wayland client on this KWin instance, one just needs to set the qpa platform to wayland:<br />
{{Input|1=QT_QPA_PLATFORM=wayland kwrite<br />
}}<br />
<br />
It is possible to verify whether X11 or Wayland is used in Help -> About Application -> Version<br />
<br />
= Running on a tty =<br />
{{Warning|This requires at least Qt 5.4.2, with an older version KWin might freeze during startup.}}<br />
<br />
Since 5.4 it is possible to start a KWin instance on the DRM interface. For this go to a tty:<br />
{{Input|1=kwin_wayland --xwayland<br />
}}<br />
<br />
As an alternative one can also specify which backend to use. On a tty both --drm and --framebuffer are supported, though only --drm provides OpenGL acceleration. If none is specified it will use the DRM backend.<br />
<br />
The option "--xwayland" is required to start a nested X server. Normally it picks the next free display id, so if an X Server is running on ":0" it picks ":1".<br />
<br />
Once the screen turned black KWin has taken over the display and one can open windows on the Xwayland server. Therefore go to another tty and start an application by passing the correct DISPLAY variable:<br />
{{Input|1=DISPLAY=:1 kwrite<br />
}}<br />
<br />
Now switching back to the tty KWin is running on should show the started window and allow to interact with it. Support for running KWin on a tty is still in it's early stages. Bugs are to be expected and there are known missing features. Please consider it only as a mode to experiment with.<br />
<br />
= Start a Plasma session on Wayland =<br />
{{Warning|This requires at least Qt 5.4.2, with an older version KWin might freeze during startup.}}<br />
<br />
Since 5.4 it is possible to start a complete Plasma session on Wayland. For this go to a tty, log in, end the running X server (otherwise startup might block) and run the following command:<br />
{{Input|1=startplasmacompositor<br />
}}<br />
<br />
Support for running a full Plasma session on Wayland is still in it's early stages. Bugs are to be expected and there are known missing features. Please consider it only as a mode to experiment with.<br />
<br />
= Why not Mir? =<br />
The Mir project got announced while KWin was already being ported to Wayland. At that time it was not known whether Mir will succeed or not given that it was in very early development stage. Furthermore it was at that time only a solution for one downstream distribution. This made it unsuited to adjust the development plans. Given that the development continues to focus on Wayland. As long as Mir is a solution for only one downstream distribution the maintenance overhead of adding support is not justified.<br />
<br />
= I found a bug, what should I do? =<br />
<br />
Open your text editor, fix it and open a review request on [http://git.reviewboard.kde.org Review Board].<br />
<br />
= I want to help =<br />
<br />
Great, get in touch with us either through kwin at kde dot org or plasma dash devel at kde dot org or find us in #kwin or #plasma on freenode. There is lots to work on and we can use every helping hand.<br />
<br />
= More Information =<br />
* Presentation on Desktop Summit 2011: [[Media:KWin_Wayland.pdf|Slides]]<br />
* Presentation at Akademy 2014: [https://conf.kde.org/system/attachments/43/original/kwin-akademy-2014.pdf Slides "The state of KWin/Wayland"]<br />
* Presentation at Akademy 2015: [https://conf.kde.org/system/attachments/75/original/presentation.pdf Slides "Welcome to Masachusetts"]</div>Mgraesslinhttps://community.kde.org/index.php?title=Plasma/5.6_Errata&diff=46798Plasma/5.6 Errata2016-03-01T16:07:51Z<p>Mgraesslin: </p>
<hr />
<div>Known issues in the Plasma 5.6 release.<br />
<br />
== Intel GPUs ==<br />
We have received many reports on problems with running Plasma on hardware with graphic cards provided by Intel. We are sorry for the inconvenience and are sorry that we are not able to provide a product which is on par on all systems. Our aim is it to have our software run well on all hardware, but we cannot prevent errors in the underlying stack. Our software was hit by surprise by the issues which are from our view regressions in the underlying driver stack as previous versions worked fine. We would have liked to provide workarounds for these issues which can only be fixed by Intel. Unfortunately we were not able to find a satisfying solution. Given that we present here a list of known workaround which can be tried by affected users.<br />
<br />
We encourage our users who experience problems to come to forum.kde.org so that we can help with our knowledge and to help us gather more information to provide better workarounds.<br />
<br />
=== Random application crashes===<br />
This issue is caused by a bugs.freedesktop.org/show_bug.cgi?id=86281|Intel driver bug. A reported workaround is to change AccelMethod to UXA in the xorg configuration and restarting the system. Please refer to documentation provided by your distribution on how to change this.<br />
<br />
=== Heavy rendering artifacts===<br />
Users told us that enabling DRI3 in xorg configuration can circumvent this problem. An alternative can be to use the new OpenGL ES backend in KWin which also seems to circumvent the problem or disable compositing completely.<br />
<br />
==KWin Wayland==<br />
* Integration features in Plasma still missing or incomplete (e.g. Pager applet, task manager)<br />
* No support for xdg_shell which means GTK+ applications cannot be started on Wayland<br />
* No Copy/Paste from X11 to Wayland windows and vice versa<br />
* No support for animated mouse cursors bugreports.qt.io/browse/QTBUG-48181 Qt Bug 48181<br />
* XWayland doesn't remove outputs bugs.freedesktop.org/show_bug.cgi?id=92914 Freedesktop Bug 92914<br />
* XWayland older than 1.18 lacks features, no touch, no updates on screen hot plug<br />
* Several effects break multi-screen rendering<br />
* No focus stealing prevention for Wayland windows<br />
* No window rules support for Wayland windows<br />
* Screen configuration only partially implemented<br />
<br />
== Tech Previews ==<br />
* Plasma Media Center is in tech preview and misses features compared to Plasma Media Center 1<br />
* Breeze Plymouth Theme is in tech preview<br />
* Breeze Grub Theme is in tech preview<br />
<br />
== Missing features ==<br />
* KWin does not provide window tabs<br />
* Tooltips on window decoration buttons<br />
<br />
== Configuration changes ==<br />
Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts from Plasma 4 should be moved there.</div>Mgraesslinhttps://community.kde.org/index.php?title=KWin/Window_Metadata&diff=45517KWin/Window Metadata2016-01-25T07:08:03Z<p>Mgraesslin: Created page with "=Window Metadata= ==Rational== Window Thumbnails as scaled down window content are hardly useable. Windows of same application are hardly distinguishable from each other whic..."</p>
<hr />
<div>=Window Metadata=<br />
==Rational==<br />
<br />
Window Thumbnails as scaled down window content are hardly useable. Windows of same application are hardly distinguishable from each other which eliminates all advantages from thumbnails in first place.<br />
<br />
In addition on Wayland it is difficult to get access to live-updating window thumbnails in the desktop shell. While the compositor has access to the window content, other applications do not. This would require a custom protocol to pass the window content from the compositor to the desktop shell. A protocol would be required which would be fairly close to being an own Wayland server.<br />
<br />
This document describes how to put the application more in control of the window thumbnail which will be rendered.<br />
<br />
== General Architecture ==<br />
<br />
The protocol will be implemented using DBus to be windowing system agnostic. The window manager registers a DBus service "org.kde.kwin.windowmetadata1" and the object path "/org/kde/kwin/WindowMetadata1". On this interface there is a call "register" which allows an application to call it and to indicate that it supports the protocol.<br />
<br />
The window manager is able to map windows to the DBus peer through the PID. On both X11 and Wayland the window manager has access to the PID. In case of Wayland this is only possible for the window manager, thus the DBus service must be bound on the window manager.<br />
<br />
When a thumbnail is required the window manager informs the application for which window and in which size a thumbnail is needed. In addition it passes a filedescriptor of a pipe to the application. The application renders the thumbnail and writes the rendering result into the pipe and closes the pipe once the rendering is<br />
finished. The application can render a thumbnail of different size if this of more use. To support that a small binary protocol on the pipe is required. It needs to describe:<br />
* size (width/height)<br />
* stride<br />
* image format<br />
* byte count<br />
* binary data<br />
<br />
Obviously the server side needs to sanity check the values.<br />
<br />
The protocol is not meant to have life-updating previews. There is a DBus call for the application to indicate that it has new data available, but it's the responsibility of the server to initiate the process. By that the server can control the updates to a sensible amount.<br />
<br />
== Passing thumbnail to Desktop Shell ==<br />
<br />
Internal implementation detail, to be defined.<br />
<br />
== Window Actions ==<br />
<br />
An additional idea is to allow the application to specify additional actions through the DBus interface. E.g. a "reload" action in a browser. This is intended to be implemented in a future release.<br />
<br />
== Implementation ==<br />
<br />
The implementation will be provided through a tier1 framework. It will be windowing system agnostic and only depends on DBus. For the application it will be as simple as just rendering to a QImage (through QPainter) or using a special QtQuick import.</div>Mgraesslinhttps://community.kde.org/index.php?title=KWin&diff=45516KWin2016-01-25T07:07:40Z<p>Mgraesslin: /* Developer Documentation */</p>
<hr />
<div>== Developer Documentation ==<br />
There are several sub sides with some developer documentation:<br />
* [[KWin/Hacking]] General development information<br />
* [[KWin/Building]] How to build KWin from master<br />
* [[KWin/Getting_Involved]] How You could get involved in KWin development<br />
* [[KWin/Frameworks]] How to build KWin on frameworks and help porting<br />
* [[KWin/Dependencies]] Dependencies of KWin on frameworks 5<br />
* [[KWin/KConfigXT_Effects]] Project: Port Effects to KConfigXT<br />
* [[KWin/KConfigXT]] Project: Create KConfigXT for KWin core<br />
* [[KWin/Animations]] Project: Find all animation details in Effects<br />
* [[KWin/Default_Options]] Default Options Project for 4.9<br />
* [[KWin/Ideas]] Ideas for small tasks in KWin<br />
* [[KWin/Environment_Variables]] Overview on the available environment variables in KWin<br />
* [[KWin/Wayland]] General information about KWin and Wayland<br />
* [[KWin/Wayland_Development]] Information for developing KWin + Wayland<br />
* [[KWin/QT5]] Progress on making KWin ready for QT5<br />
* [[KWin/Bugzilla]] Information on Bug Triaging<br />
* [[KWin/Class_Diagram]] Class Diagram of KWin<br />
* [[KWin/Shadow]] New Shadow System<br />
* [[KWin/Screen_Edges]] New Screen Edge Handling<br />
* [[KWin/Decoration]] New Window Decoration API (Discussion)<br />
* [[KWin/Screenlocker]] Moving Screenlocker to KWin (Discussion)<br />
* [[KWin/GSoC/Modularization]] Documentation for GSoC Modularization of KWin<br />
* [[KWin/GSoC/Color_Correction]] Information about the GSoC Color Correction project<br />
* [[KWin/Mission_Statement]] Mission Statement for KWin (Discussion)<br />
* [[KWin/Changelog_5]] Changelog of new features in KWin 5<br />
* [[KWin/Debugging]] Debugging the compositor with gdb is extra tricky, thus here a chaet sheet<br />
* [[KWin/Packaging]] Packaging documentation in particular WRT X11 vs. Wayland<br />
* [[KWin/Window_Metadata]] DBus protocol for passing additional window information</div>Mgraesslin