Plasma/5.0 Errata: Difference between revisions
< Plasma
Mgraesslin (talk | contribs) (→Bugs) |
No edit summary |
||
| Line 19: | Line 19: | ||
== Configuration changes == | == Configuration changes == | ||
* Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts should be moved there. The relevant System Settings control panel has been adjusted for | * Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts should be moved there. The relevant System Settings control panel has been adjusted for this change. | ||
== Performance == | |||
of Plasma 5.0 is heavily dependent on specific hardware and software configurations and usage patterns. While it has great potential, it takes time to wrangle this out of it and the underlying stack is not entirely ready for this either. In some scenarios, Plasma 5.0 will display the buttery smooth performance it is capable off - while at other times, it will be hampered by various shortcomings. These can and will be addressed, however, much is dependent on components like Qt, Mesa and hardware drivers lower in the stack. Future releases are expected to bring significant performance improvements thanks to fixes at all levels. | |||
Revision as of 14:20, 14 July 2014
Known issues in the Plasma 5.0 release.
Bugs
- Graphics corruption may occur on Intel drivers, upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=79448
- Dragging icons out of Folder instances can occassionally partly misrender the icons attached to the mouse cursor on nVidia's proprietary drivers. Qt 5.4 is introducing new API that will make this much more robust.
- XEmbed-based systemtray not supported anymore, for workarounds see http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/ http://notmart.org/blog/2014/06/systemtray-plasma-next-and-gtk/
- Override redirect windows (e.g. tooltips, Window Switcher, etc.) are completely translucent on first show, upstream bug: https://bugreports.qt-project.org/browse/QTBUG-39329
- The Meta (or "Windows") key is not recognized as modifier key. Patch merged into Qt for 5.3: https://codereview.qt-project.org/#/c/87615/
- Aurorae window decoration themes might crash the window manager, upstream bug: https://bugreports.qt-project.org/browse/QTBUG-39336
- Text in QML (Plasma Applets and/or Aurorae windows decorator) can get corrupted/turned into boxes: https://bugs.kde.org/show_bug.cgi?id=336615
- Battery monitor tray icon does not reflect AC adapter state - that is gone from Solid Devices, Power API not yet ready
- Running a Qt5 application using libvlc crashes that application, apparently because of outdated/non-existing VLC cache. See launchpad bug https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1328466
- Graphs in KsysGuard are broken, see https://git.reviewboard.kde.org/r/119265/
Missing features
- No holidays or calendar events displayed in the Plasma calendar - Awaiting KDE PIM libraries to port to KF5/Plasma5.
- Unable to edit individual locale settings - Can change locale used for setting groups such as currency or date/time, but cannot yet modify individual settings like short date format - Awaiting support upstream in Qt.
- Support for autostarting scripts (like ones setting ssh-agent and so on) in the user's home directory (~/.config/autostart) is missing. Support for applications using .desktop files is still working, however. A possible workaround involves creating .desktop files which launch the interested programs. Discussion is ongoing on how to handle this missing feature.
Configuration changes
- Environment variables and shutdown scripts are now sourced from ~/.config/plasma-workspace/env and ~/.config/plasma-workspace/shutdown, respectively. Existing scripts should be moved there. The relevant System Settings control panel has been adjusted for this change.
Performance
of Plasma 5.0 is heavily dependent on specific hardware and software configurations and usage patterns. While it has great potential, it takes time to wrangle this out of it and the underlying stack is not entirely ready for this either. In some scenarios, Plasma 5.0 will display the buttery smooth performance it is capable off - while at other times, it will be hampered by various shortcomings. These can and will be addressed, however, much is dependent on components like Qt, Mesa and hardware drivers lower in the stack. Future releases are expected to bring significant performance improvements thanks to fixes at all levels.