Registered Member
|
Hi
I built a new machine and installed Kubuntu 22.04 from scratch. Installation was flawless. But then I noticed the display wont go to standby after hitting the time given in Energy-settings. When booting the machine it has this state:
So DPMS is disabled and Standbytime is Zero (Zero disables Standby even if DPMS is enabled). So I tried different solutions with no success: Scripts in autostart etc. If I go to the console and type
the result is:
Problems: 1. I can't get this command into autostart working. Tried as script or .desktop. 2. Even more weird: When Standby time is reached the monitor goes to standby. After a few seconds it wakes up again and the standby timer restarts. Where can I search for a solution? |
Registered Member
|
The default way of making this work is to upgrade UEFI (which you already did afaics) and setting the boot option "acpi_osi=Linux" which you should try first.
If this does not work, how exactly did you try to autostart the xset command? Do you use plasma-wayland or X11? |
Registered Member
|
Thank you for your reply.
The installed BIOS is up-to-date. The boot option "acpi_osi=Linux" is already set (see quote in my first post). When installing Kubuntu 22.04 I didn't make any choices and let the installer make the decisions. As I can see it is running on X11. I made a textfile with kate and named it "DPMS.sh". The only line written was "xset dpms 600". First I made it executable but found an error message in the log file that this is not allowed. I made a new one, this time not executable. Then I found this error message:
After some research this error says there is a section entry needed. But I don't know how to write this properly. Earlier I tried to write a "/etc/X11/xorg.conf.d/10-monitor.conf" with proper sections according to xorg.conf, but this made the PC stuck and leaving me without a graphical user interface. Had to make a rescue stick on my old PC to delete this conf-file and get the machine up and running again Update: I went to System Settings >> Startup and Shutdown >> Background services and disabled KScreen2. This time the monitor stayed in standby. So this might the direction I have to look into. Although then I noticed another weird behavior: The indicator LED of the monitor stayed orange, but the backlight came up after some seconds and went off again after some seconds. And this goes on and on. |
Registered Member
|
Well, I did read the cmdline but did not see the option. So I think I should update my eyes first
When dealing with scripts, use a shebang, e.g. "#!/bin/sh" as first line. May help. And even if the $PATH variable may be set I prefer using the full path to avoid command not found, like /usr/bin/xset. In this case I'll write the xset-line into my ~/.profile. I think Ubuntu has ~/.bash_profile already created, so you can use this one too. Another way would be to enter the command to sddm-scripts which will make it work before login instead of user-dependent. Create or edit /usr/share/sddm/scripts/Xsetup and enter your xset command.
Also a good approach but these days it is preferred to run xorg dynamically. As you are using a NVidia-card you already may have a xorg.conf where you can make your changes. The use of nvidia-settings creates on afair.
Check this after the xset command works. You can run `kscreen-doctor -oi` to see how KScreen sees your monitor. |
Registered Member
|
Ok, as for now the problem seems solved
After disabling KScreen2 from "System Settings >> Startup and Shutdown >> Background services" the monitor goes to sleep and stays sleeping. The backlight issue is solved as well. It happens when connecting via Displayport. Reason maybe that the DP-cable (provided with the Acer monitor!) has a wired pin 20 which is not allowed (danger of short circuit). But before buying another cable to check this out I switched to HDMI-connection. So, once again, thank you for your support |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]