SUMMARY PIM applications such as Kmail, Kontact, Akonadi Console does not open in the Plasma Wayland session, only in X11 session, when using a newer Nvidia GPU such as 3060 or 4070. STEPS TO REPRODUCE 1. Possess a newer Nvidia GPU, with the proprietary drivers. 2. Open Plasma 6 Wayland. 3. Attempt to open Kmail. OBSERVED RESULT Kmail does not open. EXPECTED RESULT Kmail opens. SOFTWARE/OS VERSIONS ArchLinux > uname -a Linux hostname 6.8.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 05 Apr 2024 00:14:23 +0000 x86_64 GNU/Linux > pacman -Qii kmail kontact qt6-base plasma-desktop nvidia nvidia-utils| grep -E "(Name|Version)" Name : kmail Version : 24.02.1-2 Name : kontact Version : 24.02.1-1 Name : qt6-base Version : 6.6.3-1 Name : plasma-desktop Version : 6.0.3-1 Name : nvidia Version : 550.67-5 Name : nvidia-utils Version : 550.67-1 ADDITIONAL INFORMATION I am using a Nvidia 3060 with a Light Hash Rate. https://bbs.archlinux.org/viewtopic.php?id=294707 has noted identical issue with a 4070, claiming that downgrading qt6 to qt6.6.2 has resolved the issue. Attempting to open in the terminal only results in the following error message ``` > kmail Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadiserver: Starting up the Akonadi Server... /usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-check' instead akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK /usr/bin/mysql_upgrade: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-upgrade' instead This installation of MariaDB is already upgraded to 11.3.2-MariaDB. There is no need to run mariadb-upgrade again for 11.3.2-MariaDB. You can use --force if you still want to run mariadb-upgrade org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: DB initializer done Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7e7cd0002200) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7e7cd0002200) identified as "ETMCalendarMonitor - 109686660511920" org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7e7cd00290c0) ) ... org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7e7cd0268d00) identified as "SpecialCollectionsMonitor - 95485126048928" org.kde.pim.akonadiserver: Subscriber "" disconnected org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7e7cd00a48b0) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7e7cd0299970) ) kf.windowsystem: KWindowInfo is only functional when running on X11 Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. org.kde.pim.akonadiserver: Subscriber "" disconnected org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7e7cd0030bb0) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7e7cd02a3df0) ) org.kde.pim.akonadiserver: Subscriber "" disconnected ... ``` but the kmail window does not show up.
Could be https://bugreports.qt.io/browse/QTBUG-124174 try `QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" kmail` to verify
(In reply to Christophe Marin from comment #1) > Could be https://bugreports.qt.io/browse/QTBUG-124174 > > try `QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" kmail` to verify Hi Christophe Marin, Thanks for the reply. Launching from a terminal.... ``` > QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" kmail Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadiserver: Starting up the Akonadi Server... /usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-check' instead akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK /usr/bin/mysql_upgrade: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-upgrade' instead This installation of MariaDB is already upgraded to 11.3.2-MariaDB. There is no need to run mariadb-upgrade again for 11.3.2-MariaDB. You can use --force if you still want to run mariadb-upgrade org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: DB initializer done Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadicontrol: Akonadi server is now operational. org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7eadc0002200) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7eadc0002200) identified as "ETMCalendarMonitor - 100463343412336" org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7eadc00294e0) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7eadc003efc0) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7eadc0030810) ) ... org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7eadc02469b0) identified as "SpecialCollectionsMonitor - 109019720549696" Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7eadc0257ec0) identified as "MessageListTagMonitor - 109019727279424" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7eadc0257ec0) identified as "MessageListTagMonitor - 109019727279424" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7eadc0261360) identified as "MessageViewerMonitor - 109019730950720" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7eadc0261360) identified as "MessageViewerMonitor - 109019730950720" Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7eadc0090300) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7eadc02456c0) identified as "KMail Kernel ETM - 109019730536816" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7eadc026a760) identified as "TagActionManagerMonitor - 109019733799552" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7eadc0090300) identified as "FilterManagerTagMonitor - 109019728190864" We have an error during reading password "Entry not found" We have an error during reading password "Entry not found" org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_ews_resource_1 (0x5843531e0870) org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_ews_resource_0 (0x5843531e11c0) QTextHtmlParser::applyAttributes: Unknown color name 'rgba(255, 255, 255, 0.9)' QTextHtmlParser::applyAttributes: Unknown color name 'rgba(255, 255, 255, 0.9)' QTextHtmlParser::applyAttributes: Unknown color name 'rgba(255, 255, 255, 0.9)' org.kde.pim.akonadiserver.search: Executing search "kmail2-1588091513-SearchSession" org.kde.pim.akonadiserver.search: Search "kmail2-1588091513-SearchSession" done (without remote search) [SASL-XOAUTH2] - Requesting authID! [SASL-XOAUTH2] - Requesting token! [SASL-XOAUTH2] - filling prompts! [SASL-XOAUTH2] - Requesting authID! [SASL-XOAUTH2] - Requesting token! [SASL-XOAUTH2] - Requesting authID! [SASL-XOAUTH2] - Requesting token! [SASL-XOAUTH2] - filling prompts! [SASL-XOAUTH2] - Requesting authID! [SASL-XOAUTH2] - Requesting token! org.kde.pim.ews: Streaming request timeout - restarting org.kde.pim.ews: Streaming request timeout - restarting ... ``` The output is basically identical. Contrary to the Qt bug report, I wouldn't describe Kmail as freezing, so much so as it just outright failing to even spawn a window.
Updating my system after having had updates pushed to ArchLinux, running the same pacman -Qii | grep command from before: Name : kmail Version : 24.02.2-1 Name : kontact Version : 24.02.2-1 Name : qt6-base Version : 6.7.0-2 Name : plasma-desktop Version : 6.0.3-1 Name : nvidia Version : 550.67-6 Name : nvidia-utils Version : 550.67-1 along with Plasma Framework going from 6.0.0 -> 6.1.0, Kmail now does spawn a window without issue on Plasma Wayland.