Created attachment 151437 [details] Log from Terminal start SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I will maybe provide a debug log, when I have the time. STEPS TO REPRODUCE 1. Update Haruna 2. Start Haruna OBSERVED RESULT Crash. EXPECTED RESULT Haruna should start. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.60-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3 Memory: 7.7 GiB of RAM Graphics Processor: NVIDIA ADDITIONAL INFORMATION Haruna 0.8.0 works. Compiled via https://aur.archlinux.org/packages/haruna
Created attachment 151463 [details] gdb log
I compiled haruna with debug symbols now and hope that the log contains something useful, though I am not sure I did this correctly. If not, maybe someone could tell me how to do it correctly.
I tried it in a Manjaro VM and it worked fine. Try running it in a new user account.
Note: I will also try it with a second clean account, but for now: I just tried it again (on the usual account) and it seems to be a problem related to Wayland (and maybe Nvidia; one guess would be, that you can't replicate it, because in a VM you usually don't have Nvidia): If I use: $ QT_QPA_PLATFORM=xcb haruna Haruna starts. If I use: $ haruna -platform wayland Haruna fails to start.
(In reply to george fb from comment #3) > I tried it in a Manjaro VM and it worked fine. Try running it in a new user > account. Update: I now tried it with a new user, with the same result as above.
I have no idea what could cause it. I tried it on wayland, on my opensuse tw system with nvidia, and it worked. Try the flatpak maybe.
(In reply to george fb from comment #6) > I have no idea what could cause it. > I tried it on wayland, on my opensuse tw system with nvidia, and it worked. > > Try the flatpak maybe. I guess the only possible explanations left are: - Manjaro has some config included in vanilla manjaro versions that is causing this - or there is some kind of "bug fix" in newer versions of dependency software that is maybe not included in Manjaro yet, or vice versa. Will try the flatpak (I assume that includes the dependencies bundled with the software?).
Still a problem with 0.9.1. But I tried the Flatpak version now and it works (as expected), so it seems to be a problem with my dependency packages installed.
This could be caused by the cache, if you still encounter this problem try deleting your cache.
(In reply to george fb from comment #9) > This could be caused by the cache, if you still encounter this problem try > deleting your cache. I tried deleting the cache in "/home/[username]/.cache/KDE/haruna", but it still crashes.
*** Bug 463123 has been marked as a duplicate of this bug. ***
Deleting cache does not help in this case. haruna fails to start with the same message: unknown() : file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: QML MenuItem: Binding loop detected for property "implicitWidth"
(In reply to Ricky from comment #12) > Deleting cache does not help in this case. > > haruna fails to start with the same message: unknown() : > file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: > QML MenuItem: Binding loop detected for property "implicitWidth" Some additional observations: I checked running Haruna inside a VM on Arch. Plasma 5.26.4 Frameworks 5.101.0 Wayland 1.21.0-2 I still get the same messages however Haruna opens successfully. This indicates to me that those QML messages are just warnings? The only major difference I see between running inside a VM and baremetal causing an issue is using a NVIDIA GPU which I use since those drivers were recently updated.
(In reply to Ricky from comment #13) > (In reply to Ricky from comment #12) > > Deleting cache does not help in this case. > > > > haruna fails to start with the same message: unknown() : > > file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: > > QML MenuItem: Binding loop detected for property "implicitWidth" > > Some additional observations: > > I checked running Haruna inside a VM on Arch. > Plasma 5.26.4 > Frameworks 5.101.0 > Wayland 1.21.0-2 > > I still get the same messages however Haruna opens successfully. This > indicates to me that those QML messages are just warnings? > The only major difference I see between running inside a VM and baremetal > causing an issue is using a NVIDIA GPU which I use since those drivers were > recently updated. Solved. Downgrading nvidia drivers to 520.56.06 and haruna successfully opens.
What version did you have before?
(In reply to george fb from comment #15) > What version did you have before? 525.60.11
Still fails with: Nvidia 525.78.01-1 Haruna 0.10.2
(In reply to tobias from comment #17) > Still fails with: > Nvidia 525.78.01-1 > Haruna 0.10.2 Even with QT_QPA_PLATFORM=xcb ?
(In reply to Ricky from comment #18) > (In reply to tobias from comment #17) > > Still fails with: > > Nvidia 525.78.01-1 > > Haruna 0.10.2 > > Even with QT_QPA_PLATFORM=xcb ? That works (as I already said: https://bugs.kde.org/show_bug.cgi?id=458078#c4) While using XWayland might be a workaround, it does not fix the problem. And using XWayland is much slower (at least on my machine), I have switched to using mpv in the meantime. It would be interesting to know whether this an Nvidia bug or whether Nvidia changed something that Haruna or its dependencies must adjust to.
Created attachment 155223 [details] haruna log
Getting the same issue too. Haruna fails to open on NVIDIA drivers (525.78.01) I followed the comments on https://bugs.kde.org/show_bug.cgi?id=458078#c14 This could be a NVIDIA issue since downgrading the drivers helps and Haruna loads up fine. I am on Arch too, so maybe its an issue there too.. I am not entirely sure though.
Closing, I can't reproduce and the provided information is not enough.