[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.
https://bugs.kde.org/show_bug.cgi?id=469090 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #9 from Nate Graham --- I think the problem is that the xrandr output says: > eDP connected primary But Plasma and KScreen think the external screen is primary. So they don't agree, which means XWayland apps that use xrandr to determine primary-ness will use the wrong screen. That makes this the same issue as Bug 466149. *** This bug has been marked as a duplicate of bug 466149 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.
https://bugs.kde.org/show_bug.cgi?id=469090 --- Comment #8 from zyf0330 --- Created attachment 159062 --> https://bugs.kde.org/attachment.cgi?id=159062=edit Tilix Quake monitor setting Another thing, I have set Tilix Quake to display on Primary Monitor. And after this problem appears, Tilix Quake window appears on laptop monitor which is set as non-primary monitor. And if I set it to display on Monitor 0, it still displays on laptop monitor. If I set as Monitor 1, it displays on external primary monitor. So I can guess that when this problem occurs, monitor 0 and 1 is swapped. This is config in the .config/plasmashellrc. ``` [ScreenConnectors] 0=HDMI-A-0 1=eDP ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.
https://bugs.kde.org/show_bug.cgi?id=469090 --- Comment #7 from zyf0330 --- This is xrandr output ``` Screen 0: minimum 320 x 200, current 4480 x 1440, maximum 16384 x 16384 eDP connected primary 1920x1200+0+120 (normal left inverted right x axis y axis) 301mm x 188mm 2880x1800 90.01 + 1920x1200 90.01* 1920x1080 90.01 1600x1200 90.01 1680x1050 90.01 1280x1024 90.01 1440x900 90.01 1280x800 90.01 1280x720 90.01 1024x768 90.01 800x600 90.01 640x480 90.01 HDMI-A-0 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1200 59.95 1920x1080 60.0050.0059.94 1600x1200 59.95 1280x1440 59.91 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1280x800 59.95 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 disconnected (normal left inverted right x axis y axis) DisplayPort-2 disconnected (normal left inverted right x axis y axis) DisplayPort-3 disconnected (normal left inverted right x axis y axis) DisplayPort-4 disconnected (normal left inverted right x axis y axis) DisplayPort-5 disconnected (normal left inverted right x axis y axis) DisplayPort-6 disconnected (normal left inverted right x axis y axis) ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.
https://bugs.kde.org/show_bug.cgi?id=469090 --- Comment #6 from zyf0330 --- I forgot to mention one thing. I have create a window rule to force KRunner is placed at screen 0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.
https://bugs.kde.org/show_bug.cgi?id=469090 --- Comment #5 from Nate Graham --- According to KScreen, the external screen is still the primary one. So that doesn't seem to be the issue. There also seems to be some confusion; KRunner doesn't follow the primary screen. It will appear on the *active* screen, with "active" being defined as "the screen with the cursor on it". So that leaves the issue with WebStorm. Can you paste the output of the `xrandr` command when this happens? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.
https://bugs.kde.org/show_bug.cgi?id=469090 --- Comment #4 from zyf0330 --- Created attachment 158760 --> https://bugs.kde.org/attachment.cgi?id=158760=edit kscreen-doctor -o output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.
https://bugs.kde.org/show_bug.cgi?id=469090 --- Comment #3 from Nate Graham --- Thanks. When this happens, can you run `kscreen-doctor -o` in a terminal window and paste the output? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.
https://bugs.kde.org/show_bug.cgi?id=469090 --- Comment #2 from zyf0330 --- These two screens work normally for everything, just the primary screen is switched to another one. On Sat, Apr 29, 2023, 02:58 Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=469090 > > Nate Graham changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > CC||n...@kde.org > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Nate Graham --- > When this happens, can you move the mouse pointer onto the area the > disabled > screen occupied? Or is it stuck on the laptop screen? > > When this happens, can you run `kscreen-doctor -o` in a terminal window and > paste the output? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.
https://bugs.kde.org/show_bug.cgi?id=469090 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- When this happens, can you move the mouse pointer onto the area the disabled screen occupied? Or is it stuck on the laptop screen? When this happens, can you run `kscreen-doctor -o` in a terminal window and paste the output? -- You are receiving this mail because: You are watching all bug changes.
