Error configuring autostart - Исправление ошибок и поиск оптимальных решений проблем

Remove From My Forums

Question
When trying to set Options-> Run at Logon I get «Error configuring auto start» + «Security assignment user account missing (my translation from Dutch so maybe it is not quite right)». I tried to change some settings in policy editor.
Didn’t help.

All replies

On What OS are you running? What version of Process Explorer?

If you run procmon together, when you click the option what registry keys get written?

Now this option works creating a Logon Task for the user, as you can see in AutoRUns

And in Process Monitor

So, may be your user is lacking the ability to create Scheduled Task..

Start checking that with Process Monitor and Autoruns..

HTH
-mario

I am trying to make ProtonVPN autostart on my Kubuntu machine.

I have tried following this and this guides.

The latest one I tried is the one from blog.x86txt.com. But when using the following command:

systemctl enable protonvpn-cli.service && systemctl start protonvpn-cli.service

I get the following message from the terminal:

Job for protonvpn-cli.service failed because the control process exited with error code.
See "systemctl status protonvpn-cli.service" and "journalctl -xe" for details.

When i run the comand

systemctl status protonvpn-cli.service

I get the following output:

 ● protonvpn-cli.service - ProtonVPN CLI Auto-Start
   Loaded: loaded (/etc/systemd/system/protonvpn-cli.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-01-13 11:19:20 CET; 13s ago
  Process: 2177 ExecStart=/usr/bin/protonvpn-cli last-connect (code=exited, status=203/EXEC)

jan 13 11:19:20 teuton-VirtualBox systemd[2177]: protonvpn-cli.service: Failed at step EXEC spawning /usr/bin/protonvpn-cli
jan 13 11:19:20 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Control process exited, code=exited status=203
jan 13 11:19:20 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Failed with result 'exit-code'.
jan 13 11:19:20 teuton-VirtualBox systemd[1]: Failed to start ProtonVPN CLI Auto-Start.
jan 13 11:19:20 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Service hold-off time over, scheduling restart.
jan 13 11:19:20 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Scheduled restart job, restart counter is at 5.
jan 13 11:19:20 teuton-VirtualBox systemd[1]: Stopped ProtonVPN CLI Auto-Start.
jan 13 11:19:20 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Start request repeated too quickly.
jan 13 11:19:20 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Failed with result 'exit-code'.
jan 13 11:19:20 teuton-VirtualBox systemd[1]: Failed to start ProtonVPN CLI Auto-Start.
log file: -binfmt_misc.automount  protonvpn-cli.service

Teuton is the users name.

I will paste my systemd file down below.

[Unit]
Description=ProtonVPN CLI Auto-Start
After=network.target

[Service]
Type=forking
User=teuton
ExecStart=/usr/bin/protonvpn-cli last-connect
ExecReload=/usr/bin/protonvpn-cli disconnect && /usr/bin/protonvpn-cli last-connect
ExecStop=/usr/bin/protonvpn-cli disconnect
Restart=always

[Install]
WantedBy=multi-user.target

Here i removed the -- in the commands --last-connect and --disconnect from blog.x86txt.com to see if it would help me in any way.

Edit:

Here is the journalctl -xe output:

-- Subject: Unit anacron.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit anacron.service has finished starting up.
--
-- The start-up result is RESULT.
jan 13 14:04:47 teuton-VirtualBox anacron[1883]: Anacron 2.3 started on 2020-01-13
jan 13 14:04:47 teuton-VirtualBox anacron[1883]: Normal exit (0 jobs run)
jan 13 14:17:01 teuton-VirtualBox CRON[1896]: pam_unix(cron:session): session opened for user root by (uid=0)
jan 13 14:17:01 teuton-VirtualBox CRON[1897]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
jan 13 14:17:01 teuton-VirtualBox CRON[1896]: pam_unix(cron:session): session closed for user root
jan 13 14:20:16 teuton-VirtualBox systemd[1]: Starting Message of the Day...
-- Subject: Unit motd-news.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit motd-news.service has begun starting up.
jan 13 14:20:16 teuton-VirtualBox systemd[1]: Started Message of the Day.
-- Subject: Unit motd-news.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit motd-news.service has finished starting up.
--
-- The start-up result is RESULT.
jan 13 15:05:08 teuton-VirtualBox systemd[1]: Started Run anacron jobs.
-- Subject: Unit anacron.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit anacron.service has finished starting up.
--
-- The start-up result is RESULT.                                                                                                                   
jan 13 15:05:08 teuton-VirtualBox anacron[1959]: Anacron 2.3 started on 2020-01-13                                                                  
jan 13 15:05:08 teuton-VirtualBox anacron[1959]: Normal exit (0 jobs run)                                                                           
jan 13 15:17:01 teuton-VirtualBox CRON[1969]: pam_unix(cron:session): session opened for user root by (uid=0)
jan 13 15:17:01 teuton-VirtualBox CRON[1970]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
jan 13 15:17:01 teuton-VirtualBox CRON[1969]: pam_unix(cron:session): session closed for user root
jan 13 15:24:32 teuton-VirtualBox sudo[1983]:   teuton : TTY=pts/2 ; PWD=/etc/systemd/system ; USER=root ; COMMAND=/usr/sbin/visudo
jan 13 15:24:32 teuton-VirtualBox sudo[1983]: pam_unix(sudo:session): session opened for user root by teuton(uid=0)
jan 13 15:42:02 teuton-VirtualBox sudo[1983]: pam_unix(sudo:session): session closed for user root

teuton@teuton-VirtualBox:/etc/systemd/system$ sudo systemctl enable protonvpn-cli.service && systemctl start protonvpn-cli.service
[sudo] lösenord för teuton:
Job for protonvpn-cli.service failed because the control process exited with error code.
See "systemctl status protonvpn-cli.service" and "journalctl -xe" for details.
teuton@teuton-VirtualBox:/etc/systemd/system$ journalctl -xe
jan 13 15:42:25 teuton-VirtualBox systemd[2085]: protonvpn-cli.service: Failed at step USER spawning /usr/bin/protonvpn: No such process
-- Subject: Process /usr/bin/protonvpn could not be executed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The process /usr/bin/protonvpn could not be executed and failed.
--
-- The error number returned by this process is 3.
jan 13 15:42:25 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Control process exited, code=exited status=217
jan 13 15:42:25 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Failed with result 'exit-code'.
jan 13 15:42:25 teuton-VirtualBox systemd[1]: Failed to start ProtonVPN CLI Auto-Start.
-- Subject: Unit protonvpn-cli.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit protonvpn-cli.service has failed.
--
-- The result is RESULT.
jan 13 15:42:25 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Service hold-off time over, scheduling restart.
jan 13 15:42:25 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit protonvpn-cli.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
jan 13 15:42:25 teuton-VirtualBox systemd[1]: Stopped ProtonVPN CLI Auto-Start.
-- Subject: Unit protonvpn-cli.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit protonvpn-cli.service has finished shutting down.
jan 13 15:42:25 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Start request repeated too quickly.
jan 13 15:42:25 teuton-VirtualBox systemd[1]: protonvpn-cli.service: Failed with result 'exit-code'.
jan 13 15:42:25 teuton-VirtualBox systemd[1]: Failed to start ProtonVPN CLI Auto-Start.
-- Subject: Unit protonvpn-cli.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit protonvpn-cli.service has failed.
--
-- The result is RESULT.
lines 2394-2435/2435 (END)

Edit 2: here is my sudo visudo output:

#
# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaults        env_reset
Defaults        mail_badpass
Defaults        secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"

# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
root    ALL=(ALL:ALL) ALL

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "#include" directives:

#includedir /etc/sudoers.d
teuton ALL = (root) NOPASSWD: /usr/local/bin/protonvpn

Источник

When configuring Autostart Options for a virtual machine the virtual machine is not found.

def set_host_autostart(host, vm):

defaults = { 'start_delay': 120, 'stop_delay': 65535, 'start_action': 'powerOn', 'stop_action': 'GuestShutdown' }
asm = host.configManager.autoStartManager

asm_spec = vim.host.AutoStartManager.Config()
asm_spec.defaults = vim.host.AutoStartManager.SystemDefaults(enabled=True, startDelay=defaults['start_delay'],
                                                                           stopDelay=defaults['stop_delay'],
                                                                           stopAction=defaults['stop_action'])

power_info = vim.host.AutoStartManager.AutoPowerInfo(key=vm,
                                                     waitForHeartbeat=vim.host.AutoStartManager.AutoPowerInfo.WaitHeartbeatSetting.systemDefault,
                                                            startOrder=1,
                                                            startDelay=defaults['start_delay'],
                                                            stopDelay=defaults['stop_delay'],
                                                            startAction=defaults['start_action'],
                                                            stopAction=defaults['stop_action'])
asm_spec.powerInfo = [power_info]

print asm_spec

asm.ReconfigureAutostart(asm_spec)

print asm_spec:

(vim.host.AutoStartManager.Config) {
   dynamicType = <unset>,
   dynamicProperty = (vmodl.DynamicProperty) [],
   defaults = (vim.host.AutoStartManager.SystemDefaults) {
      dynamicType = <unset>,
      dynamicProperty = (vmodl.DynamicProperty) [],
      enabled = true,
      startDelay = 120,
      stopDelay = 65535,
      waitForHeartbeat = <unset>,
      stopAction = 'GuestShutdown'
   },
   powerInfo = (vim.host.AutoStartManager.AutoPowerInfo) [
      (vim.host.AutoStartManager.AutoPowerInfo) {
         dynamicType = <unset>,
         dynamicProperty = (vmodl.DynamicProperty) [],
         key = 'vim.VirtualMachine:vm-182',
         startOrder = 1,
         startDelay = 120,
         waitForHeartbeat = 'systemDefault',
         startAction = 'powerOn',
         stopDelay = 65535,
         stopAction = 'GuestShutdown'
      }
   ]
}

Raised Error:

Traceback (most recent call last):
  File "./create_vm.py", line 346, in <module>
    main()
  File "./create_vm.py", line 341, in main
    set_host_autostart(host, vm)
  File "./create_vm.py", line 176, in set_host_autostart
    asm.ReconfigureAutostart(asm_spec)
  File "build/bdist.linux-x86_64/egg/pyVmomi/VmomiSupport.py", line 566, in <lambda>
  File "build/bdist.linux-x86_64/egg/pyVmomi/VmomiSupport.py", line 375, in _InvokeMethod
  File "build/bdist.linux-x86_64/egg/pyVmomi/SoapAdapter.py", line 1300, in InvokeMethod
pyVmomi.VmomiSupport.ManagedObjectNotFound: (vmodl.fault.ManagedObjectNotFound) {
   dynamicType = <unset>,
   dynamicProperty = (vmodl.DynamicProperty) [],
   msg = 'The object has already been deleted or has not been completely created',
   faultCause = <unset>,
   faultMessage = (vmodl.LocalizableMessage) [],
   obj = 'vim.VirtualMachine:vm-2'
}

Источник

Forum
The Ubuntu Forum Community
Ubuntu Official Flavours Support
General Help
[SOLVED] Autostart Applications NOT WORKING

Autostart Applications NOT WORKING

Hello,
I have just installed lubuntu 16.04 64 bit. I have been trying to configure autostart for hours now and nothing is working. I ran a real vnc server on my old install (ubuntu 14.04) and it worked fine. I have tried using the GUI and adding the .desktop file by dragging and dropping AND the actual path and nothing happens when restarting or logging on. I have also manually added it to /home/bikini/.config/lxsession/Lubuntu/autostart and it still will not work. I also tried launching the sticky note application from there to test if it is just real vnc not working but NO applications are starting up automatically. I really need to get this sorted out as quickly as possible, any help would be greatly appreciated.

Thanks,
Ron
Re: Autostart Applications NOT WORKING

fyi I am getting the directory from the .desktop file I want to auto start from /usr/share/applications
Re: Autostart Applications NOT WORKING

I am also having problems with vnc, as when the computer goes to the lock screen (automatically after inactivity), when I connect with vnc it is just a black screen. Initially after installing I couldn’t even get into the system because I manually had to download the correct intel drivers for my old onboard integrated graphics. I am starting to contemplate to switch back to ubuntu 14.04 as there are too many problems so far. Can I go to ubuntu 16.04 or will i have the same video issues as well? Everything worked like a charm in the old one, only upgraded because I needed to switch from 32 bit to 64 bit from a memory upgrade.
Re: Autostart Applications NOT WORKING

I always go to Preferences > Default Applications for LXSession.
Click on Autostart tab on left.
Enter the command to run your script or start your application under «Manual autostarted applications» in the box and click on Add. That should do it.

On your follow up, sorry, I don’t know vnc.
Re: Autostart Applications NOT WORKING

Hi Dennis,
Thanks for your response but as a said above it ignores anything in there and it does not auto start. I put the exact path to the .Desktop file under applications in there. Also I really think its support of the older intel hard ware is what is causing the glitch with the screen going black. The latest stable version real vnc supports is ubuntu 15.10. I think I may wipe my server again and go back to regular ubuntu. I like the light weight graphics package in lubuntu and figured it would be much easier on older hardware (core 2 duo, 4gb ram), but it is very buggy and I often get internal errors and errors with the pcmanfm file system. I wish they would make a version of regular Ubuntu that was exactly the same just simplified graphics. I’m sure it can be optimized for performance in settings somewhere.

Last edited by ronnie4; June 29th, 2016 at 01:20 PM.
Re: Autostart Applications NOT WORKING

Autostarted applications are shown in this file:

~/.config/lxsession/Lubuntu/autostart

The «Default Applications for LXSession» merely writes entries to the same file. These of course are per user and don’t start until the user logs in. I have one entry and it does work in 16.04.

There is also /etc/xdg/autostart for general system autostart. In there are .desktop files.
Re: Autostart Applications NOT WORKING

I will give the «/etc/xdg/autostart» a try as the autostart in the config didn’t work either. Do I just drag and drop the .desktop file into the autostart config in /etc/xdg/autostart ?
Re: Autostart Applications NOT WORKING

Originally Posted by ronnie4

I will give the «/etc/xdg/autostart» a try as the autostart in the config didn’t work either. Do I just drag and drop the .desktop file into the autostart config in /etc/xdg/autostart ?

It will require root privileges. My preference for that is just use the cp command in the terminal. But any way it works for you.
Re: Autostart Applications NOT WORKING

Thanks for the help. One more question, when I would drag the file in the command/directory itself would include «File://» at the beginning. Should I type this in /etc/xdg/autostartor just put the exact path to the desktop file
ex:
/usr/share/applications/realvnc.desktop

or

File:/

/usr/share/applications/realvnc.desktop
Re: Autostart Applications NOT WORKING
Just so I am clear what is being done: You are going to copy a .desktop file from /usr/share/applications/ TO /exc/xdg/autostart

You don’t include anything in front of the actual file name, such as File://

Easiest way for this is open your terminal, and if the desktop file is abc.desktop
Code:

sudo cp /usr/share/applications/abc.desktop /etc/xdg/autostart/
Keep in mind this location is used for system files, and things that run in the background like a screensaver daemon , power manager, or update notifier, for example. So may or may not work.
Last edited by Dennis N; June 29th, 2016 at 07:17 PM.