Plasma/Plasma 6: Difference between revisions

From KDE Community Wiki
No edit summary
(Link to Phab task for QML import path issue)
Line 5: Line 5:
* [https://bugs.kde.org/buglist.cgi?bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bug_severity=task&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&f1=keywords&f2=reporter&list_id=2394509&o1=allwordssubstr&query_format=advanced&v1=qt6 List of issues]
* [https://bugs.kde.org/buglist.cgi?bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bug_severity=task&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&f1=keywords&f2=reporter&list_id=2394509&o1=allwordssubstr&query_format=advanced&v1=qt6 List of issues]
* In a built-from-source dev session on top of a distro-provided session, KWin effect IDs have changed, so they appear duplicated in the Effects KCM and you need to disable one of each, or else both play at the same thing and there are weird visual glitches.
* In a built-from-source dev session on top of a distro-provided session, KWin effect IDs have changed, so they appear duplicated in the Effects KCM and you need to disable one of each, or else both play at the same thing and there are weird visual glitches.
* In a built-from-source dev session on top of a distro-provided session, Qt5-using QML apps don't launch because they'll try to use the KF6 Kirigami. Workaround: For those apps, create custom .desktop files with QML2_IMPORT_PATH set to the built-from-source KF5 location in the "Environment Variables" field, and an absolute path to to the built-from-source executable in the "Program" field.
* In a built-from-source dev session on top of a distro-provided session, Qt5-using QML apps don't launch because they'll try to use the KF6 Kirigami. Workaround: For those apps, create custom .desktop files with QML2_IMPORT_PATH set to the built-from-source KF5 location in the "Environment Variables" field, and an absolute path to to the built-from-source executable in the "Program" field. See also https://phabricator.kde.org/T16483.


On the Qt side:
On the Qt side:

Revision as of 15:11, 20 June 2023

Plasma 6 is built on top of Qt 6 and is tentatively planned to be released in late 2023 or early 2024. This page outlines important information and major changes coming in Plasma 6.

Known issues

On the KDE side:

  • List of issues
  • In a built-from-source dev session on top of a distro-provided session, KWin effect IDs have changed, so they appear duplicated in the Effects KCM and you need to disable one of each, or else both play at the same thing and there are weird visual glitches.
  • In a built-from-source dev session on top of a distro-provided session, Qt5-using QML apps don't launch because they'll try to use the KF6 Kirigami. Workaround: For those apps, create custom .desktop files with QML2_IMPORT_PATH set to the built-from-source KF5 location in the "Environment Variables" field, and an absolute path to to the built-from-source executable in the "Program" field. See also https://phabricator.kde.org/T16483.

On the Qt side:

Developer-facing changes

  • Widget API has changed and all widgets need to be ported. See the Plasma 6 widget porting guide to learn how.
  • On Wayland, Plasma panels, sidebars, KRunner, and Yakuake are now positioned using the layer-shell protocol.

User-facing changes

Additions

Changes to default settings

Removals

Work that's been decided on but not implemented yet