I use linux neon user edition.
I have installed qsynth and added it to the autostart section in the settings. In qsynth is an option to 'start minimized to tray'. This worked great. Qsynth started automatically in the background. A week ago after updating Neon qsynth did not start minimized anymore.

I tried to fix this problem with reinstalling and removing the configuration files (.config/rncbc.org/Qsynth.conf). But Qsynth started normal (not minimized). I also did a few things I cannot remember.
After several attempts I decided to start qsynth manually so I removed it from autostart.

Now I have the strange situation that qsynth acts exactly the way I want it to do. It starts automatically and stays in the background.
(pidof qsynth -> 1478, so the proces is running)
But qsynth is no longer an autostart application. There also is no qsynth.service available.

My question is: how does linux start qsynth automatically at every boot? Where can I find information on this?

$ ps -Ae f | less -S

Search for 'qsynth' in tree and check its parents' configurations.

Thanks for the help. This is what I find:

pifoff qsynth -> 1551
ps -Ae f | less -S > text.txt -> " 1551 ? Sl 1:43 \_ /usr/bin/qsynth -session"

I do not know how to search any further.
There must be somewhere a command that starts qsynth.

I downloaded the packacke 'qsynth' manually, and
looked at its content.

The package itself doesn't autostart.

Therefore, either Your own activities or some plasma mechanism
is responsible for its start.

qsynth can be started as a daemon per command-line switch.
That has to be written down somewhere, else it wouldn't start this way.

To know where/by whom it's started, You need to know
the parents/ancestors whose child this process is:

Example: Who's starting and possibly pre-configuring
the KDE desktop UserLogin session?

Who starts/whose child is <P>rocess PID of kdestart?
<P>arent<P>rocess PPID: sddm-helper!

# Code

Code: Select all

USER       PID  PPID  CMD
root      1226     1  /usr/bin/sddm
root     23176  1226  \_ /usr/lib/xorg/Xorg -nolisten tc
root     23213  1226  \_ /usr/lib/x86_64-linux-gnu/sddm/
You      23224 23213    \_ /bin/sh /usr/bin/startkde
You      23288 23224        \_ /usr/bin/ssh-agent /usr
You      23344 23224        \_ kwrapper5 /usr/bin/ksms


From you reaction I understand that I should look for the parent of the process qsynth. I did not see what command you used in your example. I used pstree -pn and found the following:
systemd(1)-+-systemd-journal(319)
.............
|-kdeinit5(1398)-+-klauncher(1399).........
| -kded5(1402)..............
| -ksmserver(1460)..........
| -org_kde_powerde(1480)...........
| -qsynth(1499)-+-{QXcbEventReader}(1521)
| |-{QDBusConnection}(1524)
| |-{qsynth}(1547)
| |-{threaded-ml}(1925)
| |-{qsynth}(1926)
| `-{qsynth}(1927)
.............................
(I only copied the relevant text fragments)
so the parent of qsynth(1499) must be kdeinit5(1398)
Now I think I must look for the configuration files of kdeinit5.

The file kdeinit5 exists in /usr/bin bit wher can I find the configuration files?

Use this (long) command line and look under PPID.
That's what I intended.

# This is one single line: From 'comm…' to '…ess -S'.
$ command ps -w -w -o user,pid,ppid,command -Ae | command grep -E 'PID|qsynth' | command grep -v grep | less -S

As for the rest: I think You got my meaning.

I don't want to install it myself, because the developers themselves
in their README file describe their software as BETA.

Create a second user account.
Use it to log in into KDE.
If qsynth isn't running, then
the culprit lives in Your original account's
home directory.

You then know, where to search.

If You don't know, how to search: Ask again.

The result of the command is:
USER PID PPID COMMAND
peer 1458 1361 /usr/bin/qsynth -session 104e656f6e000149292742100000015030007_1493532091_129219
I also added a new user and then qsynth started not automatically

So I have to look in my own home directory. I think I need startup configuration files for KDE but I do not know where exactly to look for.

Repeat the command line whose output You posted last,
to get the current numbers.

Then do:

$ command ps -w -w -o command <the-PPID-is-to-be-inserted-here>
COMMAND
<the-parent's-command-line-will-appear-here>

# Looks similar to this ('$$' replaced by PPID-number; would have been
# 1361 previously):
$ command ps -w -w -o command $$
COMMAND
/bin/bash

Post back the _c_o_m_p_l_e_t_e_ output You get.

Then You'll know, who/what started qsynth and You can begin
a targeted search for the starter's (parent's) configuration files.

current PID: 1454
current PPID = 1368
$ command ps -w -w -o command 1369
COMMAND
kdeinit5: Running...

I think we are repeating now. This command shows the parent process: kdeinit5
We already found this parent process earlier.
The question is now: Where can I find the configuration files for kdeinit5
(I am learning here!! )
I allready google this question is but I have not found an answer yet. I appreciate it if you can help me further

1. We are not repeating. Don't want to explain for now.
2. One of Your PPIDs is wrong.

Short Explanation:

1. You're running a BETA-KDE-4 application within
KDE-5. Could lead to unusual behaviour.

2. We need the full command line of the parent process
not only its name. To know its parameters.

3. If it really is kdeinit5: Fine!
But I'd suspect ksmserver… Maybe, that's wrong. Let's see.

4. Next steps depend on correct info.

And if it's not a configuration file,
then it may be outdated cache files
under "${HOME}/.cache/"…

I made a typo on the second line, he PPID.
The command and output should be:
current PID: 1454
current PPID = 1369
$ command ps -w -w -o command 1369
COMMAND
kdeinit5: Running...

When I use the pstree command I find:
$pstree -pn
output is complete tree. Here is the branch for qsynth:
systemd(1) -> kdeinit5(1470) ->qsynth(1556)