Bug 463123

Summary: [Wayland] Haruna fails to start
Product: [Applications] Haruna Reporter: Ricky <ecto1>
Component: genericAssignee: george fb <georgefb899>
Status: RESOLVED DUPLICATE    
Severity: normal CC: ecto1
Priority: NOR    
Version: 0.9.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ricky 2022-12-16 15:54:35 UTC
SUMMARY
***
After upgrading to Plasma 5.26.4, Haruna refuses to start and immediately crashes on Wayland.
Tested on X11 and it works successfully.

Running haruna from the terminal the following is reported.

unknown() : qrc:/qml/main.qml:178:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }

unknown() : qrc:/qml/Actions.qml:39:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }

unknown() : qrc:/qml/HProgressBar.qml:212:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }

unknown() : file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: QML MenuItem: Binding loop detected for property "implicitWidth"

The last message is reported a dozen more times.

I am speculating an update somewhere in the QT packages has caused an issue here.
When I do a diff between the packages recently updated, I see changes to:

- qt5-base
- qt5-declarative
- qt5-wayland

***


STEPS TO REPRODUCE
1. Start haruna from the terminal, or through the desktop shortcut

OBSERVED RESULT
Crashes with errors pointing to QML

EXPECTED RESULT
Haruna should open

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION

If I use QT_QPA_PLATFORM=xcb haruna at the terminal then it opens.
Comment 1 george fb 2022-12-16 19:03:51 UTC
Try deleting the cache.

*** This bug has been marked as a duplicate of bug 458078 ***