I have two displays on screen :0. The primary display is on the RIGHT and the secondary display is on the LEFT: > xrandr | grep \ connected DVI-I-1 connected primary 1920x1200+1920+0 (normal left inverted right x axis y axis) 518mm x 324mm DVI-D-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm Here is a list of things that are going wrong on the secondary display: 1) When I maximize a window on the secondary display it gets maximized AND moved to the primary display. When I unmaximize it, the window stays on the primary display. 2) When a window on the secondary display is put in fullscreen mode (e.g. F11 in firefox), it goes in fullscreen mode but on the primary display. When I return from fullscreen, the window returns to the secondary display. 3) In the window title bar menu (right click), I have 2 options in "Move to Screen": Screen 1 and Screen 2. - If a window on the primary display is choosen, option Screen 1 is preselected. Choosing "Move to Screen 2" has NO EFFECT (menu closes, window doesn't move). - If a window on the secondary display is choosen, option Screen 2 is preselected. Choosing "Move to Screen 1" has NO EFFECT (menu closes, window doesn't move). 4) Draging windows from primary to secondary or from secondary to primary works well except for maximized windows. If I start with a maximized window on the primary display and drag it to the secondary display, when i release the mouse button the window is instantly moved back to the primary display. 5) Snapping of window edges with screen edges works everywhere except on the left edge of the secondary display. No snapping there! Reproducible: Always Steps to Reproduce: 1. See above. Actual Results: See above Expected Results: 1) Maximizing a window on the secondary display should maximize it on the secondary display (not the primary display). 2) Putting a window on the secondary display in fullscreen mode should put it on fullscreen mode on the secondary display (not the primary display). 3) Moving a window from screen 1 to screen 2 or vice versa using the window menu should result in the window being moved. 4) Moving a maximized window from the primary display to the secondary display should be possible. 5) Snapping on every edge of the screen should occur, including the left edge of the secondary display. Packages: kwin-5.3.1-1.fc22.x86_64 kmod-nvidia-4.0.4-303.fc22.x86_64-346.72-2.fc22.1.x86_64 Options: Window Behavior / Focus : "Active screen follows mouse" is selected Window Behavior / Moving : "Border snap zone" = 10 Window Behavior / Moving : "Window snap zone" = 10 KWin Scripts : Only "Enforces Window Decorations on GTK+ window" is selected Display Configuration : everything shown is correct and "Unify Outputs" is not selected.
I can't reproduce any of this what may be due to https://git.reviewboard.kde.org/r/123882/ However, please log the output of "xprop -root _NET_WORKAREA" (not being able to send windows from one to another screen sounds suspicious) As for moving maximized, do you have "quick maximization" enabled? (the thing where you can drag window to the top of the screen to maximize them) Ideally, attach the output of qdbus org.kde.KWin /KWin supportInformation
Thank you for your quick reply. > xprop -root _NET_WORKAREA _NET_WORKAREA(CARDINAL) = 0, 39, 3800, 1161 Desktop Behavior / Screen Edges / Window Management : "Maximize windows by dragging them to the top of the screen" is disabled.
Created attachment 92995 [details] Output of "qdbus org.kde.KWin /KWin supportInformation"
Errr... > Multi-Head: yes This is a multihead setup w/ the two presented putputs on :0.0 and some more on :0.1? In doubt please attach /var/log/Xorg.0.log
Yes: the 2 presented outputs are on :0.0. That's where the kde desktop is. There is a single output (TV) on a seperate screen :0.1. Screen :0.1 is on the right of screen :0.0. I just tried disconnecting the TV and use only the setup described in the original post (i.e. :0.0 only). OMG, 1), 2), 3), 4) and 5) are working now. I thought :0.0 and :0.1 were seperated enough so that :0.1 was not responsible for the problems experienced in :0.0. That's why I didn't bother to describe the whole setup at first. Sorry about that. Now, I still need to connect my TV on a seperate X screen. Why is everything screwed up when I do that? Kwin behaves badly on :0.1 too: no background image, unable to add panel, unable to go fullscreen (everything turns black), font sizes are way off (very big), no menu on desktop right click, etc. To do anything usefull on the TV, I currently replace kwin with openbox (on :0.1 only) which is working fine.
Created attachment 92996 [details] /etc/X11/xorg.conf
Created attachment 92997 [details] /var/log/Xorg.0.log
multi-head is a hardly used and hardly maintained feature. Your usecase (xrandr+multi-head) is even more rare than just multi-head. Please do not expect any fixes for the problem.
Ok, but is it possible in any way to tell kwin (and kde in general) to simply ignore :0.1? I can manage that screen with something else. All I want to do with it is mostly fullscreen video and I don't want windows from my desktop to slide or suddenly appear there. Thank you for your help.
maybe, maybe not. As said: it's a hardly used feature and hardly tested feature. Some things work, some don't. But at least to me it's not known which features work and which not.
After trying several things, this one seems to work. 1. Log in a KDE session. 2. Kill kwin on :0.1 and replace it with another WM (openbox is working). 3. On :0.0 do "KDE_MULTIHEAD=false kwin_x11 --replace". Not pretty, but apparently 1) to 5) (original post) are working on the dual display :0.0 and I still have access to the separate screen :0.1 . There might be a way to enforce KDE_MULTIHEAD=false before I login, but I don't know how to do that.
In fact, it is uncessary to kill kwin in step 2 of the previous hack. This one works equally well: 2. "DISPLAY=:0.1 KDE_MULTIHEAD=false kwin_x11 --replace" In summary, restarting both instance of kwin with KDE_MULTIHEAD=false seems to work.
putting an executable script #!/bin/sh export KDE_MULTIHEAD=false into ~/.config/plasma-workspace/env/no_multihead.sh should do (but I've not tested that env path yet, used to be ~/.kde/env, but is no more)
I confirm that adding "no_multihead.sh" solves the problems on :0.0. All I need to do after logging in is to start kwin on :0.1 (which can be done with a script). Thank you!
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
I am still using the hack described in comments #11 through #13. This solved 1) to 5) in the original post, but everything at the end of comment #5 is still valid: --- Kwin behaves badly on :0.1 too: no background image, unable to add panel, unable to go fullscreen (everything turns black), font sizes are way off (very big), no menu on desktop right click, etc. ---
Support for multi-head had been dropped.