MiniOS 5.0 Linux (Debian based) went into sleep mode after ten minutes

[Deleted member 210773]

I don’t know why since yesterday morning the operating system MiniOS 5.0 Linux (Debian based) went into sleep mode after ten minutes.
I tried everything to fix the problem with xfce power manager, but without success; so I installed the lxqt power manager (which in my opinion is better than xfce). Likewise the problem is back, I typed the Code command in the terminal:

xset -dpms

This command disables the DPMS function, which controls screen dimming.
To make sure the settings are applied correctly, you can check the current DPMS settings:
In the terminal, run:

Code:

xset -q

But the problem came back within an hour of turning on the computer, so I used the commands:

(sudo)
/usr/bin/xset s noblank
/usr/bin/xset s disabled
/usr/bin/xset dpms 0 0 0
/usr/bin/xset -dpms

The problem is partially solved, because when I restart the computer the problem reappears and I have to repeat all the above commands.

What should I do to avoid having to repeat commands every time I restart my computer with MiniOS 5.0?


Attached lxqt power manager on MiniOS 5.0

 

[osprey]

I don’t know why since yesterday morning the operating system MiniOS 5.0 Linux (Debian based) went into sleep mode after ten minutes.
I tried everything to fix the problem with xfce power manager, but without success; so I installed the lxqt power manager (which in my opinion is better than xfce). Likewise the problem is back, I typed the Code command in the terminal:

xset -dpms

This command disables the DPMS function, which controls screen dimming.
To make sure the settings are applied correctly, you can check the current DPMS settings:
In the terminal, run:

Code:

xset -q

But the problem came back within an hour of turning on the computer, so I used the commands:

(sudo)
/usr/bin/xset s noblank
/usr/bin/xset s disabled
/usr/bin/xset dpms 0 0 0
/usr/bin/xset -dpms

The problem is partially solved, because when I restart the computer the problem reappears and I have to repeat all the above commands.

What should I do to avoid having to repeat commands every time I restart my computer with MiniOS 5.0?


Attached lxqt power manager on MiniOS 5.0

A relatively straight forward way of dealing with issue is to create a script with those commands which resolve the issue, place it in
/usr/local/bin, or somewhere in the $PATH that suits, and then configure xfce to run as a startup application.

Not having used xfce for some time, I can't be precise, but from memory look at Session and Startup settings. Perhaps open the settings manager, go to the Application Autostart tab, and click Add to create a new entry with a name and command to run on login. Then you won't have to run it continually, hopefully .

 

[Deleted member 210773]

A relatively straight forward way of dealing with issue is to create a script with those commands which resolve the issue, place it in
/usr/local/bin

Please what is the script I have to insert?

 

[osprey]

Please what is the script I have to insert?

The script would just include the commands which you suggested as having resolved the issue in post #1. It could look like this:

#!/bin/bash
/usr/bin/xset s noblank
/usr/bin/xset s disabled
/usr/bin/xset dpms 0 0 0
/usr/bin/xset -dpms

I've assumed that your shell is bash. If not, alter the first line to reflect the current shell.

The script needs a unique name, perhaps with some reference to what it does, for example you could name it: setxset.
So the file named setxset which you create with a text editor has the above contents, and it should be made executable with the command:

chmod 755 setxset

Then it can be placed as described in post #2 above, and tested. If it works, good, if not, then it can be amended. A reboot should have it work.

 

[Deleted member 210773]

Thank you very much!! I have tried (but I have not already restarted the computer on MiniOS)

P.S. On the terminal I have typed "sudo nano setxset" and in the nano text editor and I have added the following command-lines:
/usr/bin/xset s noblank
/usr/bin/xset s disabled
/usr/bin/xset dpms 0 0 0
/usr/bin/xset -dpms
(and I have saved them with Ctrl+x)

After I have typed "sudo chmod 755 setxset"
It's right?

 

[osprey]

Thank you very much!! I have tried (but I have not already restarted the computer on MiniOS)

P.S. On the terminal I have typed "sudo nano setxset" and in the nano text editor and I have added the following command-lines:
/usr/bin/xset s noblank
/usr/bin/xset s disabled
/usr/bin/xset dpms 0 0 0
/usr/bin/xset -dpms
(and I have save it with Ctrl+x)

After I have typed sudo chmod 755 setxset
It's right?

Looks good to me. The proof of the pudding is in the eating . The file needs to be placed in the $PATH as mentioned in post #2.
/usr/local/bin is usually good.

 

[wizardfromoz]

Just an additional note @secureuser - you can determine your Path with

echo $PATH

The different choices are separated by a colon, :

I nearly always use

/usr/local/bin

for my bash scripts, it is a common choice.

If you wish to place it elsewhere, you will need to amend your Path,

Cheers

Wizard

 

[Deleted member 210773]

Looks good to me. The proof of the pudding is in the eating . The file needs to be placed in the $PATH as mentioned in post #2.
/usr/local/bin is usually good.

Just an additional note @secureuser - you can determine your Path with

echo $PATH

The different choices are separated by a colon, :

I nearly always use

/usr/local/bin

for my bash scripts, it is a common choice.

If you wish to place it elsewhere, you will need to amend your Path,

Cheers

Wizard

Unfortunately the test did not have the expected outcome: MiniOS shut down after 10 minutes.
I reinstalled xfce4 power manager (after uninstalling lxqt power manager)
In "sudo nano setxset" typed the following commands:
echo/usr/local/bin
/usr/bin/xset s noblank
/usr/bin/xset s disabled/usr/bin/xset dpms 0 0 0
/usr/bin/xset -dpms

Also in the terminal I typed:
sudo chmod 755 setxset
and after that I checked the permissions by typing:
sudo ls -l setxset
the output of this last command is:
l-rwxr-xr-x 1 root root 114 Oct 29 09:11 setxset
(indicating that permissions are set correctly)

For now provisionally when I turn on MiniOS I type in the terminal:
sudo /usr/bin/xset s noblank && sudo /usr/bin/xset s off && sudo/usr/bin/xset dpms 0 0 0 && sudo /usr/bin/xset -dpms and I hit Enter (the screen of MiniOS no longer turns off)

 

[osprey]

Unfortunately the test did not have the expected outcome: MiniOS shut down after 10 minutes.
I reinstalled xfce4 power manager (after uninstalling lxqt power manager)
In "sudo nano setxset" typed the following commands:
echo/usr/local/bin
/usr/bin/xset s noblank
/usr/bin/xset s disabled/usr/bin/xset dpms 0 0 0
/usr/bin/xset -dpms

Also in the terminal I typed:
sudo chmod 755 setxset
and after that I checked the permissions by typing:
sudo ls -l setxset
the output of this last command is:
l-rwxr-xr-x 1 root root 114 Oct 29 09:11 setxset
(indicating that permissions are set correctly)

For now provisionally when I turn on MiniOS I type in the terminal:
sudo /usr/bin/xset s noblank && sudo /usr/bin/xset s off && sudo/usr/bin/xset dpms 0 0 0 && sudo /usr/bin/xset -dpms and I hit Enter (the screen of MiniOS no longer turns off)

Okay. You could replace the commands in the setxset script file with the exact long command which does work from the command line, and see if that works. If the script file is being placed in /usr/local/bin it should be owned by root so the sudos in your long command would not be necessary.

You didn't mention whether you configured xfce to run the setxset script as a startup script which I referred to in post #2. That must be done for the script to actually run at startup to make a difference.

 

[Deleted member 210773]

Okay. You could replace the commands in the setxset script file with the exact long command which does work from the command line, and see if that works. If the script file is being placed in /usr/local/bin it should be owned by root so the sudos in your long command would not be necessary.

You didn't mention whether you configured xfce to run the setxset script as a startup script which I referred to in post #2. That must be done for the script to actually run at startup to make a difference.

Thank you,
I have inserted in xfce power manager the script: /usr/local/bin as you can see in the attached photograph, but I don't know what to select under the script.
I don't know if what I'm doing is right.

 

[osprey]

Thank you,
I have inserted in xfce power manager the script: /usr/local/bin as you can see in the attached photograph, but I don't know what to select under the script.
I don't know if what I'm doing is right.

The following shows the steps I took to have a script placed in /usr/local/bin, and have that script run at startup the next time I booted minios. The following is a proof of concept so I have used a simple executable in place of the particular one which you are concerned with.

On a booting up a session of minios I hit e to add a configuration.
On a new line under the existing text I added:

perchdir=resume

I don't know if this is necessary because when rebooting minios, I could choose the option: "Resume previous session", which would presumably keep the previous session's work in the filesystem anyway.

On the booted up session, I opened a terminal and navigated to the directory: /usr/local/bin.

At /usr/local/bin I opened a file:

sudo nano writefile

The contents of the file: writefile, were:

#!/bin/bash
touch /home/live/newfile

The file: writefile was made executable with the command:

sudo chmod 755 writefile

The effect of this command is to write a file named: newfile, in the minios home directory /home/live.

The process of configuration to get this file to execute on boot up automatically was as follows:

During the live miniso session menu I selected:
All Applications -> Session and Startup -> Application Autostart

In the Application Autostart display I selected: +Add

When +Add was selected a box opened with the following dialogs:

Name:
Description:
Command:
Trigger:

These were filled with:

Name: writefile
Description: writes a file to home
Command: /usr/local/bin/writefile
Trigger: on login

Then I clicked: OK, and the new option just created was added to the list of Application Autostart entries.

On rebooting minios, the "Resume previous session" option was selected, and after booting up, on opening a terminal to check whether the file: newfile, had been automatically created by the executable I had created earlier, it had. So the proof of concept was successful. In other words, the executable file created and written to /usr/local/bin, was executed on boot up automatically.

On your system, you could perhaps convert the successful configuration described above to include the executable script which you wish to have automatically run on start up. You have two scripts you could try described in post #5 and post #8, bearing in mind the other comments which have been made in this thread. I hope the above is clear enough. It all works as expected .