#systemdunit — Public Fediverse posts

Dear "KDE on Linux with systemd" users,

I have a laptop that refuses to open one application at login, although
- the desktop file exists in ~/.config/autostart,
- the desktop file can be double-clicked and starts the application and
- the application can be started from the CLI

I do not find the right system unit (with systemctl --user), so I guess it might break the parsing in the generator that creates the systemd-user-unit from the desktop file.

The system settings (in "Autostart") just show that "it was not stated yet" (or similar, translated from German).

Any ideas how to debug?

OS is Fedora Kinoite 43, the application is OpenCloud Desktop installed via Nix.

#kde #plasma #kde6 #Fedora #systemd #debugging #linux #SystemdUnit

Dear "KDE on Linux with systemd" users,

I have a laptop that refuses to open one application at login, although
- the desktop file exists in ~/.config/autostart,
- the desktop file can be double-clicked and starts the application and
- the application can be started from the CLI

I do not find the right system unit (with systemctl --user), so I guess it might break the parsing in the generator that creates the systemd-user-unit from the desktop file.

The system settings (in "Autostart") just show that "it was not stated yet" (or similar, translated from German).

Any ideas how to debug?

OS is Fedora Kinoite 43, the application is OpenCloud Desktop installed via Nix.

#kde #plasma #kde6 #Fedora #systemd #debugging #linux #SystemdUnit

Dear "KDE on Linux with systemd" users,

I have a laptop that refuses to open one application at login, although
- the desktop file exists in ~/.config/autostart,
- the desktop file can be double-clicked and starts the application and
- the application can be started from the CLI

I do not find the right system unit (with systemctl --user), so I guess it might break the parsing in the generator that creates the systemd-user-unit from the desktop file.

The system settings (in "Autostart") just show that "it was not stated yet" (or similar, translated from German).

Any ideas how to debug?

OS is Fedora Kinoite 43, the application is OpenCloud Desktop installed via Nix.

#kde #plasma #kde6 #Fedora #systemd #debugging #linux #SystemdUnit

Dear "KDE on Linux with systemd" users,

I have a laptop that refuses to open one application at login, although
- the desktop file exists in ~/.config/autostart,
- the desktop file can be double-clicked and starts the application and
- the application can be started from the CLI

I do not find the right system unit (with systemctl --user), so I guess it might break the parsing in the generator that creates the systemd-user-unit from the desktop file.

The system settings (in "Autostart") just show that "it was not stated yet" (or similar, translated from German).

Any ideas how to debug?

OS is Fedora Kinoite 43, the application is OpenCloud Desktop installed via Nix.

#kde #plasma #kde6 #Fedora #systemd #debugging #linux #SystemdUnit

Dear "KDE on Linux with systemd" users,

I have a laptop that refuses to open one application at login, although
- the desktop file exists in ~/.config/autostart,
- the desktop file can be double-clicked and starts the application and
- the application can be started from the CLI

I do not find the right system unit (with systemctl --user), so I guess it might break the parsing in the generator that creates the systemd-user-unit from the desktop file.

The system settings (in "Autostart") just show that "it was not stated yet" (or similar, translated from German).

Any ideas how to debug?

OS is Fedora Kinoite 43, the application is OpenCloud Desktop installed via Nix.

#kde #plasma #kde6 #Fedora #systemd #debugging #linux #SystemdUnit