Hi. EndeavourOS/Arch Newbie, I am trying to figure out why 5 instances of Barrier are autostarted at boot. I am using the latest plasma on x11. Where should I look for that to find what is starting this process?
I assume there are several places the app is called.
Thanks a mil
Welcome @B1r0 to the forum!
I think your program is in autostart? Maybe you don’t start with a clear session, but with the programs of latest login or a defined session, where those instances were launched?
I enabled it to autostart in the application itself, but I had some issues, so I disabled it in the app, and added the link to the Autostart in the system’s settings.
The strange thing is sometimes it show only three times, but usually five times.
I suspect that the program added itself to some other places where things gets autostarted.
I am not familiar with Arch, maybe it is in some sort of init script?
What does ~/.config/ksmserverrc
contain?
One thing I’ve done with my system is turn off session restore (start with empty session) and just set applications to start when logging in. I found that some apps did not like restoring.
Spot on!
[LegacySession: saved at previous logout]
count=0
[Session: saved at previous logout]
clientId1=108cd4e0d0000172906694000000012150006
clientId2=108cd4e0d0000172883590200000012180004
clientId3=108cd4e0d0000172848946100000012110007
clientId4=108cd4e0d0000172829038300000012720006
clientId5=108cd4e0d0000172883590200000012180009
clientId6=108cd4e0d0000172929026300000011850009
count=6
program1=/usr/bin/barrier
program2=/usr/bin/barrier
program3=/usr/bin/barrier
program4=/usr/bin/barrier
program5=/usr/bin/megasync
program6=/usr/bin/firewall-applet
restartCommand1=/usr/bin/barrier,-session,108cd4e0d0000172906694000000012150006_1729290323_591749
restartCommand2=/usr/bin/barrier,-session,108cd4e0d0000172883590200000012180004_1729290323_591754
restartCommand3=/usr/bin/barrier,-session,108cd4e0d0000172848946100000012110007_1729290323_591755
restartCommand4=/usr/bin/barrier,-session,108cd4e0d0000172829038300000012720006_1729290323_591687
restartCommand5=/usr/bin/megasync,-session,108cd4e0d0000172883590200000012180009_1729290323_591684
restartCommand6=/usr/bin/firewall-applet,-session,108cd4e0d0000172929026300000011850009_1729290323_591758,-name,firewall-applet
restartStyleHint1=0
restartStyleHint2=0
restartStyleHint3=0
restartStyleHint4=0
restartStyleHint5=0
restartStyleHint6=0
userId1=b1r0
userId2=b1r0
userId3=b1r0
userId4=b1r0
userId5=b1r0
userId6=b1r0
I’ve disabled the session restore option, and now I have only one barrier running.
It is strange that I never said to save a session and it did.
I usually run poweroff
from the launcher, and when I do it through the menu shutdown, there is no option to save the session.
@ajgringo619 and @Enthrall
Thank you both for guiding me to the answer.
Session restore is on by default for logouts. You can set it to manual and it should prompt a confirmation. Also if you’re interested in barrier there is a newer fork called input leap.