https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #14 from rthe...@protonmail.com ---
(In reply to Nate Graham from comment #13)
> So with the old cable, it's still broken in the same way, or still broken
> but in a different way, or it's fixed now?
I didn't change cables, I just swapped wh
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #13 from Nate Graham ---
So with the old cable, it's still broken in the same way, or still broken but
in a different way, or it's fixed now?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #12 from rthe...@protonmail.com ---
Hi Nate,
Sorry it took me so long, but I have some news. I swapped the DP cables between
Dell and HP monitors, and after resume the primary monitor was set to the
other one!
kscreen-doctor after swapp
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #11 from Nate Graham ---
If you bring back the old cable, does the issue come back? If so, it might
truly be a hardware issue, similar to another bug report I saw recently that
was ultimately solved with a new HDMI cable.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #10 from rthe...@protonmail.com ---
Alright, an interesting development has occured. I've changed the layout of the
monitors, because I replaced the monitor arm so my monitors are one above
another. This seem to have fixed the issue with swap
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #9 from rthe...@protonmail.com ---
(In reply to Nate Graham from comment #8)
> Thanks. Nothing looks crazy to me in there.
>
> Seems similar to the issue reported in Bug 466342.
Yup, the report seems to be the same as my case, except with s
https://bugs.kde.org/show_bug.cgi?id=469653
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #7 from rthe...@protonmail.com ---
Just for completeness sake, here's the output of doctor before and I after
change primary once the screens got flipped from resume:
(~)$ kscreen-doctor -o
Output: 1 DP-3 enabled connected priority 2 Display
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #6 from rthe...@protonmail.com ---
Sure Nate, Here you go:
(~)$ kscreen-console bug
xrandr --verbose==
Screen 0: minimum 16 x 16, current 4880 x 2560, maximum 32767 x 32767
XWAYLAND1 connected
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #5 from Nate Graham ---
So it looks like which screen counts as output 1 and which counts as output 2
are getting switched around.
Can you also attach the output of `kscreen-console bug`?
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #4 from rthe...@protonmail.com ---
Managed to get it flipped after second resume from sleep.
Attaching also kscreen-doctor output
(~)$ kscreen-doctor -o
Output: 1 DP-3 enabled connected priority 2 DisplayPort Modes: 0:3440x1440@60!
1:3440x
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #3 from rthe...@protonmail.com ---
Created attachment 159019
--> https://bugs.kde.org/attachment.cgi?id=159019&action=edit
Monitor layout after resume from sleep
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469653
--- Comment #2 from rthe...@protonmail.com ---
Hi Nate,
Yes, the output I provided from both the screenshot and kscreen-doctor is how
it's supposed to be. I will paste here the output of both when the screens are
'flipped' after resume.
Regards
--
Yo
https://bugs.kde.org/show_bug.cgi?id=469653
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REPORTED
14 matches
Mail list logo
