[opensuse] Plasma problem: energy saving not activated
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem? thal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Alex Bihlmaier <thalunil@kallisti.at> [03-29-20 05:04]:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
I did but do not now. But, your question is quite vague, missing associated version and hardware information, so my answer doesn't really mean anything. more meaningful, yesterday's release, 20200326, resolved xset's failure to turn off the lsd backlight, with NVIDIA GF106 [GeForce GTS 450] and nvidia v: 390.132 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 3/29/20 5:03 AM, Alex Bihlmaier wrote:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
thal
I see that once in a while, but not consistently. I'd say once every week or so. But then activating the computer by using it for something, and then leaving it, it will turn off as it should. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 3/29/20 2:36 PM, Doug McGarrett wrote:
On 3/29/20 5:03 AM, Alex Bihlmaier wrote:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
thal
I see that once in a while, but not consistently. I'd say once every week or so. But then activating the computer by using it for something, and then leaving it, it will turn off as it should. --doug
This is my message after upgrading my tumbleweed system this afternoon, 29 March. It now appears that the display does not turn off after being left for over an hour. I would appreciate any input that would tell me how to fix this. I am not a programmer, so please be specific and simple! (I don't know what the "configured period of time" is--I was relying on whatever the OS thought it ought to be--something like 20 minutes, I suspect, but I never timed it.) If there is a file I should look at, (and perhaps modify) please specify. I will post anything here if I can't figure it out. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
The chrome browser, and possibly others, may keep a screen from going into power saving if a media is being played somewhere on an active page. For example, video/audio adverts that auto-play and auto-rollover can cause this. You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole: xset dpms force suspend The plasma settings for how long to wait can be found in: System Settings -> Power Management -> Energy Saving Michael On Monday 30 March 2020, Doug McGarrett wrote:
On 3/29/20 2:36 PM, Doug McGarrett wrote:
On 3/29/20 5:03 AM, Alex Bihlmaier wrote:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
thal
I see that once in a while, but not consistently. I'd say once every week or so. But then activating the computer by using it for something, and then leaving it, it will turn off as it should. --doug
This is my message after upgrading my tumbleweed system this afternoon, 29 March. It now appears that the display does not turn off after being left for over an hour. I would appreciate any input that would tell me how to fix this. I am not a programmer, so please be specific and simple! (I don't know what the "configured period of time" is--I was relying on whatever the OS thought it ought to be--something like 20 minutes, I suspect, but I never timed it.) If there is a file I should look at, (and perhaps modify) please specify. I will post anything here if I can't figure it out.
--doug
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 3/30/20 2:53 AM, Michael Hamilton wrote:
The chrome browser, and possibly others, may keep a screen from going into power saving if a media is being played somewhere on an active page. For example, video/audio adverts that auto-play and auto-rollover can cause this.
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
Michael
/snip/
On Monday 30 March 2020, Doug McGarrett wrote:
On 3/29/20 2:36 PM, Doug McGarrett wrote:
I see that once in a while, but not consistently. I'd say once every week or so. But then activating the computer by using it for something, and then leaving it, it will turn off as it should. --doug
This is my message after upgrading my tumbleweed system this afternoon, 29 March. It now appears that the display does not turn off after being left for over an hour. I would appreciate any input that would tell me how to fix this. I am not a programmer, so please be specific and simple! (I don't know what the "configured period of time" is--I was relying on whatever the OS thought it ought to be--something like 20 minutes, I suspect, but I never timed it.) If there is a file I should look at, (and perhaps modify) please specify. I will post anything here if I can't figure it out.
--doug
I followed the instructions above--
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
And running the command on a root konsole, the screen goes black, as it should, and rolling the mouse brings it back to like. The system settings call for a ten minute blackout. I'll check that right now: (Starting 10:48 PM.) Screen came back to life in about one minute. Anyone have a solution, please? --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Doug McGarrett <dmcgarrett@optonline.net> [03-30-20 22:51]:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
The chrome browser, and possibly others, may keep a screen from going into power saving if a media is being played somewhere on an active page. For example, video/audio adverts that auto-play and auto-rollover can cause this.
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
Michael
/snip/
On Monday 30 March 2020, Doug McGarrett wrote:
On 3/29/20 2:36 PM, Doug McGarrett wrote:
I see that once in a while, but not consistently. I'd say once every week or so. But then activating the computer by using it for something, and then leaving it, it will turn off as it should. --doug
This is my message after upgrading my tumbleweed system this afternoon, 29 March. It now appears that the display does not turn off after being left for over an hour. I would appreciate any input that would tell me how to fix this. I am not a programmer, so please be specific and simple! (I don't know what the "configured period of time" is--I was relying on whatever the OS thought it ought to be--something like 20 minutes, I suspect, but I never timed it.) If there is a file I should look at, (and perhaps modify) please specify. I will post anything here if I can't figure it out.
--doug
I followed the instructions above--
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
And running the command on a root konsole, the screen goes black, as it should, and rolling the mouse brings it back to like. The system settings call for a ten minute blackout. I'll check that right now: (Starting 10:48 PM.) Screen came back to life in about one minute.
Anyone have a solution, please?
--doug
I use: xset +dpms xset dpms 300 400 500 xset s on sleep .3;xset dpms force off -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday 31 March 2020, Doug McGarrett wrote:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
The chrome browser, and possibly others, may keep a screen from going into power saving if a media is being played somewhere on an active page. For example, video/audio adverts that auto-play and auto-rollover can cause this.
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
Michael
/snip/
On Monday 30 March 2020, Doug McGarrett wrote:
On 3/29/20 2:36 PM, Doug McGarrett wrote:
I see that once in a while, but not consistently. I'd say once every week or so. But then activating the computer by using it for something, and then leaving it, it will turn off as it should. --doug
This is my message after upgrading my tumbleweed system this afternoon, 29 March. It now appears that the display does not turn off after being left for over an hour. I would appreciate any input that would tell me how to fix this. I am not a programmer, so please be specific and simple! (I don't know what the "configured period of time" is--I was relying on whatever the OS thought it ought to be--something like 20 minutes, I suspect, but I never timed it.) If there is a file I should look at, (and perhaps modify) please specify. I will post anything here if I can't figure it out.
--doug
I followed the instructions above--
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
And running the command on a root konsole, the screen goes black, as it should, and rolling the mouse brings it back to like. The system settings call for a ten minute blackout. I'll check that right now: (Starting 10:48 PM.) Screen came back to life in about one minute.
Anyone have a solution, please?
--doug
The manual xset command should have caused the display to stay blank indefinitely So if it woke up after 1 minute it's likely something software or hardware on the system is doing something to wake things up. So you need to figure out what that is. I'm not 100% sure on the best approach, but the plasma sub-system that does power management is called powerdevil. It seems to be responsible for inhibiting and restoring display power management. Powerdevil writes to the system journal and can be monitored with journalctrl. journalctl -f This will tail the journal contiguously and can be exited by using control-C or you can review the past n entries or entries sine the last boot: journalctl -n 1000 journalctl --boot For example, here are some journal entries where powerdevil has inhibited the DPMS (Display Power Management System) while briefly I briefly watched a video in chrome: ... org_kde_powerdevil[2931]: powerdevil: Enforcing inhibition from ":1.74" "/usr/bin/google-chrome-beta" with cookie 22 and reason "Playing audio" ... org_kde_powerdevil[2931]: powerdevil: Scheduling inhibition from ":1.19" "/usr/bin/google-chrome-beta" with cookie 23 and reason "Video Wake Lock" ... org_kde_powerdevil[2931]: powerdevil: Disabling DPMS due to inhibition When I close the chrome tab, powerdevil restored DPMS ... org_kde_powerdevil[2931]: powerdevil: Releasing inhibition with cookie 20 ... org_kde_powerdevil[2931]: powerdevil: Restoring DPMS features after inhibition release As I mentioned earlier, it could be that some piece of software, such as chrome is preventing dpms from kicking in due to media being played. Running journalctl in a root shell or via sudo would likely give you even more info (not necessarily all useful): sudo journalctl -f The last time I had a similar problem I had left a chrome tab active on a page that auto played adverts. If it's not powerdevil inhibiting DPMS, then I'm at a bit of a loss. In that case I might try a different mouse to see if it's some kind of sensitivity to jittery input or vibration. Or start selectively shutting down any likely software candidates - such as a music player or alarm clock. BTW, I'm on TW 20200326 and DPMS seems to be working fine (with the proprietary nvidia driver 440.64-24). Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 3/31/20 12:09 AM, Michael Hamilton wrote:
On Tuesday 31 March 2020, Doug McGarrett wrote:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
The chrome browser, and possibly others, may keep a screen from going into power saving if a media is being played somewhere on an active page. For example, video/audio adverts that auto-play and auto-rollover can cause this.
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
Michael
/snip/
On Monday 30 March 2020, Doug McGarrett wrote:
On 3/29/20 2:36 PM, Doug McGarrett wrote:
I see that once in a while, but not consistently. I'd say once every week or so. But then activating the computer by using it for something, and then leaving it, it will turn off as it should. --doug
This is my message after upgrading my tumbleweed system this afternoon, 29 March. It now appears that the display does not turn off after being left for over an hour. I would appreciate any input that would tell me how to fix this. I am not a programmer, so please be specific and simple! (I don't know what the "configured period of time" is--I was relying on whatever the OS thought it ought to be--something like 20 minutes, I suspect, but I never timed it.) If there is a file I should look at, (and perhaps modify) please specify. I will post anything here if I can't figure it out.
--doug
I followed the instructions above--
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
And running the command on a root konsole, the screen goes black, as it should, and rolling the mouse brings it back to like. The system settings call for a ten minute blackout. I'll check that right now: (Starting 10:48 PM.) Screen came back to life in about one minute.
Anyone have a solution, please?
--doug
The manual xset command should have caused the display to stay blank indefinitely So if it woke up after 1 minute it's likely something software or hardware on the system is doing something to wake things up. So you need to figure out what that is.
I'm not 100% sure on the best approach, but the plasma sub-system that does power management is called powerdevil. It seems to be responsible for inhibiting and restoring display power management. Powerdevil writes to the system journal and can be monitored with journalctrl.
journalctl -f
This will tail the journal contiguously and can be exited by using control-C or you can review the past n entries or entries sine the last boot:
journalctl -n 1000 journalctl --boot
For example, here are some journal entries where powerdevil has inhibited the DPMS (Display Power Management System) while briefly I briefly watched a video in chrome:
... org_kde_powerdevil[2931]: powerdevil: Enforcing inhibition from ":1.74" "/usr/bin/google-chrome-beta" with cookie 22 and reason "Playing audio" ... org_kde_powerdevil[2931]: powerdevil: Scheduling inhibition from ":1.19" "/usr/bin/google-chrome-beta" with cookie 23 and reason "Video Wake Lock" ... org_kde_powerdevil[2931]: powerdevil: Disabling DPMS due to inhibition
When I close the chrome tab, powerdevil restored DPMS
... org_kde_powerdevil[2931]: powerdevil: Releasing inhibition with cookie 20 ... org_kde_powerdevil[2931]: powerdevil: Restoring DPMS features after inhibition release
As I mentioned earlier, it could be that some piece of software, such as chrome is preventing dpms from kicking in due to media being played.
Running journalctl in a root shell or via sudo would likely give you even more info (not necessarily all useful):
sudo journalctl -f
The last time I had a similar problem I had left a chrome tab active on a page that auto played adverts. If it's not powerdevil inhibiting DPMS, then I'm at a bit of a loss. In that case I might try a different mouse to see if it's some kind of sensitivity to jittery input or vibration. Or start selectively shutting down any likely software candidates - such as a music player or alarm clock.
BTW, I'm on TW 20200326 and DPMS seems to be working fine (with the proprietary nvidia driver 440.64-24).
Michael
Well, I'm not using a chrome tab, whatever that is, and I use Firefox as my browser. I don't know what DPMS is, and I don't think I invoked it, or if I did it was by accident. Please adopt me as a wayfayrer on unmapped streets. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday 31 March 2020, Doug McGarrett wrote:
On 3/31/20 12:09 AM, Michael Hamilton wrote:
On Tuesday 31 March 2020, Doug McGarrett wrote:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
The chrome browser, and possibly others, may keep a screen from going into power saving if a media is being played somewhere on an active page. For example, video/audio adverts that auto-play and auto-rollover can cause this.
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
Michael
/snip/
On Monday 30 March 2020, Doug McGarrett wrote:
On 3/29/20 2:36 PM, Doug McGarrett wrote:
> I see that once in a while, but not consistently. I'd say once every week or so. But then activating the computer by using it for something, and then leaving it, it will turn off as it should. --doug
This is my message after upgrading my tumbleweed system this afternoon, 29 March. It now appears that the display does not turn off after being left for over an hour. I would appreciate any input that would tell me how to fix this. I am not a programmer, so please be specific and simple! (I don't know what the "configured period of time" is--I was relying on whatever the OS thought it ought to be--something like 20 minutes, I suspect, but I never timed it.) If there is a file I should look at, (and perhaps modify) please specify. I will post anything here if I can't figure it out.
--doug
I followed the instructions above--
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
And running the command on a root konsole, the screen goes black, as it should, and rolling the mouse brings it back to like. The system settings call for a ten minute blackout. I'll check that right now: (Starting 10:48 PM.) Screen came back to life in about one minute.
Anyone have a solution, please?
--doug
The manual xset command should have caused the display to stay blank indefinitely So if it woke up after 1 minute it's likely something software or hardware on the system is doing something to wake things up. So you need to figure out what that is.
I'm not 100% sure on the best approach, but the plasma sub-system that does power management is called powerdevil. It seems to be responsible for inhibiting and restoring display power management. Powerdevil writes to the system journal and can be monitored with journalctrl.
journalctl -f
This will tail the journal contiguously and can be exited by using control-C or you can review the past n entries or entries sine the last boot:
journalctl -n 1000 journalctl --boot
For example, here are some journal entries where powerdevil has inhibited the DPMS (Display Power Management System) while briefly I briefly watched a video in chrome:
... org_kde_powerdevil[2931]: powerdevil: Enforcing inhibition from ":1.74" "/usr/bin/google-chrome-beta" with cookie 22 and reason "Playing audio" ... org_kde_powerdevil[2931]: powerdevil: Scheduling inhibition from ":1.19" "/usr/bin/google-chrome-beta" with cookie 23 and reason "Video Wake Lock" ... org_kde_powerdevil[2931]: powerdevil: Disabling DPMS due to inhibition
When I close the chrome tab, powerdevil restored DPMS
... org_kde_powerdevil[2931]: powerdevil: Releasing inhibition with cookie 20 ... org_kde_powerdevil[2931]: powerdevil: Restoring DPMS features after inhibition release
As I mentioned earlier, it could be that some piece of software, such as chrome is preventing dpms from kicking in due to media being played.
Running journalctl in a root shell or via sudo would likely give you even more info (not necessarily all useful):
sudo journalctl -f
The last time I had a similar problem I had left a chrome tab active on a page that auto played adverts. If it's not powerdevil inhibiting DPMS, then I'm at a bit of a loss. In that case I might try a different mouse to see if it's some kind of sensitivity to jittery input or vibration. Or start selectively shutting down any likely software candidates - such as a music player or alarm clock.
BTW, I'm on TW 20200326 and DPMS seems to be working fine (with the proprietary nvidia driver 440.64-24).
Michael
Well, I'm not using a chrome tab, whatever that is, and I use Firefox as my browser. I don't know what DPMS is, and I don't think I invoked it, or if I did it was by accident. Please adopt me as a wayfayrer on unmapped streets.
--doug
What applies to the chrome browser likely applies to them all. Some of the more recent replies also describe issues with other browsers and music players. DPMS is the standard that allows software to put the monitor into power saving. For a starter on DPMS - see: https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling I would add TW is not a distribution that I would recommend unless you are keen on getting under the hood and using google to figure things out. It's bleeding edge emphasis often introduces little annoyances, it's the price for playing with the latest stuff. Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 3/31/20 2:22 AM, Michael Hamilton wrote:
On Tuesday 31 March 2020, Doug McGarrett wrote:
On 3/31/20 12:09 AM, Michael Hamilton wrote:
On Tuesday 31 March 2020, Doug McGarrett wrote:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
The chrome browser, and possibly others, may keep a screen from going into power saving if a media is being played somewhere on an active page. For example, video/audio adverts that auto-play and auto-rollover can cause this.
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
Michael
/snip/
On Monday 30 March 2020, Doug McGarrett wrote:
On 3/29/20 2:36 PM, Doug McGarrett wrote:
>> > I see that once in a while, but not consistently. I'd say once every week or so. > But then activating the computer by using it for something, and then leaving it, it will turn off as it should. > --doug
This is my message after upgrading my tumbleweed system this afternoon, 29 March. It now appears that the display does not turn off after being left for over an hour. I would appreciate any input that would tell me how to fix this. I am not a programmer, so please be specific and simple! (I don't know what the "configured period of time" is--I was relying on whatever the OS thought it ought to be--something like 20 minutes, I suspect, but I never timed it.) If there is a file I should look at, (and perhaps modify) please specify. I will post anything here if I can't figure it out.
--doug
I followed the instructions above--
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
And running the command on a root konsole, the screen goes black, as it should, and rolling the mouse brings it back to like. The system settings call for a ten minute blackout. I'll check that right now: (Starting 10:48 PM.) Screen came back to life in about one minute.
Anyone have a solution, please?
--doug
The manual xset command should have caused the display to stay blank indefinitely So if it woke up after 1 minute it's likely something software or hardware on the system is doing something to wake things up. So you need to figure out what that is.
I'm not 100% sure on the best approach, but the plasma sub-system that does power management is called powerdevil. It seems to be responsible for inhibiting and restoring display power management. Powerdevil writes to the system journal and can be monitored with journalctrl.
journalctl -f
This will tail the journal contiguously and can be exited by using control-C or you can review the past n entries or entries sine the last boot:
journalctl -n 1000 journalctl --boot
For example, here are some journal entries where powerdevil has inhibited the DPMS (Display Power Management System) while briefly I briefly watched a video in chrome:
... org_kde_powerdevil[2931]: powerdevil: Enforcing inhibition from ":1.74" "/usr/bin/google-chrome-beta" with cookie 22 and reason "Playing audio" ... org_kde_powerdevil[2931]: powerdevil: Scheduling inhibition from ":1.19" "/usr/bin/google-chrome-beta" with cookie 23 and reason "Video Wake Lock" ... org_kde_powerdevil[2931]: powerdevil: Disabling DPMS due to inhibition
When I close the chrome tab, powerdevil restored DPMS
... org_kde_powerdevil[2931]: powerdevil: Releasing inhibition with cookie 20 ... org_kde_powerdevil[2931]: powerdevil: Restoring DPMS features after inhibition release
As I mentioned earlier, it could be that some piece of software, such as chrome is preventing dpms from kicking in due to media being played.
Running journalctl in a root shell or via sudo would likely give you even more info (not necessarily all useful):
sudo journalctl -f
The last time I had a similar problem I had left a chrome tab active on a page that auto played adverts. If it's not powerdevil inhibiting DPMS, then I'm at a bit of a loss. In that case I might try a different mouse to see if it's some kind of sensitivity to jittery input or vibration. Or start selectively shutting down any likely software candidates - such as a music player or alarm clock.
BTW, I'm on TW 20200326 and DPMS seems to be working fine (with the proprietary nvidia driver 440.64-24).
Michael
Well, I'm not using a chrome tab, whatever that is, and I use Firefox as my browser. I don't know what DPMS is, and I don't think I invoked it, or if I did it was by accident. Please adopt me as a wayfayrer on unmapped streets.
--doug
What applies to the chrome browser likely applies to them all. Some of the more recent replies also describe issues with other browsers and music players.
DPMS is the standard that allows software to put the monitor into power saving. For a starter on DPMS - see:
https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling
I would add TW is not a distribution that I would recommend unless you are keen on getting under the hood and using google to figure things out. It's bleeding edge emphasis often introduces little annoyances, it's the price for playing with the latest stuff.
Michael
Michael, I selected TW for its rolling release capabilities; I do not wish to have to reinstall the OS every few months, or, in fact, ever. It looks now that I have been bitten by some bug in the latest download, and I hope somebody finds the bug and stomps on it soon! I am not a programmer, and I don't know my way around the operating system, but I'm not afraid of the root console when it's required to enter a command. Is it possible to edit the DPMS command in order to make it work properly, and if so, how? When I use "find" fpr DPMS, I find two outputs, one says "on" the other says "off" and they are both dated today at the same time--one is called file:///sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-1/dpms and the other is called file:///sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-2/dpms. --doug PS: Is someone watching to see if this is fixed, and if so, how would I know? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday 01 April 2020, Doug McGarrett wrote:
On 3/31/20 2:22 AM, Michael Hamilton wrote:
On Tuesday 31 March 2020, Doug McGarrett wrote:
On 3/31/20 12:09 AM, Michael Hamilton wrote:
On Tuesday 31 March 2020, Doug McGarrett wrote:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
The chrome browser, and possibly others, may keep a screen from going into power saving if a media is being played somewhere on an active page. For example, video/audio adverts that auto-play and auto-rollover can cause this.
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
Michael
/snip/
On Monday 30 March 2020, Doug McGarrett wrote: > > On 3/29/20 2:36 PM, Doug McGarrett wrote:
>>> >> I see that once in a while, but not consistently. I'd say once every week or so. >> But then activating the computer by using it for something, and then leaving it, it will turn off as it should. >> --doug > > This is my message after upgrading my tumbleweed system this afternoon, 29 March. It now appears that the display does > not turn off after being left for over an hour. I would appreciate any input that would tell me how to fix this. > I am not a programmer, so please be specific and simple! (I don't know what the "configured period of time" is--I was > relying on whatever the OS thought it ought to be--something like 20 minutes, I suspect, but I never timed it.) If there > is a file I should look at, (and perhaps modify) please specify. I will post anything here if I can't figure it out. > > --doug >
I followed the instructions above--
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
And running the command on a root konsole, the screen goes black, as it should, and rolling the mouse brings it back to like. The system settings call for a ten minute blackout. I'll check that right now: (Starting 10:48 PM.) Screen came back to life in about one minute.
Anyone have a solution, please?
--doug
The manual xset command should have caused the display to stay blank indefinitely So if it woke up after 1 minute it's likely something software or hardware on the system is doing something to wake things up. So you need to figure out what that is.
I'm not 100% sure on the best approach, but the plasma sub-system that does power management is called powerdevil. It seems to be responsible for inhibiting and restoring display power management. Powerdevil writes to the system journal and can be monitored with journalctrl.
journalctl -f
This will tail the journal contiguously and can be exited by using control-C or you can review the past n entries or entries sine the last boot:
journalctl -n 1000 journalctl --boot
For example, here are some journal entries where powerdevil has inhibited the DPMS (Display Power Management System) while briefly I briefly watched a video in chrome:
... org_kde_powerdevil[2931]: powerdevil: Enforcing inhibition from ":1.74" "/usr/bin/google-chrome-beta" with cookie 22 and reason "Playing audio" ... org_kde_powerdevil[2931]: powerdevil: Scheduling inhibition from ":1.19" "/usr/bin/google-chrome-beta" with cookie 23 and reason "Video Wake Lock" ... org_kde_powerdevil[2931]: powerdevil: Disabling DPMS due to inhibition
When I close the chrome tab, powerdevil restored DPMS
... org_kde_powerdevil[2931]: powerdevil: Releasing inhibition with cookie 20 ... org_kde_powerdevil[2931]: powerdevil: Restoring DPMS features after inhibition release
As I mentioned earlier, it could be that some piece of software, such as chrome is preventing dpms from kicking in due to media being played.
Running journalctl in a root shell or via sudo would likely give you even more info (not necessarily all useful):
sudo journalctl -f
The last time I had a similar problem I had left a chrome tab active on a page that auto played adverts. If it's not powerdevil inhibiting DPMS, then I'm at a bit of a loss. In that case I might try a different mouse to see if it's some kind of sensitivity to jittery input or vibration. Or start selectively shutting down any likely software candidates - such as a music player or alarm clock.
BTW, I'm on TW 20200326 and DPMS seems to be working fine (with the proprietary nvidia driver 440.64-24).
Michael
Well, I'm not using a chrome tab, whatever that is, and I use Firefox as my browser. I don't know what DPMS is, and I don't think I invoked it, or if I did it was by accident. Please adopt me as a wayfayrer on unmapped streets.
--doug
What applies to the chrome browser likely applies to them all. Some of the more recent replies also describe issues with other browsers and music players.
DPMS is the standard that allows software to put the monitor into power saving. For a starter on DPMS - see:
https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling
I would add TW is not a distribution that I would recommend unless you are keen on getting under the hood and using google to figure things out. It's bleeding edge emphasis often introduces little annoyances, it's the price for playing with the latest stuff.
Michael
Michael, I selected TW for its rolling release capabilities; I do not wish to have to reinstall the OS every few months, or, in fact, ever. It looks now that I have been bitten by some bug in the latest download, and I hope somebody finds the bug and stomps on it soon! I am not a programmer, and I don't know my way around the operating system, but I'm not afraid of the root console when it's required to enter a command. Is it possible to edit the DPMS command in order to make it work properly, and if so, how? When I use "find" fpr DPMS, I find two outputs, one says "on" the other says "off" and they are both dated today at the same time--one is called file:///sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-1/dpms and the other is called file:///sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-2/dpms. --doug PS: Is someone watching to see if this is fixed, and if so, how would I know?
I'm afraid there may be no magic bullets. You are experiencing a problem that some aren't seeing. It may be a bug, it may be a configuration issue, it might be being cased by a browser, video player, audio player, media editor, game or some other piece of software that decides to inhibit power saving. Using the find command in this way isn't appropriate. DPMS is a low level internal way for PC's to control monitors. The X11 windows system handles DPMS for us - we can view/change X11's behaviour with the xset command (man xset) and X11/xorg configuration. KDE/plasma power management sits about X11 and provides another layer of abstraction with services such as powerdevil - which are controlled via the plasma desktop System Settings. It's had to tell whats going on without investigating at the issue systematically. You need to gather more info, and in order to do that you may have to be prepared to do some googling and reading based around the possibilities people have already raised in their replies before you can sensibly approach the problem. You could google plasma powerdevil and see how that relates. You could google X11 DPMS and find out what that is. You could google linux journalctl and see how that allows you to retrieve diagnostic messages about what is going on in the operating system. You could google firefox media.autoplay.enabled At the moment people are only guessing that your problem might be related to the browser (firefox or any other) playing media. It may have nothing to do with your case. You could test that by shutting down firefox and seeing if the problem no longer occurs. Maybe it's being caused by an audio player or media editor. Progressively reducing what's running or running the desktop with no programs running might narrow this down. Does an empty first logged in desktop work properly? As I've already mentioned KDE plasma powerdevil logs to the journal when some programs inhibit powersaving - so is there anything relevant in the journal? I gave you some command lines to check that. If you can pin this down to an actual fault in plasma or some other component you should raise a bug at https://bugzilla.opensuse.org/index.cgi You could also search for existing bugs at the bugzilla site. This advice is not just true for TW, or Linux, a similar approach with different OS tools would be required to track down such a problem in Windows too. You have to be prepared to learn a bit about the OS in order to be able to work with it and converse with others about it. Alternatively you put up with faults that are too complex to bother with and see if a future release fixes them. TW weed as a rolling release has the advantage that you get all the latest stuff including the latest bugs (some of which will be from upstream projects that may not feed through fixes to TW for some time). A non-rolling release such as Leap has the advantage of long periods of stability but older software. I've never found Leap upgrades to be difficult - I don't see that as an issue, older software is the issue for me). Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/04/2020 02.14, Doug McGarrett wrote:
On 3/31/20 2:22 AM, Michael Hamilton wrote:
On Tuesday 31 March 2020, Doug McGarrett wrote:
...
Michael, I selected TW for its rolling release capabilities; I do not wish to have to reinstall the OS every few months, or, in fact, ever.
But you have to be ready for sudden changes, and you have to be able to investigate them on your own.
It looks now that I have been bitten by some bug in the latest download, and I hope somebody finds the bug and stomps on it soon! I am not a programmer, and I don't know my way around the operating system, but I'm not afraid of the root console when it's required to enter a command. Is it possible to edit the DPMS command in order to make it work properly, and if so, how?
DPMS is not a command, it is a protocol or standard. The commands were explained in another post by Michael or Patrick -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.1 (Legolas))
On 31/03/2020 06.47, Doug McGarrett wrote:
Well, I'm not using a chrome tab, whatever that is,
Chrome is a a popular web browser made by Google. It uses tabs, same as firefox - see menu file / new tab on firefox.
and I use Firefox as my browser. I don't know what DPMS is, and I don't think I invoked it, or if I did it was by accident.
Yes, you are using DPMS. Rather your monitor is using it, as it is a standard. <https://en.wikipedia.org/wiki/VESA_Display_Power_Management_Signaling> -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 31/03/2020 06.09, Michael Hamilton wrote:
On Tuesday 31 March 2020, Doug McGarrett wrote:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
...
I'm not 100% sure on the best approach, but the plasma sub-system that does power management is called powerdevil. It seems to be responsible for inhibiting and restoring display power management. Powerdevil writes to the system journal and can be monitored with journalctrl.
...
The last time I had a similar problem I had left a chrome tab active on a page that auto played adverts.
Wow, that's perverted. Forcing the screen on to display the adverts. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Am Dienstag, 31. März 2020, 15:10:22 CEST schrieb Carlos E. R.:
The last time I had a similar problem I had left a chrome tab active on a page that auto played adverts.
Wow, that's perverted. Forcing the screen on to display the adverts.
Not at all. If I have any video running in a browser tab I want to the screen to stay on. Unfortunately that includes adverts as well. But that's where a sane ad blocker comes to play. Cheers, vinz. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/03/2020 17.32, Vinzenz Vietzke wrote:
Am Dienstag, 31. März 2020, 15:10:22 CEST schrieb Carlos E. R.:
The last time I had a similar problem I had left a chrome tab active on a page that auto played adverts.
Wow, that's perverted. Forcing the screen on to display the adverts.
Not at all. If I have any video running in a browser tab I want to the screen to stay on. Unfortunately that includes adverts as well. But that's where a sane ad blocker comes to play.
You are right, it is difficult to determine if the video is the main objective of the page (like youtube) or it comes inside an advert and is thus secondary. It is also difficult to convince a browser to not run any videos on page load. Yes, an ad blocker works - mostly, although some pages refuse to load if they detect it. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Tue, 31 Mar 2020 21:11:21 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
It is also difficult to convince a browser to not run any videos on page load.
In Firefox it's simply a matter of toggling the media.autoplay.enabled config item. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/03/2020 23.21, Dave Howorth wrote:
On Tue, 31 Mar 2020 21:11:21 +0200 "Carlos E. R." <> wrote:
It is also difficult to convince a browser to not run any videos on page load.
In Firefox it's simply a matter of toggling the media.autoplay.enabled config item.
That entry does not exist in mine. Instead, I have: media.autoplay.enabled.user-gestures-needed;true -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Wed, 1 Apr 2020 00:00:32 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 31/03/2020 23.21, Dave Howorth wrote:
On Tue, 31 Mar 2020 21:11:21 +0200 "Carlos E. R." <> wrote:
It is also difficult to convince a browser to not run any videos on page load.
In Firefox it's simply a matter of toggling the media.autoplay.enabled config item.
That entry does not exist in mine. Instead, I have:
media.autoplay.enabled.user-gestures-needed;true
I have that setting as well. So why do you say it is difficult if you've already done/got it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/04/2020 00.35, Dave Howorth wrote:
On Wed, 1 Apr 2020 00:00:32 +0200 "Carlos E. R." wrote:
On 31/03/2020 23.21, Dave Howorth wrote:
On Tue, 31 Mar 2020 21:11:21 +0200 "Carlos E. R." <> wrote:
It is also difficult to convince a browser to not run any videos on page load.
In Firefox it's simply a matter of toggling the media.autoplay.enabled config item.
That entry does not exist in mine. Instead, I have:
media.autoplay.enabled.user-gestures-needed;true
I have that setting as well. So why do you say it is difficult if you've already done/got it?
No,it is not the one that's needed, it is a different one. I have to create the right one and I don't remember how. In any case, it is a hidden setting. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.1 (Legolas))
On 3/31/20 6:00 PM, Carlos E. R. wrote:
On 31/03/2020 23.21, Dave Howorth wrote:
On Tue, 31 Mar 2020 21:11:21 +0200 "Carlos E. R." <> wrote:
It is also difficult to convince a browser to not run any videos on page load.
In Firefox it's simply a matter of toggling the media.autoplay.enabled config item.
That entry does not exist in mine. Instead, I have:
media.autoplay.enabled.user-gestures-needed;true
I don't seem to see anything like that. Please lead me thru the path to get to media.autoplay. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Doug McGarrett <dmcgarrett@optonline.net> [03-31-20 19:23]:
On 3/31/20 6:00 PM, Carlos E. R. wrote:
On 31/03/2020 23.21, Dave Howorth wrote:
On Tue, 31 Mar 2020 21:11:21 +0200 "Carlos E. R." <> wrote:
It is also difficult to convince a browser to not run any videos on page load.
In Firefox it's simply a matter of toggling the media.autoplay.enabled config item.
That entry does not exist in mine. Instead, I have:
media.autoplay.enabled.user-gestures-needed;true
I don't seem to see anything like that. Please lead me thru the path to get to media.autoplay.
open firefox type in following url: about:confg search for: autoplay negate the appropriate option. and PLEASE TRIM YOUR POSTS!. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [03-31-20 20:27]: [...]
open firefox type in following url: about:confg
s/about:confg/about:config/
search for: autoplay
negate the appropriate option.
and PLEASE TRIM YOUR POSTS!.
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 3/31/20 5:21 PM, Dave Howorth wrote:
On Tue, 31 Mar 2020 21:11:21 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
It is also difficult to convince a browser to not run any videos on page load.
In Firefox it's simply a matter of toggling the media.autoplay.enabled config item.
I can't find media.auotoplay how does one get there? --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/03/2020 04.47, Doug McGarrett wrote:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
I followed the instructions above--
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
And running the command on a root konsole,
I think you must use the same user as your session. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.1 (Legolas))
On 3/31/20 10:54 PM, Carlos E. R. wrote:
On 31/03/2020 04.47, Doug McGarrett wrote:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
I followed the instructions above--
> You can manually check if your screen is able to be put into power saving > by issuing an xset command in konsole: > > xset dpms force suspend > > The plasma settings for how long to wait can be found in: > > System Settings -> Power Management -> Energy Saving
And running the command on a root konsole,
I think you must use the same user as your session.
(A bit OT:) I am the only user on the system. When I select console, I get a login prompt Password: I seem to remember that when I installed the system the first (or almost first) screen I saw let me type in passwd and I gave it mine. I'm not afraid of goofs in the console-- the system is very good about catching them. I'm a child of PCLINUXOS and I'm allergic to SUDO. I think it's ridiculous! (I don't even remember how to get back to a user console, except it's NOT exit. Exit shuts the console down.) --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/04/2020 07.06, Doug McGarrett wrote:
On 3/31/20 10:54 PM, Carlos E. R. wrote:
On 31/03/2020 04.47, Doug McGarrett wrote:
On 3/30/20 2:53 AM, Michael Hamilton wrote:
I followed the instructions above--
You can manually check if your screen is able to be put into power saving by issuing an xset command in konsole:
xset dpms force suspend
The plasma settings for how long to wait can be found in:
System Settings -> Power Management -> Energy Saving
And running the command on a root konsole,
I think you must use the same user as your session.
(A bit OT:)
I am the only user on the system. When I select console, I get a login prompt Password: I seem to remember that when I installed the system the first (or almost first) screen I saw let me type in passwd and I gave it mine. I'm not afraid of goofs in the console-- the system is very good about catching them. I'm a child of PCLINUXOS and I'm allergic to SUDO. I think it's ridiculous! (I don't even remember how to get back to a user console, except it's NOT exit. Exit shuts the console down.) --doug
What I mean is that you must not run that command (xset) as root, but as "doug" or whatever is your user. Even if it is only one user in the system, that is not relevant. And if, god forbid, your sesion user is root, then stop and reinstall the system, and never run it as root again. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
* Doug McGarrett <dmcgarrett@optonline.net> [04-01-20 01:12]: [...]
(A bit OT:)
more likely "off the wall"
I am the only user on the system. When I select console, I get a login prompt Password: I seem to remember that when I installed the system the first (or almost first) screen I saw let me type in passwd and I gave it mine. I'm not afraid of goofs in the console-- the system is very good about catching them. I'm a child of PCLINUXOS and I'm allergic to SUDO. I think it's ridiculous! (I don't even remember how to get back to a user console, except it's NOT exit. Exit shuts the console down.)
yes, it is definitely not "exit". The command which has been repeated many times in this thread is "xset". And it definitely will not work unless invoked properly, ie: not as "exit". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/1/20 8:20 AM, Patrick Shanahan wrote:
* Doug McGarrett <dmcgarrett@optonline.net> [04-01-20 01:12]: [...]
(A bit OT:)
more likely "off the wall"
I am the only user on the system. When I select console, I get a login prompt Password: I seem to remember that when I installed the system the first (or almost first) screen I saw let me type in passwd and I gave it mine. I'm not afraid of goofs in the console-- the system is very good about catching them. I'm a child of PCLINUXOS and I'm allergic to SUDO. I think it's ridiculous! (I don't even remember how to get back to a user console,* except it's NOT exit. Exit shuts the console down.) *See instructions below.
yes, it is definitely not "exit". The command which has been repeated many times in this thread is "xset". And it definitely will not work unless invoked properly, ie: not as "exit".
Firat: OK, here's my sin: I just discovered that I had left a "Mouse Jiggler" plugged into a port. Of course the display would not shut down, and of course, it came back almost immediately. Second, someone thinks I should reinstall the whole system, and I have already stated that I'm using TW so I will hopefully never have to. Third: the way to get from a root console to a user console is: su - username no new password required So I can, if I want get to a restricted console.This turns the red prompts to black, with my username. Hope all is clear from my end, and I'm sorry if I confused a bunch of good folks reading here and helping others. --doug Everything is working properly now, but I don't know if the xset commands I entered earlier are controlling. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 29. März 2020 11:03:42 schrieb Alex Bihlmaier <thalunil@kallisti.at>:
with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
Nope, can't confirm with two machines (AMD and Intel, no Nvidia). Both of them with current TW Plasma snapshot from yesterday. Cheers, vinz. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 30.03.20 um 00:06 schrieb Vinzenz Vietzke:
with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
Nope, can't confirm with two machines (AMD and Intel, no Nvidia). Both of them with current TW Plasma snapshot from yesterday.
My described behaviour is no longer happening on the affected TW machine. "works for me"! Which is good. thanks, thal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 3/29/20 4:03 AM, Alex Bihlmaier wrote:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
Some software suppresses this action. Amarok suppresses it while playing music. Ktorrent suppresses it when there is an active torrent. However, Ktorrent does have setting to turn of that behavior. Browsers probably suppress it when playing a video, maybe when playing music. In particular, konqueror suppresses it. But konqueror sometimes fails to unsuppress it. When that happens, killing konqueror should restore the function. If you click on the battery in the hidden tray (the triangle is the hidden tray), then it will sometimes tell you what is suppressing normal power behavior. But sometimes it doesn't show anything, but killing konqueror still fixes the problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Alex Bihlmaier wrote:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
I know I am late to the game, but I have just noticed the same on my TW system in the datacentre. It's usually left locked for days or even weeks, and I noticed the blue light on just now. -- Per Jessen, Zürich (7.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 29.03.20 um 11:03 schrieb Alex Bihlmaier:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
despite this issue (which recently happended again) on my TW installation i am also wondering: is there a way to *just blank the screen*? The screensavers are gone. Should i manually run xscreensaver to restore that functionality? With xscreensaver there is a simple "blank screen" mode. I want to have something along these lines: blank screen after 5 minutes of inactivity, poweroff display after 15 minutes of inactivity. cheers thal
Alex Bihlmaier wrote:
Am 29.03.20 um 11:03 schrieb Alex Bihlmaier:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
despite this issue (which recently happended again) on my TW installation i am also wondering: is there a way to *just blank the screen*?
When kscreenlocker was looping recently, I just disabled the locking and the screen would only go blank.
I want to have something along these lines: blank screen after 5 minutes of inactivity, poweroff display after 15 minutes of inactivity.
This is how it used to work, only a couple of weeks ago. -- Per Jessen, Zürich (2.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 01.04.20 um 10:12 schrieb Per Jessen:
Alex Bihlmaier wrote:
Am 29.03.20 um 11:03 schrieb Alex Bihlmaier:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
despite this issue (which recently happended again) on my TW installation i am also wondering: is there a way to *just blank the screen*?
When kscreenlocker was looping recently, I just disabled the locking and the screen would only go blank.
I can disable locking, that's right. But how/where do you configure the blanking? The xset commands from Patrick results in a blank screen, and after some seconds the display turns on automatically.... I will check how it works on Leap, this behaviour is quite annoying. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Alex Bihlmaier <thalunil@kallisti.at> [04-02-20 15:17]:
Am 01.04.20 um 10:12 schrieb Per Jessen:
Alex Bihlmaier wrote:
Am 29.03.20 um 11:03 schrieb Alex Bihlmaier:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
despite this issue (which recently happended again) on my TW installation i am also wondering: is there a way to *just blank the screen*?
When kscreenlocker was looping recently, I just disabled the locking and the screen would only go blank.
I can disable locking, that's right. But how/where do you configure the blanking?
The xset commands from Patrick results in a blank screen, and after some seconds the display turns on automatically....
I have seen something similar, after a blank screen some seconds later the "back light" comes on but never the normal display. But this was probably errant behavour as I have not seen it since just before your first post and I had just updated my Tw. currently: CPU: 6-Core: Intel Core i7 970 type: MT MCP arch: Nehalem speed: 2970 MHz min/max: 1596/3193 MHz Graphics: Device-1: NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: nvidia v: 390.132 bus ID: 03:00.0 chip ID: 10de:0dc4 Display: x11 server: X.Org 1.20.7 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: kwin_x11 resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: GeForce GTS 450/PCIe/SSE2 v: 4.6.0 NVIDIA 390.132 direct render: Yes openSUSE Tumbleweed-20200331 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Alex Bihlmaier wrote:
Am 01.04.20 um 10:12 schrieb Per Jessen:
Alex Bihlmaier wrote:
Am 29.03.20 um 11:03 schrieb Alex Bihlmaier:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
despite this issue (which recently happended again) on my TW installation i am also wondering: is there a way to *just blank the screen*?
When kscreenlocker was looping recently, I just disabled the locking and the screen would only go blank.
I can disable locking, that's right. But how/where do you configure the blanking?
Wait, I may have misspoke - disable the password requirement ? I don't remember now, I'll have to go and check. I had help solving the looping issue, and after that I reverted to the normal setting, locking with blanking and powersave.
I will check how it works on Leap, this behaviour is quite annoying.
Agree, it has to work. -- Per Jessen, Zürich (5.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Alex Bihlmaier <thalunil@kallisti.at> [04-01-20 03:53]:
Am 29.03.20 um 11:03 schrieb Alex Bihlmaier:
Hi, with TW and Plasma i experience currently the problem that the display does not turn off after the configured period of time (in system settings). Anybody else with the same problem?
despite this issue (which recently happended again) on my TW installation i am also wondering: is there a way to *just blank the screen*?
The screensavers are gone. Should i manually run xscreensaver to restore that functionality? With xscreensaver there is a simple "blank screen" mode.
I want to have something along these lines: blank screen after 5 minutes of inactivity, poweroff display after 15 minutes of inactivity.
xset +dpms xset dpms 300 1000 3000 xset s on 5 minutes = 300 seconds man xset -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Today i tested 1) current TW 2) Leap 15.2 Beta 3) Leap 15.1 I installed a fresh Plasma and set Locking to off, Energy save of monitor to 1 minute. All of these platforms have the SAME issue. After 1 minute the display goes off and immediately starts again. cpu: AMD Ryzen 5 2600 Six-Core Processor, 1475 MHz graphics card: Sapphire Radeon RX 560 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Alex Bihlmaier wrote:
Today i tested 1) current TW 2) Leap 15.2 Beta 3) Leap 15.1
I installed a fresh Plasma and set Locking to off, Energy save of monitor to 1 minute.
All of these platforms have the SAME issue.
Leap 15.1 - no problem seen, locking and screen power off works. Current TW - locking works, screen power off does not. Display driver issue ? My two systems above have very different graphics. I have also (June 2018) reported that screen power saving on virtual consoles does not work. Bug#1095700 -- Per Jessen, Zürich (10.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 05.04.20 um 11:32 schrieb Per Jessen:
I have also (June 2018) reported that screen power saving on virtual consoles does not work. Bug#1095700
I created Bug 1168648 https://bugzilla.opensuse.org/show_bug.cgi?id=1168648 "Plasma problem: energy saving of monitor not working" thal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 05.04.20 um 11:40 schrieb Alex Bihlmaier:
I created Bug 1168648 https://bugzilla.opensuse.org/show_bug.cgi?id=1168648 "Plasma problem: energy saving of monitor not working"
Well. D'Oh. The wonderful joys of PC technology! If the display is hooked up with DVI the DPMS is working properly (with KDE & XFCE)! It seems like a weird combination of graphics, cable, display things... thank you guys for your responses! thal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Alex Bihlmaier wrote:
Am 05.04.20 um 11:40 schrieb Alex Bihlmaier:
I created Bug 1168648 https://bugzilla.opensuse.org/show_bug.cgi?id=1168648 "Plasma problem: energy saving of monitor not working"
Well. D'Oh.
The wonderful joys of PC technology! If the display is hooked up with DVI the DPMS is working properly (with KDE & XFCE)! It seems like a weird combination of graphics, cable, display things...
I'm tempted to reopen that report - in the datacentre, we use only oldfashioned VGA. -- Per Jessen, Zürich (20.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [04-05-20 05:34]:
Alex Bihlmaier wrote:
Today i tested 1) current TW 2) Leap 15.2 Beta 3) Leap 15.1
I installed a fresh Plasma and set Locking to off, Energy save of monitor to 1 minute.
All of these platforms have the SAME issue.
Leap 15.1 - no problem seen, locking and screen power off works. Current TW - locking works, screen power off does not.
sleep .3;xset dpms force off defnitely powers off the screen on Tumbleweed 20200402 NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: nvidia v: 390.13 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [04-05-20 05:34]:
Alex Bihlmaier wrote:
Today i tested 1) current TW 2) Leap 15.2 Beta 3) Leap 15.1
I installed a fresh Plasma and set Locking to off, Energy save of monitor to 1 minute.
All of these platforms have the SAME issue.
Leap 15.1 - no problem seen, locking and screen power off works. Current TW - locking works, screen power off does not.
sleep .3;xset dpms force off defnitely powers off the screen on Tumbleweed 20200402
Not my screen - have just updated and tried it - it blanks the screem but it does not power down.
NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: nvidia v: 390.13
Intel Corporation 82Q35 Express Integrated Graphics Controller Driver is most probably 'i915'. -- Per Jessen, Zürich (17.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [04-05-20 11:44]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [04-05-20 05:34]:
Alex Bihlmaier wrote:
Today i tested 1) current TW 2) Leap 15.2 Beta 3) Leap 15.1
I installed a fresh Plasma and set Locking to off, Energy save of monitor to 1 minute.
All of these platforms have the SAME issue.
Leap 15.1 - no problem seen, locking and screen power off works. Current TW - locking works, screen power off does not.
sleep .3;xset dpms force off defnitely powers off the screen on Tumbleweed 20200402
Not my screen - have just updated and tried it - it blanks the screem but it does not power down.
NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: nvidia v: 390.13
Intel Corporation 82Q35 Express Integrated Graphics Controller Driver is most probably 'i915'.
ah, more explanation is necessary :( My nvidia driver needs a patch which is not yet available for the 5.6+ kernel so I am still on 5.5.13-1-default. Probably the difference. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [04-05-20 11:44]:
Patrick Shanahan wrote:
sleep .3;xset dpms force off defnitely powers off the screen on Tumbleweed 20200402
Not my screen - have just updated and tried it - it blanks the screem but it does not power down.
NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: nvidia v: 390.13
Intel Corporation 82Q35 Express Integrated Graphics Controller Driver is most probably 'i915'.
ah, more explanation is necessary :(
My nvidia driver needs a patch which is not yet available for the 5.6+ kernel so I am still on 5.5.13-1-default. Probably the difference.
My previous kernel was 5.5.11-1-default, also didn't work. I still think it's in the driver, somehow - somehow that DPMS signal does not get sent. -- Per Jessen, Zürich (17.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [04-05-20 12:03]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [04-05-20 11:44]:
Patrick Shanahan wrote:
sleep .3;xset dpms force off defnitely powers off the screen on Tumbleweed 20200402
Not my screen - have just updated and tried it - it blanks the screem but it does not power down.
NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: nvidia v: 390.13
Intel Corporation 82Q35 Express Integrated Graphics Controller Driver is most probably 'i915'.
ah, more explanation is necessary :(
My nvidia driver needs a patch which is not yet available for the 5.6+ kernel so I am still on 5.5.13-1-default. Probably the difference.
My previous kernel was 5.5.11-1-default, also didn't work. I still think it's in the driver, somehow - somehow that DPMS signal does not get sent.
I had a brief period where my xset blanking failed power off but didn't record the environment. I can say it work-for-me(!TM) with kernel 5.5.13 and 20200402. fwiw: during that period, xscreensaver-command -suspend did work but that makes little sense cause xscreensaver utilizes xset. Makes the world go around ... :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 05.04.20 um 14:19 schrieb Patrick Shanahan:
* Per Jessen <per@computer.org> [04-05-20 05:34]:
Alex Bihlmaier wrote:
Today i tested 1) current TW 2) Leap 15.2 Beta 3) Leap 15.1
I installed a fresh Plasma and set Locking to off, Energy save of monitor to 1 minute.
All of these platforms have the SAME issue.
Leap 15.1 - no problem seen, locking and screen power off works. Current TW - locking works, screen power off does not.
sleep .3;xset dpms force off defnitely powers off the screen on Tumbleweed 20200402
NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: nvidia v: 390.13
It tries to power the screen off, Monitor is saying "No signal detected" and then...the desktop is back. I resetted all settings in the UEFI firmware...still no luck thal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Alex Bihlmaier -
Carlos E. R. -
Dave Howorth -
Doug McGarrett -
Michael Hamilton -
Neil Rickert -
Patrick Shanahan -
Per Jessen -
Vinzenz Vietzke