| Summary: | Systemd startup: things in autostart don't autostart when custom prefix is set late | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Nate Graham <nate> |
| Component: | kcm_autostart | Assignee: | Nicolas Fella <nicolas.fella> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | fuzz, j.straight-kde, katyaberezyaka, kde, kishore96, kyle.devir, nl6720, plasma-bugs, rdieter, tagwerk19, tgnff242 |
| Priority: | NOR | ||
| Version: | 5.21.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=433223 https://bugs.kde.org/show_bug.cgi?id=433299 https://bugs.kde.org/show_bug.cgi?id=434241 https://bugs.kde.org/show_bug.cgi?id=434242 https://bugs.kde.org/show_bug.cgi?id=434243 https://bugs.kde.org/show_bug.cgi?id=455252 |
||
| Latest Commit: | Version Fixed In: | ||
|
Description
Nate Graham
2020-10-04 20:23:36 UTC
*** Bug 427342 has been marked as a duplicate of this bug. *** They do. But there's an issue with the use of a custom prefix. the generator won't find them. My hack covers finding the services in a prefix, it doesn't help solve the case of autostart files in a prefix. I kinda hoped I could just make explicit units for all KDE things and then that problem goes away.... I think I could also explicitly re-run the generator after I set the envs. It'd be expanding the hack, but it's only for dev sessions at least. Could be fixed by: https://github.com/sddm/sddm/pull/1370 (with relevant KDE side changes) *** Bug 434242 has been marked as a duplicate of this bug. *** *** Bug 434243 has been marked as a duplicate of this bug. *** *** Bug 436450 has been marked as a duplicate of this bug. *** The (In reply to David Edmundson from comment #2) > But there's an issue with the use of a custom prefix. the generator won't > find them. Could this be what is causing: https://bugzilla.redhat.com/show_bug.cgi?id=1951580 referring to https://github.com/systemd/systemd/issues/18791 I have guest VM (an upgraded to Fedora 34 machine) that doesn't release the mouse pointer. That seems to be a service provided by spice-vdagent and the autostart spice-vdagent.desktop file includes X-GNOME-Autostart-Phase=WindowsManager Strangely a new/clean install of F34 works, just the upgraded one has trouble |