[Solved]Desktop session startup not working

[Member Dzhigit]

I am trying to run four commands at startup so I don’t have to type them in myself every time I turn on my computer. Here is my ~/.desktop-session/startup:

automount-antix &
pulseaudio --start &
fbxkb-start &
volumeicon &

I want to start up automount, audio, and the keyboard flag so I can switch between Russian and English. (I just press alt+shift but I want to see the flag.) When I first installed, the original preinstalled startup file was working, but after I started making changes to it and other parts of the system, it stopped working. The desktop-session-antix package was updated during the first update after the original installation and replaced with a new startup file with minor differences. I did uninstall a lot of packages from antiX-base that I didn’t need, and removed a lot of things from the system I didn’t need (or thought I didn’t need) so I may have uninstalled something that is necessary for the startup file to work, but I don’t know what it is and desktop-session-antix is still installed so I didn’t uninstall any of its dependencies. (I uninstalled lots of applications and packages I didn’t want because I wanted to install antiX-net, but UEFI wouldn’t work because of this bug, so I decided to install antiX-base and remove anything I didn’t need.) I have tried reinstalling the package. I also edited the startup file in /etc/skel/.desktop-session thinking that that was the one I needed to edit, before I knew that /etc/skel/ was for making new users. My goal is to make all of these commands work, and I may possibly add the connman GUI in the future. I only use jwm, so I apt-get purged all other window managers from the system. The only troubleshooting steps I have taken are editing the startup file and reinstalling desktop-session-antix, since that is the package that the startup file belongs to, according to apt-file.

Edit: add link to UEFI bug

• This topic was modified 2 years, 8 months ago by Dzhigit.
• This topic was modified 2 years, 8 months ago by Dzhigit. Reason: add solved to title

[Member Xecure]

Helpful

Up

0

::

I see two possibilities.
A) You are running minimal-JWM (which DOESNT load ~/.desktop-session/startup)
B) desktop-session program is not being loaded on startup.

Did you remove/replace SLIM? If so, you may be launching jwm directly (which doesn’t load desktop-session program.
You can easily check if the program is running by executing in terminal:
sudo ps_mem.py | grep desktop-session
If it is running, it will tell you how much RAM it is using. If it is NOT running, you will see no output.

You can also add the startup commands to your ~/.jwm/startup file. You don’t need desktop-session if you add the commands directly to that startup file.

More info may be needed to solve your issue.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Dzhigit]

Helpful

Up

0

::

Thank you for the reply. Here are the commands I ran:

$ sudo ps_mem.py | grep desktop-session
[sudo] пароль для Maksim: 
704.0 KiB + 343.5 KiB =   1.0 MiB	desktop-session
$ dpkg -l | grep slim
ii  artwork19-antix                         0.1.5                               all          Default wallpapers, grub, slim background for antiX-19.
ii  slim                                    1.3.6.10.6                          amd64        desktop-independent graphical login manager for X11
ii  slim-themes-extras-antix                0.1.4                               all          extra slim themes for antiX.

[Member Dzhigit]

Helpful

Up

0

::

And if you need to know, my init system is runit. I have attached a screenshot of my System V startup configuration.

Attachments:

1. 

   screenshot.jpg
   

[Member Xecure]

Helpful

Up

0

::

Please, also provide:
cat ~/.desktop-session/desktop-code.0
This should give us the current desktop-session you are using.

And we will know if the startup is being loaded and the startup delay with:
cat ~/.desktop-session/desktop-session.conf | grep "LOAD_STARTUP\|STARTUP_DELAY"

Lastly, check out the the ~/.desktop-session/log file and see if your startup file is being loaded. You need to look for a line containing .desktop-session/startup &
You may also be able to find an error with desktop-session there. If you want to share it, upload it as a .txt or in a zip file.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Dzhigit]

Helpful

Up

0

::

Here is the output of those commands:

$ cat ~/.desktop-session/desktop-code.0
jwm
$ cat ~/.desktop-session/desktop-session.conf | grep "LOAD_STARTUP\|STARTUP_DELAY"
STARTUP_DELAY="2"
LOAD_STARTUP_FILE="true"

There is indeed an error in the log file.
/usr/local/lib/desktop-session/lib-desktop-session.sh: строка 77: /home/Maksim/.desktop-session/startup: Отказано в доступе
That text translates to: /usr/local/lib/desktop-session/lib-desktop-session.sh: line 77: /home/Maksim/.desktop-session/startup: Access denied

• This reply was modified 2 years, 8 months ago by Dzhigit.

[Member Dzhigit]

Helpful

Up

0

::

Also, here is the log file attachment.

• This reply was modified 2 years, 8 months ago by Dzhigit. Reason: add txt extension to file so it will upload

Attachments:

1. log.txt

[Member Xecure]

Helpful

Up

0

::

Execute this in terminal to know about the startup file permissions.
ls -lh /home/Maksim/.desktop-session | grep startup
It should look similar to:
-rwxr-xr-x 1 user user 1.3K Jul 1 08:32 startup
where “user” would be “Maksim”, and -rwxr-xr-x should be exactly the same.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Dzhigit]

Helpful

Up

0

::

Well the output is different:

$ ls -lh /home/Maksim/.desktop-session | grep startup
-rw-r--r-- 1 Maksim Maksim   66 сен  1 12:08 startup

• This reply was modified 2 years, 8 months ago by Dzhigit.

[Member Xecure]

Helpful

Up

0

::

It is an easy fix. Execute in terminal:
chmod +x ~/.desktop-session/startup

From now on you should no longer have this problem.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Dzhigit]

Helpful

Up

0

::

Thanks for your speedy help, it works now! So the startup file wasn’t executable then. Now I have a new issue where volumeicon doesn’t start after restarting the computer, or after I log in after logging out, but it works when I restart the session. I’m working on that now.

$ cat ~/.desktop-session/log | grep volume
volumeicon: alsa_backend.c:86: asound_get_volume: Проверочное утверждение «m_elem != NULL» не выполнено.

[Member Xecure]

Helpful

Up

0

::

run volumeicon from terminal when it fails and paste the output here. Maybe you need to blacklist/unblacklist some kernel module or it could be something else. It is probably related to your soundcard controller.

• This reply was modified 2 years, 8 months ago by Xecure.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Dzhigit]

Helpful

Up

0

::

It’s just errors about missing icons, which were icons that were part of the icewm-icons-papirus-antix package, which is a package I deleted.

$ cat ~/.desktop-session/log | grep volume
volumeicon: alsa_backend.c:86: asound_get_volume: Проверочное утверждение «m_elem != NULL» не выполнено.
$ volumeicon
/home/Maksim/.gtkrc-2.0.mine:6: Файл с изображением не найден в pixmap_path: «rox-show-hidden.png»
/home/Maksim/.gtkrc-2.0.mine:7: Файл с изображением не найден в pixmap_path: «rox-show-details.png»
/home/Maksim/.gtkrc-2.0.mine:8: Файл с изображением не найден в pixmap_path: «rox-select.png»

[Member Dzhigit]

Helpful

Up

0

::

Sorry if this gets sent twice, if it does then I sent it again because I don’t think it worked the first time. Running volumeicon just shows errors about missing icons, all of which are icons belonging to the icewm-icons-papirus-antix package, which is a package I apt-get purged. But volumeicon works perfectly.

$ cat ~/.desktop-session/log | grep volume
volumeicon: alsa_backend.c:86: asound_get_volume: Проверочное утверждение «m_elem != NULL» не выполнено.
$ volumeicon 
/home/Maksim/.gtkrc-2.0.mine:6: Файл с изображением не найден в pixmap_path: «rox-show-hidden.png»
/home/Maksim/.gtkrc-2.0.mine:7: Файл с изображением не найден в pixmap_path: «rox-show-details.png»
/home/Maksim/.gtkrc-2.0.mine:8: Файл с изображением не найден в pixmap_path: «rox-select.png»

[Member Xecure]

Helpful

Up

0

::

After running it does the icon appear on the task bar?
If it does, you could maybe add a bit of a delay to volumicon startup.
Two methods:
A) Add delay to the general startup file. Edit ~/.desktop-session/desktop-session.conf variable STARTUP_DELAY. For example, adding an extra 1 seccond:
STARTUP_DELAY="3"
B) Add a delay inside the ~/.desktop-session/startup file only for volumeicon:
sleep 1; volumeicon &

It is just a guess. On one of my devices (that has a somewhat slow CPU) I need to add a bit of a delay for some of the startup programs.

If this doesn’t help (adding a bit of a delay), open a new thread asking about this specific problem (so it is easy to identify by other forum users) and maybe someone with more experience can help with this problem.

When you have time, please edit the post title and add [Solved] to it.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Author]

Posts