https://bugs.kde.org/show_bug.cgi?id=486149
Zamundaaa changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/k
https://bugs.kde.org/show_bug.cgi?id=486149
Zamundaaa changed:
What|Removed |Added
CC||eamonn...@protonmail.com
--- Comment #26 from Zamun
https://bugs.kde.org/show_bug.cgi?id=486149
Nate Graham changed:
What|Removed |Added
Version Fixed In||6.2.0
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #25 from Zamundaaa ---
(In reply to JLV from comment #23)
> I don't know if this changes will be included in the future by default
> installations.
Currently that's up to the distro; Fedora for example already configures it to
be that way b
https://bugs.kde.org/show_bug.cgi?id=486149
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
|
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #23 from JLV ---
(In reply to Mufeed Ali from comment #22)
> After a good amount of time, I can confirm that making SDDM use Wayland did
> in fact fix the issue for me and I haven't faced it since my last comment
> here.
I can confirm too.
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #22 from Mufeed Ali ---
After a good amount of time, I can confirm that making SDDM use Wayland did in
fact fix the issue for me and I haven't faced it since my last comment here.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #21 from Mufeed Ali ---
Okay, the real fix was a lot simpler and the reason might also be simple. I set
SDDM to use Wayland (https://wiki.archlinux.org/title/SDDM#Wayland) and synced
the settings from Plasma to SDDM once. This seems to have
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #20 from Mufeed Ali ---
I am so sorry... What I said above isn't true... Turns out it's me plugging in
power into the laptop that triggered the vrr_capable to 1. But booting with
power plugged in doesn't set it to 1.
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #19 from Mufeed Ali ---
My issue is related to power management somehow. Switching the Power Profile to
anything (even Power Save) consistently gets the state to "vrr_capable: 1"
immediately.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #18 from Mufeed Ali ---
I also just wanted to confirm this. It does switch from "vrr_capable = 0" to
"vrr_capable = 1" at some point post-boot. This doesn't seem to be the case
with my Fedora Silverblue setup though, so might be some issue w
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #17 from Mufeed Ali ---
> Would you be willing to patch KWin to get that information?
Sorry for the delay in getting back to you, but i can do that
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486149
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=486149
Bug Janitor Service changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=486149
JLV changed:
What|Removed |Added
CC||undertakerj...@gmail.com
--- Comment #15 from JLV ---
I
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #14 from Zamundaaa ---
> But the driver probably shouldn't be reporting a lack of VRR support in the
> first place right?
Maybe, we'd have to confirm my theory first. Would you be willing to patch KWin
to get that information?
> Also, if I
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #13 from Mufeed Ali ---
But the driver probably shouldn't be reporting a lack of VRR support in the
first place right? Should I try to report that to mesa?
Also, if I set it to "Automatic" on a boot where the option appears, would that
stil
https://bugs.kde.org/show_bug.cgi?id=486149
Zamundaaa changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #11 from Mufeed Ali ---
I've added output for when it works and when it doesnt work. I've tried
rebooting multiple times now. It seems to work on some boots but not on others.
Is this a driver bug?
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #10 from Mufeed Ali ---
Created attachment 168949
--> https://bugs.kde.org/attachment.cgi?id=168949&action=edit
kscreen output when working
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #9 from Mufeed Ali ---
Created attachment 168948
--> https://bugs.kde.org/attachment.cgi?id=168948&action=edit
drm_info output when option is available
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #8 from Mufeed Ali ---
Is drm_info a dependency for this feature?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486149
Mufeed Ali changed:
What|Removed |Added
Attachment #168932|0 |1
is obsolete||
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #6 from Mufeed Ali ---
Created attachment 168945
--> https://bugs.kde.org/attachment.cgi?id=168945&action=edit
Updated drm_info
Rebooted from windows just now and it's not working again.
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #5 from Mufeed Ali ---
Okay, sorry for the false alert but the `kscreen -o` output was on this boot
and I hadn't checked the system settings app yet. The Adaptive Sync option is
back... I have no idea what's going on.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #4 from Mufeed Ali ---
Created attachment 168939
--> https://bugs.kde.org/attachment.cgi?id=168939&action=edit
`kscreen -o` output
Looks like you're right. VRR is showing up as "Automatic" here. I also feel
like it's working considering t
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #3 from Zamundaaa ---
okay, the driver reports it as supported. Please attach the output of
> kscreen-doctor -o
as well, maybe it's just a bug in the GUI?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486149
--- Comment #2 from Mufeed Ali ---
Created attachment 168932
--> https://bugs.kde.org/attachment.cgi?id=168932&action=edit
drm_info output
I've added the drm_info output here
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486149
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC|
29 matches
Mail list logo
