https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #12 from Gazi ---
(In reply to Zamundaaa from comment #11)
> > I will go ahead and try submit a bug for AMDGPU driver, where they accept
> > bug reports
>
> That would be https://gitlab.freedesktop.org/drm/amd/-/issues
>
> I looked throug
https://bugs.kde.org/show_bug.cgi?id=469764
Zamundaaa changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #10 from Gazi ---
You're 100% correct, it is a driver issue. I've testing this on Gnome and Sway,
enabling VRR causes exactly the same outcome. Tried all 3 DEs on arch and then
gentoo, same result. I will go ahead and try submit a bug for AM
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #9 from Gazi ---
Link to the long log
https://drive.google.com/file/d/1KTE-3vDCjD_t17ekKoGhG4UZFeuXP5V_/view?usp=share_link
didn't want to grep anything out of it, because I am not sure what to look for
:/
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #8 from Gazi ---
Created attachment 159041
--> https://bugs.kde.org/attachment.cgi?id=159041&action=edit
after attempting to change VRR
Sometimes it fails to revert back to normal settings and the screen ends up
looking like this, althoug
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #7 from Gazi ---
Created attachment 159040
--> https://bugs.kde.org/attachment.cgi?id=159040&action=edit
short drm log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #6 from Gazi ---
(In reply to Zamundaaa from comment #5)
> The log doesn't contain any warnings about commits failing or anything like
> that, so this is likely a driver problem. To make sure, can you enable drm
> debug logging and record a
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #5 from Zamundaaa ---
The log doesn't contain any warnings about commits failing or anything like
that, so this is likely a driver problem. To make sure, can you enable drm
debug logging and record a dmesg log while causing the problem again
https://bugs.kde.org/show_bug.cgi?id=469764
Gazi changed:
What|Removed |Added
CC||strelok.zer...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #4 from Gazi ---
Created attachment 159018
--> https://bugs.kde.org/attachment.cgi?id=159018&action=edit
A clip of what is happening
Had to film it with my phone for obvious reasons.
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #3 from Gazi ---
(In reply to Zamundaaa from comment #1)
> Please attach the output of
> > journalctl --user-unit plasma-kwin_wayland --boot 0
> After causing the issue again
Sure thing, submitted it as an attachment. I thought I'd add more
https://bugs.kde.org/show_bug.cgi?id=469764
--- Comment #2 from Gazi ---
Created attachment 159017
--> https://bugs.kde.org/attachment.cgi?id=159017&action=edit
journalctl log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469764
Zamundaaa changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=469764
Nate Graham changed:
What|Removed |Added
Component|kcm_kscreen |wayland-generic
Assignee|kscreen-bugs-n
14 matches
Mail list logo
