You are not logged in.

#1 2020-12-16 18:11:37

serialschoenberg
Member
Registered: 2020-04-01
Posts: 28

[solved] deconnect automatic docking

Dear friends,

I use the Helium distrib.
In /etc/systemd/logind.conf, I wrote
-------------------------
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=suspend
HandleLidSwitch=ignore
# fait le 15.12.2020
HandleLidSwitchDocked=ignore
# changé le 16.12.2020
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192
#UserTasksMax=33%
-------------------------
and so I can activate it by
-----------------------
sudo systemctl enable upower.service && sudo systemctl restart upower.service
-----------------------

How to do that at boot ?

Thanks for your ideas.
rené

Last edited by serialschoenberg (2020-12-19 15:42:34)

Offline

#2 2020-12-16 19:16:48

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,083

Re: [solved] deconnect automatic docking

I think you could add command in roots crontab:

$ sudo crontab -e

add:

@reboot sleep 30 && systemctl enable upower.service && systemctl restart upower.service

Last edited by rbh (2020-12-16 19:17:20)


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#3 2020-12-16 19:20:25

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,083

Re: [solved] deconnect automatic docking

serialschoenberg wrote:

I use the Helium distrib.

You have updated to Buster last spring? Time to upgrade to Litium to?

Last edited by rbh (2020-12-16 19:40:15)


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#4 2020-12-17 13:43:51

serialschoenberg
Member
Registered: 2020-04-01
Posts: 28

Re: [solved] deconnect automatic docking

Salut,

I never made un update ...

I user BL since the end of march 2020

rené

Offline

#5 2020-12-18 11:14:52

serialschoenberg
Member
Registered: 2020-04-01
Posts: 28

Re: [solved] deconnect automatic docking

Salut rbh,

The crontab method is not adapted to my working habits. (So it is not a good idea to do it at boot).
How can I get rid of it?

I will put

systemctl enable upower.service && systemctl restart upower.service

in aa executable file (chmod)  which I can call when I need it.

Thanks for the time you spent.

rené

Offline

#6 2020-12-19 02:56:02

hhh
Meep!
Registered: 2015-09-17
Posts: 12,032
Website

Re: [solved] deconnect automatic docking

Moderator here, posts deleted. I don't know, I don't speak Orc.

unklar wrote:

delete

serialschoenberg wrote:

delete what ? etwas unklar smile

Offline

#7 2020-12-19 15:40:40

serialschoenberg
Member
Registered: 2020-04-01
Posts: 28

Re: [solved] deconnect automatic docking

I found crontab -r

Offline

#8 2020-12-19 22:09:36

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,083

Re: [solved] deconnect automatic docking

serialschoenberg wrote:

The crontab method is not adapted to my working habits. (So it is not a good idea to do it at boot).

Crontab is easier to manage command at boot than systemd... Commands that need be started with admin rights, can also be started in /etc/crontab.

How can I get rid of it?

Sorry, did not understand, that you wanted to remove the command from crontab. Hope there was no other commands in it, as "crontab -r", deletes whole users crontab. Instead of deleting whole crontab, delete the entry or just comment out the command. You can edit crontab with usual editor also.

I will put [...] in aa executable file (chmod)  which I can call when I need it.

But, you asked: "How to do that at boot ?" Now I get more curious. You do not need to run it at boot? You do not always need to run it? If you only need to run it sometimes, you should not run it every boot... You can make an tint2 button and/or assign key-shortcuts for the script.

I understand that you don't want the laptop to go to slep when closing the lid, if it is docked.
What is status for upower after boot? Is it not enabled? Do you realy need enable it and to restart it?


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

Board footer

Powered by FluxBB