https://bugs.kde.org/show_bug.cgi?id=483094
--- Comment #36 from Billy Messenger ---
How do I go about getting the list of commits that happened between versions
6.0 and 6.1?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=483094
--- Comment #35 from Billy Messenger ---
I've also been having monitor troubles ever since Plasma 6.1.
https://bugs.kde.org/show_bug.cgi?id=489457
There's definitely some kind of bug that has been introduced around that time,
but I'm at
https://bugs.kde.org/show_bug.cgi?id=483094
Billy Messenger changed:
What|Removed |Added
CC||u4fqdzbz@billydm.anonaddy.m
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #28 from Billy Messenger ---
This issue could be related to this one
https://bugs.kde.org/show_bug.cgi?id=483094
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #27 from Billy Messenger ---
Oh, nevermind, spoke too soon. I tried just putting the computer to sleep real
quick and it froze on the unlock screen again.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #26 from Billy Messenger ---
(In reply to Billy Messenger from comment #25)
> Maybe, it's an issue with Mini Displayport? (The monitor that is sometimes
> blank on the login screen is connected with mini displayport). I'll
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #25 from Billy Messenger ---
Maybe, it's an issue with Mini Displayport? (The monitor that is sometimes
blank on the login screen is connected with mini displayport). I'll try
switching that to an HDMI cable and see if the i
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #24 from Billy Messenger ---
Darn, now my system is sometimes freezing when I log in/unlock my computer.
I'm thinking it might have something to do with one of my monitors not waking
up properly. I notice that the freeze happens whe
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #23 from Billy Messenger ---
Oh derp, and now I realize those values are supposed to be different across
calls.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #22 from Billy Messenger ---
Nermind, those methods on `Edid` are constant. (Sorry my C++ is a bit rusty.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #21 from Billy Messenger ---
Wait no, derp, only the list of display pointers stays constant, the values
those displays return can still change between calls. So only calculating those
bools once could still solve the problem.
--
You are
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #20 from Billy Messenger ---
(In reply to Billy Messenger from comment #19)
> It also seems like `uniqueEdid`, `uniqueEdidHash`, and `uniqueMst` is being
> recalculated every time `OutputConfigurationStore::findOutput` is called.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #19 from Billy Messenger ---
It also seems like `uniqueEdid`, `uniqueEdidHash`, and `uniqueMst` is being
recalculated every time `OutputConfigurationStore::findOutput` is called. I'm
guessing what may be happening is that for some r
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #18 from Billy Messenger ---
Ah, yeah, I see.
It seems in my case the connector name is more reliable than the hash.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #16 from Billy Messenger ---
Hmm, just taking a gander from reading the source code. Maybe for some reason
one of my monitors isn't reporting a valid `edidIdentifier`, and that causes
the `uniqueEdid` bool to incorrectly be true
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #15 from Billy Messenger ---
There is also this older commit which is where it seems new screen
configuration code was introduced.
https://invent.kde.org/plasma/kwin/-/commit/ae84480fbfdc684b8ee4b0207d3ce679f6fb4cd7
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=489457
Billy Messenger changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #12 from Billy Messenger ---
Nope, I still get the same issue with the NVidia card removed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #11 from Billy Messenger ---
Oh yeah, I do have a secondary NVidia graphics card that I use for testing
stuff in a VM. I wonder if that's creating any funky results? Maybe I'll try
removing it and see if the issue is gone.
-
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #10 from Billy Messenger ---
And here is the output of drm_info with the issue present:
https://pastebin.com/3xxmkKUg
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #9 from Billy Messenger ---
Here's the output of drm_info when it is working:
https://pastebin.com/wFnPF726
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #8 from Billy Messenger ---
Ah, I forgot to give you the output of drm_info. I'll do that real quick.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #7 from Billy Messenger ---
Yeah, it does appear to be getting messed up. For some reason monitor DP-3 is
listed twice and DP-2 does indeed have its scale set to 1.25.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #6 from Billy Messenger ---
Ok cool, I got it to happen immediately. Here it is when the issue is present:
[
{
"data": [
{
"autoRotation": "InTabletMode",
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #5 from Billy Messenger ---
When the issue happens again I'll post the json config then.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
Billy Messenger changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
--- Comment #4 from Billy Messenger
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #2 from Billy Messenger ---
An update. Now sometimes when I first log in after rebooting my computer the
same issue happens.
Am I the only one experiencing this issue? I suppose it's not a major issue but
it's still mildl
https://bugs.kde.org/show_bug.cgi?id=489457
--- Comment #1 from Billy Messenger ---
Oh yeah and I have the monitors set to 75Hz.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489457
Billy Messenger changed:
What|Removed |Added
CC||u4fqdzbz@billydm.anonaddy.m
https://bugs.kde.org/show_bug.cgi?id=489457
Bug ID: 489457
Summary: On Plasma 6.1, monitors get rescaled and repositioned
after waking from sleep
Classification: Plasma
Product: KScreen
Version: 6.1.1
Platform: Arch Lin
30 matches
Mail list logo
