Bug 451218 - [wayland] instant crash at startup (nvidia)
Summary: [wayland] instant crash at startup (nvidia)
Status: RESOLVED UPSTREAM
Alias: None
Product: KScreen
Classification: Plasma
Component: Plasma Applet (show other bugs)
Version: 5.24.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-07 01:55 UTC by Tobias G.
Modified: 2022-03-22 10:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
backtace (88.50 KB, image/png)
2022-03-07 11:50 UTC, Tobias G.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias G. 2022-03-07 01:55:12 UTC
SUMMARY
Hey there,

I recently switched from x11 to wayland, but latte always either crashes when trying to start it or when trying to creaste a new panel.
Here's the log: https://pastebin.com/7bBQhS6t

I have an nvidia GTX 1080 with proprietary graphics drivers installed and I'm on Plasma 5.24.2 on Manjaro.
I already tried to delete the config folder of latte.
Should any additional information be required, I'd be happy to help!


STEPS TO REPRODUCE
1.  start Plasma in wayland session
2.  try to start latte-dock
3.  observe

OBSERVED RESULT
latte crashes

EXPECTED RESULT
latte doesn't crash

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.11-2-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 23.4 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2

ADDITIONAL INFORMATION
Comment 1 Michail Vourlakos 2022-03-07 06:49:55 UTC
https://userbase.kde.org/LatteDock/HowToReportCrashes
Comment 2 Tobias G. 2022-03-07 11:49:37 UTC
(In reply to Michail Vourlakos from comment #1)
> https://userbase.kde.org/LatteDock/HowToReportCrashes

Oh sorry,

I've attached a picture of the backtrace window.
It doesn't really seem to be a crash, but latte just "hangs" endlessly and never shows up.

I also ran the other command listed on the website.

Here's the output of env QV4_FORCE_INTERPRETER=1 latte-dock -d:
https://pastebin.com/dtrbhTtn
Comment 3 Tobias G. 2022-03-07 11:50:00 UTC
Created attachment 147343 [details]
backtace
Comment 4 Michail Vourlakos 2022-03-07 11:52:29 UTC
This is KScreen applet crash under wayland that is hosted probably in the systray.
If you close Latte, add a default plasma panel and relogin dont you have the same crash?
Comment 5 Tobias G. 2022-03-07 11:54:32 UTC
(In reply to Michail Vourlakos from comment #4)
> This is KScreen applet crash under wayland that is hosted probably in the
> systray.
> If you close Latte, add a default plasma panel and relogin dont you have the
> same crash?

oh, that's interesting.
I already added a default plasma panel, before running these latte commands (as I wouldn't have any panel at all otherwise)
So, with default Plasma panel -> crash
Comment 6 Tobias G. 2022-03-07 12:38:52 UTC
(In reply to Michail Vourlakos from comment #4)
> This is KScreen applet crash under wayland that is hosted probably in the
> systray.
> If you close Latte, add a default plasma panel and relogin dont you have the
> same crash?

I just noticed that executing "latte-dock -d --default-layout " brings up a dock that works, I can't add a panel or dock though
Comment 7 Bug Janitor Service 2022-03-22 04:35:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!