I have 3 Monitors. Always when i have on my middle Monitor some open App-Windows and my PC goes into Monitor-Energy-Save-Mode after 15 Minutes then is it so that after reactivate are all my open App-Windows from my middle Monitor are automatical moved into my left Monitor. Reproducible: Always
Sounds as if at elast one screen gets removed (and the desktop resizes) when it falls asleep. The windows are moved to the remaining visible region (the left screen, eventually the topleft corner) to not be lost. Either ssh into the machine or set a sleep timer sleep $((15*60+30)); xrandr -q to check the screen setup while the screen is in power saving mode (the commad waits 15.5 minutes and the dumps the setup. You might also wait less long and on a second konsole run "xset dpms force off" to activate screen powersaving immediately) Post the output and a comparing "xrandr -q" without powersaving for confirmation of the assumption.
I think that's absolutely correct! What can I do that the Powersavingmode do not resize my desktop size?
Hello, I think that's absolutely correct! What can I do that the Powersavingmode do not resize my desktop size? Liebe Grüße Martin Montag, 11. November 2013, 13:56:15 - Thomas Lübking schrieb: > https://bugs.kde.org/show_bug.cgi?id=327442 > > --- Comment #1 from Thomas Lübking <thomas.luebking@gmail.com> --- > Sounds as if at elast one screen gets removed (and the desktop resizes) when it > falls asleep. The windows are moved to the remaining visible region (the left > screen, eventually the topleft corner) to not be lost. > > Either ssh into the machine or set a sleep timer > > sleep $((15*60+30)); xrandr -q > > to check the screen setup while the screen is in power saving mode (the commad > waits 15.5 minutes and the dumps the setup. You might also wait less long and > on a second konsole run "xset dpms force off" to activate screen powersaving > immediately) > > Post the output and a comparing "xrandr -q" without powersaving for > confirmation of the assumption. > > -- > You are receiving this mail because: > You reported the bug.
I got the first comment ;-) Please also don't fullquote in mails to the bugtracker. I do not think that either kscreen or krandr would bind xdmps to a screen reconfiguration (and certainly not by default), yet you might disable them in "kcmshell4 kded" (reasonably you'll have only one of them installed - and that'd better be kscreen, krandr is deprecated) To know what happens (screen unregisters or is configured off) one would have to see the "xrandr -q" dumps. To pot. workaround the issue, one would further have to determine for what level of powersaving this happens, turn off screen energy saving in "kcmshell4 powerdevilprofilesconfig" and setup the saving times in some ~/.xprofile using "xset" there're 4 energy states ==================== xset dpms force standby xset dpms force suspend xset dpms force off ---- xset dpms force on Try running each (execpt. obviously "on") and check whether that triggers a screen resize. Marking downstream by comment #2, the bug can still be assigned to the KDE component that triggers this behavior (if and when determined)
Hello Thomas, thanks for this helpfull Information! When I enter the command "xset dpms force standby" into terminal then is my middle and my left Display after Standby with all my open App-Windows here. Thats great! All Windows from this two Displays are on his correct place. Only the third Monitor (right side) is yet with the same failure. The Windows from my third Monitor are after Standby moved into my middle Display But this Situation is better than before! But I don`t know where I can find the ~/.xprofile Can you help me please to setup the saving times in some ~/.xprofile using "xset" My Operating System is Kubuntu 13.10 x64 Best Regards Martin Montag, 11. November 2013, 18:40:35 - Thomas Lübking schrieb: > https://bugs.kde.org/show_bug.cgi?id=327442 > > Thomas Lübking <thomas.luebking@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |DOWNSTREAM > > --- Comment #4 from Thomas Lübking <thomas.luebking@gmail.com> --- > I got the first comment ;-) > Please also don't fullquote in mails to the bugtracker. > > > I do not think that either kscreen or krandr would bind xdmps to a screen > reconfiguration (and certainly not by default), yet you might disable them in > "kcmshell4 kded" (reasonably you'll have only one of them installed - and > that'd better be kscreen, krandr is deprecated) > > To know what happens (screen unregisters or is configured off) one would have > to see the "xrandr -q" dumps. > > To pot. workaround the issue, one would further have to determine for what > level of powersaving this happens, turn off screen energy saving in "kcmshell4 > powerdevilprofilesconfig" and setup the saving times in some ~/.xprofile using > "xset" > > there're 4 energy states > ==================== > xset dpms force standby > xset dpms force suspend > xset dpms force off > ---- > xset dpms force on > > Try running each (execpt. obviously "on") and check whether that triggers a > screen resize. > > Marking downstream by comment #2, the bug can still be assigned to the KDE > component that triggers this behavior (if and when determined) > > -- > You are receiving this mail because: > You reported the bug.
if you only intend to use this from KDE, do: mkdir -p "`kde4-config --localprefix`/env" echo -e '#!/bin/sh\nxset dpms 360 0 0' > "`kde4-config --localprefix`/env/set_dpms.sh" chmod +x "`kde4-config --localprefix`/env/set_dpms.sh" Those are three lines, ensure bugzilla didn't break them somehow. It will create a local env dir parsed on login, write a new script to set dpms standby after 360 seconds but never "suspend" or "off" and with the last line make it executable If you run "`kde4-config --localprefix`/env/set_dpms.sh" afterwards and then xset -q it should say DPMS (Energy Star): Standby: 360 Suspend: 0 Off: 0 DPMS is Enabled Monitor is On
I am sorry. This Script works but the App-Windows from my middle display moves now again to the left display after standbymode. What can I do?
But not all windows moves
Define "not all windows" and *most important* check the "xrandr -q" output before, while and after the standby/suspend/off state, so that we do not operate on wild assumptions about what happens.
Hi Thomas! Here my complete xrandr -q Output from before/while and after suspend/standby/off state. Xrandr -q before suspend/standby/off state martin@martin-linux:~$ xrandr -q Screen 0: minimum 320 x 200, current 6400 x 1080, maximum 6400 x 2560 DFP1 connected primary 2560x1080+1920+0 (normal left inverted right x axis y axis) 677mm x 290mm 2560x1080 60.0*+ 1920x1080 50.0 59.9 50.0 60.0 1776x1000 50.0 59.9 50.0 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 60.0 1280x960 60.0 1152x864 60.0 1280x768 60.0 1280x720 50.0 59.9 1024x768 60.0 1152x648 50.0 59.9 800x600 60.0 720x480 60.0 640x480 60.0 DFP2 disconnected (normal left inverted right x axis y axis) DFP3 disconnected (normal left inverted right x axis y axis) DFP4 disconnected (normal left inverted right x axis y axis) DFP5 disconnected (normal left inverted right x axis y axis) DFP6 connected 1920x1080+4480+0 (normal left inverted right x axis y axis) 530mm x 300mm 1920x1080 60.0*+ 1600x1200 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1280x800 59.8 1280x768 59.8 1280x720 59.8 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 DFP7 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 530mm x 300mm 1920x1080 60.0*+ 1600x1200 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1280x800 59.8 1280x768 59.8 1280x720 59.8 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 CRT1 disconnected (normal left inverted right x axis y axis) martin@martin-linux:~$ Xrandr -q while suspend/standby/off state martin@martin-linux:~$ sleep 85; xrandr -q Screen 0: minimum 320 x 200, current 6400 x 1080, maximum 6400 x 2560 DFP1 connected primary 2560x1080+1920+0 (normal left inverted right x axis y axis) 677mm x 290mm 2560x1080 60.0*+ 1920x1080 50.0 59.9 50.0 60.0 1776x1000 50.0 59.9 50.0 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 60.0 1280x960 60.0 1152x864 60.0 1280x768 60.0 1280x720 50.0 59.9 1024x768 60.0 1152x648 50.0 59.9 800x600 60.0 720x480 60.0 640x480 60.0 DFP2 disconnected (normal left inverted right x axis y axis) DFP3 disconnected (normal left inverted right x axis y axis) DFP4 disconnected (normal left inverted right x axis y axis) DFP5 disconnected (normal left inverted right x axis y axis) DFP6 connected 1920x1080+4480+0 (normal left inverted right x axis y axis) 530mm x 300mm 1920x1080 60.0*+ 1600x1200 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1280x800 59.8 1280x768 59.8 1280x720 59.8 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 DFP7 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 530mm x 300mm 1920x1080 60.0*+ 1600x1200 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1280x800 59.8 1280x768 59.8 1280x720 59.8 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 CRT1 disconnected (normal left inverted right x axis y axis) martin@martin-linux:~$ Xrandr -q after suspend/standby/off state martin@martin-linux:~$ xrandr -q Screen 0: minimum 320 x 200, current 6400 x 1080, maximum 6400 x 2560 DFP1 connected primary 2560x1080+1920+0 (normal left inverted right x axis y axis) 677mm x 290mm 2560x1080 60.0*+ 1920x1080 50.0 59.9 50.0 60.0 1776x1000 50.0 59.9 50.0 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 60.0 1280x960 60.0 1152x864 60.0 1280x768 60.0 1280x720 50.0 59.9 1024x768 60.0 1152x648 50.0 59.9 800x600 60.0 720x480 60.0 640x480 60.0 DFP2 disconnected (normal left inverted right x axis y axis) DFP3 disconnected (normal left inverted right x axis y axis) DFP4 disconnected (normal left inverted right x axis y axis) DFP5 disconnected (normal left inverted right x axis y axis) DFP6 connected 1920x1080+4480+0 (normal left inverted right x axis y axis) 530mm x 300mm 1920x1080 60.0*+ 1600x1200 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1280x800 59.8 1280x768 59.8 1280x720 59.8 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 DFP7 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 530mm x 300mm 1920x1080 60.0*+ 1600x1200 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1280x800 59.8 1280x768 59.8 1280x720 59.8 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 CRT1 disconnected (normal left inverted right x axis y axis) martin@martin-linux:~$ About my second Information that not all App-Windows are moved into my left display, I explain so: When the line into the set_dpms.sh is "xset dpms 360 0 0" then all my windows from my middle Display moves into my left Display. When the Line into the set_dpms.sh is "xset dpms 0 360 0" then not all my windows from my middle Display moves into my left Display. Chromium Browser was correct on my Display but only the Kate Editor was moved into the left Display. I dont know why? I tested this more times and with other Programs. Some small windows was moved into my left Display by this last setting. Thanks for your help!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!