Bug 1201728 - KDE Plasma (and systemd) does not launch desktop files with X-GNOME-Autostart-Phase anymore
Summary: KDE Plasma (and systemd) does not launch desktop files with X-GNOME-Autostart...
Status: RESOLVED UPSTREAM
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma) (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on: 1201421
Blocks:
  Show dependency treegraph
 
Reported: 2022-07-20 15:12 UTC by Fuminobu Takeyama
Modified: 2023-11-03 14:30 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fuminobu Takeyama 2022-07-20 15:12:48 UTC
KDE Plasma now use systemd-xdg-autostart-generator to launch applications specified in /etc/xdg/autostart (/usr/etc/xdg/autostart).

According to [1], it ignores desktop files containing the following entries

* Hidden, X-systemd-skip
* X-GNOME-Autostart-Phase

Due to this specification, some applications are not launched under KDE Plasma session anymore.
As far as my quick survey, the affected applications include

* ibus-autostart.desktop (#1201421)
* pkcs11-register.desktop
* spice-vdagent.desktop
* xdg-user-dirs.desktop
* fcitx-autostart.desktop

I am not sure if Plasma should handles desktop files with X-GNOME-Autostart-Phase or not as GNOME Shell might does.

And also, the upstream maintainer is saying that we should stop .desktop and migrate to systemd .service [2].

Regarding to ibus-autostart, I will remove X-GNOME-Autostart-Phase, which is meaningless for it.
But how should we fix other desktop files?


I also found a related report in Fedora [3]

[1] https://www.freedesktop.org/software/systemd/man/systemd-xdg-autostart-generator.html
[2] https://github.com/systemd/systemd/issues/18791
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1932447
Comment 1 Fabian Vogt 2022-07-25 06:28:52 UTC
Yes, this is a known issue and being discussed upstream in the issues you linked. See also https://bugs.kde.org/show_bug.cgi?id=455992.

> And also, the upstream maintainer is saying that we should stop .desktop and migrate to systemd .service [2].

Where? Except for specific cases, that's just wrong - that would break compatibility without systemd startup and IMO it's systemd's job to handle .desktop files properly if they want it to be part of desktop startup.
Comment 2 Fabian Vogt 2022-07-25 06:30:45 UTC
IMO the right solution is to either get systemd upstream to just ignore the key completely or DEs would have to supply their own xdg-autostart-generator which does so.

Alternatively, the key needs to be removed from all .desktop files.
Comment 3 Fuminobu Takeyama 2022-07-25 14:39:16 UTC
> Where?
https://github.com/systemd/systemd/issues/18791#issuecomment-785776043
https://github.com/systemd/systemd/issues/18791#issuecomment-957330719


Is this really resolved by upstream (KDE or systemd)?
I thought we have to find such desktop files and fix them all.
Comment 4 Fabian Vogt 2022-07-25 14:59:14 UTC
(In reply to Fuminobu Takeyama from comment #3)
> > Where?
> https://github.com/systemd/systemd/issues/18791#issuecomment-785776043
> https://github.com/systemd/systemd/issues/18791#issuecomment-957330719
> 
> 
> Is this really resolved by upstream (KDE or systemd)?
> I thought we have to find such desktop files and fix them all.

IMO this should be discussed upstream first.
Comment 5 OBSbugzilla Bot 2023-02-20 15:25:02 UTC
This is an autogenerated message for OBS integration:
This bug (1201728) was mentioned in
https://build.opensuse.org/request/show/1066853 Factory / systemd-presets-common-SUSE