Autostart apps not starting with system

[Member Budgie]

Helpful

Up

0

::

Having failed on the first two measures I went to the third way which Dave suggested as an option using the WM start which did work.

My problem now, apart from finding out why the previous solutions did not work, is that I need to start pcloud before keepassxc.

Keepassxc is starting as intended from ~/.config/autostart/ but with pcloud starting from WM, pcloud is bound to come later than keepassxc. Is it possible to delay keepassxc until after pcloud now. I assume not as delaying keepassxc will then delay WM but I am really guessing now.

BTW should I put quotes or code brackets around my commands here?

[Forum Admin Dave]

Helpful

Up

0

::

I am not seeing anything in the desktop-session/log file for the startup of programs in the startup file. Only from what is normally in ~/.config/autostart. This may not be logged but from my memory it is usually logged; however I am not on my antiX PC to verify. Also you may want to disable the xdg autostart option in ~/.desktop-session/desktop-session.conf if you are going to use the startup file.

Try running in terminal as regular user
chmod 755 ~/.desktop-session/startup

Then log out and log back in to see if startup works.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member Budgie]

Helpful

Up

0

::

Dave wrote:

I am not seeing anything in the desktop-session/log file for the startup of programs in the startup file. Only from what is normally in ~/.config/autostart. This may not be logged but from my memory it is usually logged; however I am not on my antiX PC to verify. Also you may want to disable the xdg autostart option in ~/.desktop-session/desktop-session.conf if you are going to use the startup file.

Try running in terminal as regular user
chmod 755 ~/.desktop-session/startup

Then log out and log back in to see if startup works.

Hi Dave,
So sorry I have been making hard work of this but going back to your first reply and your three options, I tried

edit ~/.desktop-session/desktop-session.conf and change the LOAD_XDG_AUTOSTART=”false” to LOAD_XDG_AUTOSTART=”true”.

This didn’t work the first time. As suggested above I have now therefore reversed this option to “false.”

The second option adding the command to ~/.desktop-sessions/startup did not work.

The third option adding the command to ~/.icewm/startup worked and is working on reboot every time. So some progress with pcloud, however, now Keepassxc does not start!!!

I had also been trying to ensure that pcloud started before Keepassxc but now Keepassxc no longer starts.

Grateful for your suggestion when you can.

Many thanks once more,
Budgie

[Forum Admin Dave]

Helpful

Up

0

::

Keepassxc no longer starting would make sense. That would verify that the whole ~/.desktop-session/startup file is not working.
Did you try the chmod command?

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member Budgie]

Helpful

Up

0

::

Hi Dave,
Yes I had already run the chmod command. I think I may have crossed my wires a bit though because keepassxc is not in ~/.desktop-session/startup.
Keepassxc as far as I recall had been running from ~/.config/autostart.

I am taking a good deal of your time, for which I am extremely grateful and pcloud now starts from boot as required. I can then start Keepassxc myself.

To achieve “perfection,” rather than making more changes, I wonder if it would be quicker now just to do a fresh install. My antiX system has been much messed around over many years and now I have cleared out all the windoze rubbish it would be a simple matter to do a fresh install. I have antiX on USB already as I used it as a live OS in order to tidy up the partitions.

If I do this are there any issues. I wish to retain a three partition solution of /, /home and swap.

[Anonymous]

Helpful

Up

0

::

If I do this are there any issues.

no questionmark, but it sure reads like you are asking a question.
A very open-ended question.

OF COURSE there are potential issues when attempting to “reinstall and retain a three partition solution”.
(cat could walk across your keyboard during the installation)
(falling space debris could decapi-toe-pitate your toe during the installation)
(a swapFILE may be preferable to a swap partition)

Hopefully you will not encounter problems from any of the myriad possible issues but, in any event… any discussion of such does merit a new, separate, topic.

[Member Budgie]

Helpful

Up

0

::

Hi skidoo, I take the point. No space debris but the cat has done some unsolicited editing on occasions and I am still struggling with replacement keyboard from ebay after a hot chocolate spill from working too late one night, so will check out what has already been explained and start a new thread if necessary.
Regards,
Budge.

[Member slidesinger]

Helpful

Up

0

::

I am having issues with this on antiX-22_x64-base Grup Yorum 19 October 2022

My ~/.icewm/startup is -rwxr-xr-x so is executable.

Contents of ~/.icewm/startup:

#!/bin/bash

# change keyboard map
setxkbmap dvorak

Session is icewm, not minimal and not rox. Logout, login, kbmap is still qwerty.

I have already tried what is here, if I understood what was written correctly, except the add startup from the menu, which I have been unable to find.

Any ideas?

[Member slidesinger]

Helpful

Up

0

::

This is just because I forgot to tic off the ‘Notify me…’ box.

[Member PPC]

Helpful

Up

0

::

Try:

#!/bin/bash

# change keyboard map
setxkbmap dvorak &

[Member slidesinger]

Helpful

Up

0

::

Tried it with the (&)

No difference.

Modified the ~/.icewm/startup further so as to get data.

#!/bin/bash

sleep 5;
xterm &;
sleep 5;

# change keyboard map
setxkbmap dvorak &;
sleep 5;

The result was the same: nada

I have tried this both with and without the (;), no difference.
On the basis of the information found at https://ice-wm.org/man/icewm-startup, specifically $XDG_CONFIG_HOME/icewm/startup, I have looked for the environment variables and found them not. Not certain of the appropriate way to add those, but will research that. OTOH, according to what I read, /usr/local/bin/desktop-session has a lot to do with whether this thing runs or not, so I probably need to pass the appropriate information to that script so that things don’t break (hopefully) with the next update.

[Member PPC]

Helpful

Up

0

::

I just tested. I can’t replicate your problem. Have you tried using another Window manager (like JWM) and add that to it’s startup file? It may be some kind of problem with your icewm…

edit: are you sure making the addition to ~/.desktop-session/startup does also not work?

P.

• This reply was modified 3 months ago by PPC.

[Member Xunzi_23]

Helpful

Up

0

::

Please add
# change keyboard map
setxkbmap dvorak &

in about the middle of
~/.desktop-session/startup

i.e.before fxkb entry

works fine for me

• This reply was modified 3 months ago by Xunzi_23.

[Author]

Posts