[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 fanzhuyi...@gmail.com changed: What|Removed |Added CC||k...@manongrivot.me --- Comment #12 from fanzhuyi...@gmail.com --- *** Bug 480330 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 behran...@gmail.com changed: What|Removed |Added CC||behran...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 --- Comment #11 from Thomas Lübking --- Yes, even if I had not known, I would have heard - but that is not the same as enforcing the primary screen :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 --- Comment #10 from Leslie Zhai --- > One could btw. specify a blind rule to have all windows always show on screen > 1 kwinoptions separateScreenFocus && activeMouseScreen helps to have all windows always show on screen with activeMouse ;-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 Robert Kaiser changed: What|Removed |Added CC||ka...@kairo.at -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 --- Comment #9 from Thomas Lübking --- (In reply to Martin Gräßlin from comment #7) > that doesn't specify a position. Uh oh, what's going on there? Either the window doesn't specify a position (what's good) or yet another QWidget/Window call ending nowhere. Since netwm is completely multiscreen unaware, it would afaics require some call like KStartupInfoData::setXinerama(.) to define a specific screen - there's no real protocol. One could btw. specify a blind rule to have all windows always show on screen 1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 --- Comment #8 from Leslie Zhai --- app.primaryScreen()->availableGeometry() output is QRect(0,0 1366x732) PS: kwinoptions separateScreenFocus && activeMouseScreen works happily! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 --- Comment #7 from Martin Gräßlin --- WM_NORMAL_HINTS(WM_SIZE_HINTS): user specified size: 480 by 822 window gravity: Static that doesn't specify a position. Uh oh, what's going on there? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 --- Comment #6 from Leslie Zhai --- Hi Martin, I pasted xprop here https://forum.isoft-linux.org/viewtopic.php?f=4&t=32&p=134#p134 > kcmshell5 kwinoptions for the Multiscreen behaviour, both check > separateScreenFocus && activeMouseScreen shown as > https://pbs.twimg.com/media/CnIya4IUkAAc72h.jpg then newly opened window will > shown in the PRIMARY screen ;-) but kwinoptions works happily! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 --- Comment #5 from Martin Gräßlin --- > And I find setScreen(QScreen*) is not able to work for Qt-5.7.0 Can you please xprop such a window. I would like to see what it sets in the normal hints. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 --- Comment #4 from Leslie Zhai --- Hi Armin, As Martin suggested the active screen is configurable https://blog.martin-graesslin.com/blog/2016/07/multi-screen-woes-in-plasma-5-7/ Newly opened windows not placed on the primary screen kcmshell5 kwinoptions for the Multiscreen behaviour, both check separateScreenFocus && activeMouseScreen shown as https://pbs.twimg.com/media/CnIya4IUkAAc72h.jpg then newly opened window will shown in the PRIMARY screen ;-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 Leslie Zhai changed: What|Removed |Added CC||xiangzha...@gmail.com --- Comment #3 from Leslie Zhai --- Hi Martin, Thanks for your reply and your great job ;-) KDE/Openbox session (or just run openbox --replace in your konsole) is able to fix such issue: GIMP and LibreOffice's splash will NOT shown in the extended (but correctly in the primary) screen any more https://pbs.twimg.com/media/CnIQr9DUMAQCuRO.jpg And I find setScreen(QScreen*) is not able to work for Qt-5.7.0 https://github.com/xiangzhai/qwx/commit/9419eabf0fa689fba5046b7e606b0007db7a90a6 Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 Martin Gräßlin changed: What|Removed |Added Target Milestone|1.0 |--- Product|plasmashell |kwin Assignee|aleix...@kde.org|kwin-bugs-n...@kde.org Status|UNCONFIRMED |RESOLVED Version|master |5.7.0 Resolution|--- |INVALID Component|Multi-screen support|xrandr --- Comment #2 from Martin Gräßlin --- Sorry for the late response. > App window sometimes displays on the primary monitor, sometimes on the > extended monitor This is something we do not really control. Windows have the possibility to position themselves when they show. They indicate this through window hints to the window manager and KWin (Plasma's window manager) honors this request. See https://tronche.com/gui/x/icccm/sec-4.html#s-4.1.2.3 for more information. If KWin sees a window with a position set it assumes that the window has more information about where to go than the window manager. Apparently this seems to be wrong in some cases. I appreciate any information about windows which show this behavior. For windows showing incorrect behavior you can override this with a window specific rule to ignore the requested position. With that KWin places the window and for that follows the "active screen" - that's to KWin either the window with the currently active window or the screen containing the mouse cursor (depending on config option). -- You are receiving this mail because: You are watching all bug changes.
