When I install dnscrypt-proxy, I found no dnscrypt-proxy.service here. I write a bash to launch it, and write a desktop file here, ~/.config/autostart/dnscrypt.desktop #!/bin/bash zenity --password --title="sudo"|tr -d '\n'|sudo -S dnscrypt-proxy -R cisco -a 127.0.0.2:53 -u whoami But it no work after input password. I can not found gksudo and gnome-keyring-query in the repo, so I use zenity.

In systemD, we need to execute this command to autostart an application on system startup: sudo systemctl enable . What will be the equivalent command for sysvinit since chkconfig is no longer supported? I could not find any.

configured guake terminal to autostart at login, in startup ubuntu app \ The command is: guake --show -e "sudo nethogs -b" When I reboot, or logout and login, the terminal starts, but if \ I open the startup ubuntu app, the entry I added is disappeared \ I created a file in .config/autostart/ dir and the same thing \ happens, run once then the file disappeared \ Any idea ?

I have zsh and oh-my-zsh installed but my terminal (xfce4-terminal on [EndeavourOS](https://endeavouros.com/) (Arch-based)) always starts in bash.

Why was sysv-rc-conf removed from the Debian repos? Is there for example a better alternative with a GUI? When I run sudo apt-get upgrade it's the only package held back:

The following packages have been kept back:
  sysv-rc-conf

When I run sudo sysv-rc-conf I can still configure autostarting services in the console. I find it difficult to use as it's not a GUI and has just unexplained numbers as columns. Nevertheless, instead of removing I'd like to install some substitution tool that can also configure autostarting services.

Description: SysV init runlevel configuration tool for the terminal
 sysv-rc-conf provides a terminal GUI for managing "/etc/rc{runlevel}.d/"
 symlinks.  The interface comes in two different flavors, one that simply
 allows turning services on or off and another that allows for more fine tuned
 management of the symlinks.  Unlike most runlevel config programs, you can
 edit startup scripts for any runlevel, not just your current one.

It probably has something to do with "orphan-sysvinit-scripts" showing up in KDE Discover and Apper to be installed (but getting installed or upgraded when upgrading).

I've been troubleshooting an issue with a sysVinit service not coming online properly at boot within a systemd environment. What I've found is that when no service file or overrides are present in /etc/systemd/system/ for the said service, it autostarts properly. In this case, as I understand it, systemd should be dynamically loading the startup script via reading "legacy" sysvinit scripts present on the system, although I'm not 100% clear on that. What I'm confused about is that as soon as I pass the edit --full option to systemctl for said service, a flat file is generated at /etc/systemd/system/ and said service now fails to autostart at boot. Using the edit option and trying to add any overrides also seems to cause the service to fail to boot. Examples, if needed, provided below... ### Example of the system when it works The service (on Centos), in this example called "ProgramExample" has an init script placed in /etc/init.d/programexample and also /etc/rc.d/init.d/programexample: # ls -l /etc/rc.d/init.d/programexample -rwxr-xr-x. 1 root root 2264 Mar 29 14:11 /etc/rc.d/init.d/programexample No service file present at /etc/systemd/system/: # ls -lh /etc/systemd/system/programexample.service ls: cannot access /etc/systemd/system/programexample.service: No such file or directory Systemctl status output in this configuration: # systemctl status programexample.service ● programexample.service - LSB: Start Program Example at boot time Loaded: loaded (/etc/rc.d/init.d/programexample; bad; vendor preset: disabled) Active: active (exited) since Wed 2017-03-29 15:53:06 CDT; 14min ago Docs: man:systemd-sysv-generator(8) Process: 1297 ExecStart=/etc/rc.d/init.d/programexample start (code=exited, status=0/SUCCESS) Mar 29 15:53:05 centos7-box systemd: Starting LSB: Start ProgramExample at boot time... Mar 29 15:53:05 centos7-box su: (to programexample) root on none Mar 29 15:53:06 centos7-box programexample: ProgramExample (user programexample): instance name set to centos7-box Mar 29 15:53:06 centos7-box programexample: instance public base uri set to https://192.168.0.148.programexample.net/programexample/ Mar 29 15:53:06 centos7-box programexample: instance timezone set to US/Central Mar 29 15:53:06 centos7-box programexample: starting java services Mar 29 15:53:06 centos7-box programexample: ProgEx server started. Mar 29 15:53:06 centos7-box systemd: Started LSB: Start ProgramExample at boot time. With the above configuration, without any files created/placed in /etc/systemd/system/, the ProgramExample service autostarts properly. **Once systemctl edit --full (or just edit) is used:** Once any edits are passed to systemctl, I have observed the following: - A flat file or an override directory will be placed in /etc/systemd/system/ - Said service, in this case ProgramExample, fails to start at boot. - I will be unable to "enable" said service using systemctl Systemctl status output in this configuration (post edit): # systemctl status programexample.service ● programexample.service - LSB: Start ProgramExample at boot time Loaded: loaded (/etc/rc.d/init.d/programexample; static; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) This is the service file that is being generated and placed in /etc/systemd/system/ when using the edit --full option:

# Automatically generated by systemd-sysv-generator

[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/rc.d/init.d/programexample
Description=LSB: Start ProgramExample at boot time
Before=runlevel2.target
Before=runlevel3.target
Before=runlevel4.target
Before=runlevel5.target
Before=shutdown.target
Before=adsm.service
After=all.target
After=network-online.target
After=postgresql-9.4.service
Conflicts=shutdown.target

[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/rc.d/init.d/programexample start
ExecStop=/etc/rc.d/init.d/programexample stop
ExecReload=/etc/rc.d/init.d/programexample reload

What is happening here? Am I correct that without the flat service file and/or service override directory in /etc/systemd/system/ that systemd is dynamically reading this information from said service's init script? I've tried numerous iterations of editing the service file at /etc/systemd/system/ and leaving the default file in place and cannot get autostarting to work or the service to go into an "enabled" state. I believe it would be preferable to have a systemd .service file for systemd configurations instead of relying on systemd to read from init script LSB headers for compatibility and concurrency reasons, but the default file systemd is creating is failing to start or enable, along with numerous other more simple iterations of the .service file which I've attempted.

When Evolution is installed, my KDE session automatically starts its background services like the calendar alarm notifier. I don't see startup scripts in ~/.config/autostart and have no idea what else may be starting the services. What are the locations that are used for starting programs/background services in a KDE desktop session?

I'm running an ordinary Debian system on which I have installed Zoom. After using Zoom, and quitting, the program keeps restarting. After I kill it I use ps to check and it is gone, after about 15 minutes it returns, I kill it again, and later it returns... When it restarts it always has a ppid of 1 (init). I have checked cron, init.d, systemd and all my dot files and there is no trace of anything that can restart Zoom. What can be doing it? How does it do it? I know it's not really a big deal but it is driving me mad and I want to understand how it happens _and_ I would like it to disappear except when I want to use it.

Basically I want to login in my system and let the system to open for me my Web browser (Thorium). Since I' using Ubuntu 22.04 and I want to start the browser as *user* (and not as *root*), I followed this instruction carefully (using the *--user* option and putting my *.service* script in the *systemd/user* folder). So I have now this configuration: ubuntu@B1:/etc/systemd/user$ cat thorium.service [Unit] Description=Thorium Web Browser [Service] #User=myuser #Group=mypass ExecStart=/opt/scripts/thorium_start.sh [Install] WantedBy=default.target where the AppImage of Thorium is started from this script: ubuntu@B1:/etc/systemd/user$ cat /opt/scripts/thorium_start.sh #!/bin/bash filename="/opt/thorium/Thorium.AppImage" logfile="/tmp/log.txt" echo "Starting Thorium" > ${logfile} echo date >> ${logfile} sleep 30 # /usr/lib/systemd/user/pipewire-media-session.service drwxr-xr-x 2 root root 4096 Jul 21 2023 sockets.target.wants -rwxr-xr-x 1 root root 152 Jul 11 23:15 thorium.service thus the .service file has been correctly configured to start at boot and has execution rights. But the problem is that after login no broswer starts. Doing from terminal a simple: $./thorium_start.sh starts the browser as expected, so I do not think that the problem is the script. Any help? My system is: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS" PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/ " SUPPORT_URL="https://help.ubuntu.com/ " BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/ " PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy " UBUNTU_CODENAME=jammy

I have successfully installed wayland/weston on my system. I would like to start a program (chromium) whenever weston starts. Right now: weston-lauch starts the desktop, from there I can start a terminal and type chromium, what starts chromium. But is it possible to start chromium automatically, just when the desktop is loaded? If so, how? All I can find is how to add a item to the launcher panel…

I have my "c" application which uses a lot of printf to display the necessary information. Application has started automatically at boot time (using init.d or systemd). How I can access to it's console? I am not interesting in all data since application was started. I want to view current data... Should I use tmux?

My computer turned itself off to protect itself from a power-surge. This has happened before many times, with nothing weird happening the next time I turned on the computer. I would press the power button, wait a minute, enter my password, and then be right back at my Desktop. This time however, something different happened. When I press the power button, I am taken to the BusyBox command line. To be completely honest, I am way out of my depth. My only guess for what is happening is that before there was a file that BusyBox automatically ran when the command line was opened upon start-up, and now it does not. This seems pretty absurd to me though because the problem started after a power-surge, which primarily affects hardware, so the software should be fine. Even if this is what happened, I have no idea what file is suppose to be run, where in the directory it would be located, or the syntax that BusyBox uses.

These don't work: sudo update-rc.d kdeconnectd disable sudo systemctl disable kdeconnectd.service There is no script for it in /etc/init.d/ and the /usr/share/dbus-1/services/org.kde.kdeconnect.service file only has Exec=/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd set sysv-rc-conf, rcconf and bum don't list kdeconnect. /etc/xdg/autostart/kdeconnectd.desktop looks like this: [Desktop Entry] Type=Application Exec=/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd X-KDE-StartupNotify=false X-KDE-autostart-phase=0 X-GNOME-Autostart-enabled=false OnlyShowIn=KDE;GNOME;Unity;XFCE; NoDisplay=true (Kdeconnectd has port 1716 open all the time when running.) It's not just starting automatically when booting but also a while after ending the process without me opening it. I'm running Debian 9/KDE. Update: Debian issue now is here

Many GNU/Linux distros come with autostarts configured that are not needed for most users and are a privacy and security risk (even if small). In principle, it makes sense to only autostart things one actually needs to reduce the likelihood of crashes, the number of irrelevant log entries, the hardware resource consumption, and the attack surface (for example due to potential vulnerabilities in any of the software or ports they listen on). A problem is that when upgrading packages or the distro like Debian, the autostart could be enabled again. What is the best way to **permanently** disable autostarting *without* removing the package (which often isn't even possible anyway as the autostarting package comes shipped with some other needed package). At various questions each about one particular undesired by-default-autostarting software different methods to disable the autostart have been recommended: * Removing (or moving) the file in the autostart folder like so for the Orca screenreader sudo rm /etc/xdg/autostart/orca-autostart.desktop * Something like systemctl --user disable at-spi-dbus-bus.service as recommended here for the screenreader KDE Accessible or for the geolocation tracker geoclue-demo-agent.desktop * Removing the executable flag so it needs to first be manually set (with +x) whenever one wants to run the app like sudo chmod -x /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd && pkill kdeconnectd as recommended here for the wireless communication listener KDE Connect * Copying the .desktop file to the .config folder and changing things so that it doesn't autostart (ironically that makes it show up in KDE's System Settings->Autostart while it wasn't shown there before ) for example like so cp /etc/xdg/autostart/org.kde.kalendarac.desktop ~/.config/autostart and then changing crc:General:Autostart:true to false :false in the file in ~/.config as recommended here for Calendar Reminders or adding Hidden=true to that file as recommended here * Renaming the file in /etc/xdg/autostart/to filename.desktop.disabled * Removing it from the D-Bus autostart services /usr/share/dbus-1/services/ or putting a modified version into ~/.local/share/dbus-1/services/ * A combination of the above such as removing the file from the autostart folder but leaving a .config file that should disable the autostart if it gets restored by some upgrade (especially a distro upgrade). Now I don't know which way to use and all the ones I tried seem to get reset after an upgrade. The .desktop file can get overwritten if the package gets upgraded.

I still don't know why KDE Accessible / the screenreader starts automatically and how to conveniently prevent it via KDE's options . In the latest version of KDE that's used by KDE neon I could not find a a way to remove the package to make sure it's not getting started. I'd like to remove or properly disable it because: * I don't need it * it only increases the attack surface of the machine * having a screenreader enabled might be a privacy-related security problem In Debian10/KDE I sued to be able to simply remove kaccessible by running sudo apt-get purge kaccessible. But it looks like it's not installed as a separate package in KDE Plasma 5.20 of the latest KDE neon (no package kaccess or similar is installed). Furthermore, I found that even on Debian 10 kaccess still starts automatically even after purging kaccessible: dpkg -S /usr/bin/kaccess says that it's now part of plasma-desktop and I can't find a way to prevent it from autostarting. I already removed it from autostarts in the settings "Autostart" but it's *still* starting automatically (check whether it's running after booting with the process manager / System Monitor). One workaround seems to be running sudo chmod -x /usr/bin/kaccess (see its location with which kaccess) in the same way as for KDE connect which is similarly annoyingly uncontrollable by the user . Update: It's not a separate package one could remove in Debian11/KDE anymore. Update: Debian issue about it here . Other ways to disable it are here .

I'm running Debian 9.1 with KDE and KDE Accessible / the screenreader keeps appearing from time to time for some reason. I'd like to know *why* that is and how to prevent it from starting. It's not listed in the autostart entries in Background Services nor in the BootUp-Manager (bum). In the Accessibility Options "Screen reader enabled" is not checked. ---- ps -ef | grep access gives me: > /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 > /usr/lib/kde4/libexec/kaccessibleapp The content of /usr/share/defaults/at-spi2/accessibility.conf can be found here . Debian issue for disabling it now is here .

I came across the messages below with sudo journalctl --since today | tail -n 3000. Shouldn't autostart entries be removed from there when removing a package? It seems like general good practice to remove autostart entries if the package has been removed (or to prompt the user about it during removal or to remove them when running a command like sudo apt-get autoremove). Moreover, wouldn't it cause executables to get autostarted if they are named / aliased / linked in the same way the command in Exec there. If this isn't currently done, what would be the right way to auto-remove these entries? Where could an issue about this exist? For now I under Debian12/KDE just moved them like so sudo mv /etc/xdg/autostart/xbindkeys.desktop ~/DisabledAutostarts_defunct/xbindkeys.desktop and hope that is fine as is as a workaround. systemd-xdg-autostart-generator: Exec binary 'xbindkeys_autostart' does not exist: No such file or directory systemd-xdg-autostart-generator: /etc/xdg/autostart/xbindkeys.desktop: not generating unit, executable specified in Exec= does not exist. systemd-xdg-autostart-generator: Exec binary '/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1' does not exist: No such file or directory systemd-xdg-autostart-generator: /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop: not generating unit, executable specified in Exec= does not exist. systemd-xdg-autostart-generator: Exec binary 'gsettings-data-convert' does not exist: No such file or directory systemd-xdg-autostart-generator: /etc/xdg/autostart/gsettings-data-convert.desktop: not generating unit, executable specified in Exec= does not exist. systemd-xdg-autostart-generator: Exec binary 'start-pulseaudio-x11' does not exist: No such file or directory systemd-xdg-autostart-generator: /etc/xdg/autostart/pulseaudio.desktop: not generating unit, executable specified in Exec= does not exist. systemd-xdg-autostart-generator: Exec binary 'kmixctrl' does not exist: No such file or directory systemd-xdg-autostart-generator: /etc/xdg/autostart/restore_kmix_volumes.desktop: not generating unit, executable specified in Exec= does not exist. systemd-xdg-autostart-generator: Exec binary 'kmix' does not exist: No such file or directory systemd-xdg-autostart-generator: /etc/xdg/autostart/kmix_autostart.desktop: not generating unit, executable specified in Exec= does not exist. systemd-xdg-autostart-generator: Exec binary 'usbguard-applet-qt' does not exist: No such file or directory systemd-xdg-autostart-generator: /etc/xdg/autostart/usbguard-applet-qt.desktop: not generating unit, executable specified in Exec= does not exist. Files that cause things to autostart are different from any /etc/ config file which just provides some configs if the application is running. In addition to the problem mention, it can for example even also be a problem when reinstalling a later version of the same software because it could create an additional entry in that folder with another name so it starts twice. Issue is here now.

So I'd like to manage my autostart applications and e.g. disable those which I prefer not to autostart. How can I do that in Debian 9.0? I could not do so via the System Monitor and I'd prefer a GUI over the console. In KDE's System Settings most of the autostarting software is not shown under Autostart (issue here ). Furthermore it would be nice if such a tool also displayed some information about the apps/processes such as what they do, whether they're safe to disable and e.g. things like whether many have them running as well and whether (many/specific) users have flagged them for being undesired.

After upgrading Debian11/KDE to Debian 12, Solaar (for Bluetooth input devices) and onboard (for a virtual touchscreen keyboard) is showing twice in the tray-bar. I checked with the process manager and there only is one process for each of those. **Why are they showing twice, and how to prevent that?** No other are shown twice there. The context menu can be shown for both tray icons of Solaar. The second tray-icon for onboard looks slightly different from the other. When I click on the latter only a context menu is shown, when I click on the first the onboard keyboard is shown so these are definitely different. It may have to do with Plasma tray icon settings files (which should not be screwed up by updating). The four icons look like this in the tray: The second Solaar icon is on the most right of icons in the traybar, right of the network-manager icon. If I quit either application and restart it, only one icon is shown. I used X11 before and after the upgrade. When I switch to Wayland, the Onboard keyboard does show after login but, unlike with X11, it does not show in the tray (Solaar is in the tray with one icon) once I close that keyboard. **Update**: The issue still exists. All packages are up-to-date (Plasma 5.27.5). I made sure there is only one entry for each in /etc/xdg/autostart (make sure the one that remains has "KDE" in OnlyShowIn) and no extra entry in ~/.config/autostart. Both only show once in the processes (underneath branch systemd->systemd). It is strange that on another computer with Deb12/KDE, there is no icon for Solaar (also underneath systemd->systemd) even though it is running with one entry for it in /etc/xdg/autostart where both have Exec=solaar --window=hide and StartupNotify=true. When disconnecting the bluetooth receiver no icon is shown anymore and when reconnecting two icons are shown again. **At another nearly identical Deb12 machine no icon for Solaar is in the tray bar** (Plasma System Tray) except for a short time after connecting the receiver. Maybe there is another way to get info about things showing up in the traybar. A solution to this problem could also be useful for the disappearing tray icon for veracrypt where its GUI can't be opened again due to error "VeraCrypt is already running".

I have a bash script, called runthunderbird, that… runs thunderbird :

#!/bin/bash
sleep 5
thunderbird & disown

When I execute `runthunderbird from krunner, Thunderbird starts after 5 seconds as intended, then the runthunderbird process ends, as evidenced by ps -ef` or the process list in the System monitor from Plasma 5.27.10. However, the same System monitor has an Applications tab where `runthunderbird remains listed, instead of thunderbird-bin`, with the resource (eg. memory) consumption of Thunderbird. If instead of just Thunderbird, the scripts runs several graphical applications before ending, they are lumped together in the Application tab, again under the name of the (terminated) script. I am wondering how this is managed and how I should write my script to completely detach thunderbird from the script than runs it. I am also wondering if this fact is related to Thunderbird not being effectively run when the runthunderbird script is run at login from a desktop file in `~/.config/autostart`.