| Summary: | Plasma/Wayland always goes frozen on an AMD APU | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | HD Scania <hd-scania> |
| Component: | platform-drm | Assignee: | HD Scania <hd-scania> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | aleixpol, hd-scania |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.4 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Was a log run on Trinity X11 just now demonstrating whatever was going on with my Plasma Wayland compositions
My SDDM logs ... SDDM is where i usually start Plasma Wayland compositions from My SDDM logs up to 18 April simplified with only Wayland related, warnings, and errors |
||
|
Description
HD Scania
2023-04-18 00:24:51 UTC
I'm afraid we will need more information here. Can you maybe check if you can find any errors on the user logs, maybe from the kwin_wayland process? As is, this is not really actionable. Where to get logs for Wayland-related issues? And will going frozen then having to reboot even be loggable? I'm quite unsure Something I do in these cases is the following: - start the system, switch to a tty (ctrl+alt+F3) - log into your user - run tmux (or screen or anything similar you prefer) - ssh from another system - attach to the tmux from the other system "tmux a" - execute "startplasma-wayland" There we should be able to see what's going on. Created attachment 158184 [details]
Was a log run on Trinity X11 just now demonstrating whatever was going on with my Plasma Wayland compositions
There was a log running the Plasma Wayland compositions on QTerminal under Trinity X11, but ok for being told what's going wrong? (In reply to Aleix Pol from comment #3) Created attachment 158185 [details]
My SDDM logs ... SDDM is where i usually start Plasma Wayland compositions from
Created attachment 158203 [details]
My SDDM logs up to 18 April simplified with only Wayland related, warnings, and errors
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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |