Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1932447
Summary: | plasma systemdBoot: autostart items not launched (xdg-user-dirs) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rex Dieter <rdieter> |
Component: | plasma-workspace | Assignee: | KDE SIG <kde-sig> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 34 | CC: | awilliam, jgrulich, kde-sig, me, phoenix_87_c, rdieter, than |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | AcceptedFreezeException | ||
Fixed In Version: | kde-settings-34.0-3.fc34 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-03-03 21:06:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1933312 | ||
Bug Blocks: | 1829023 |
Description
Rex Dieter
2021-02-24 16:04:51 UTC
Per upstream report, This is due to xdg-autostart-generator not supporting startup phases yet. If the desktop file contains the X-GNOME-Autostart-Phase key, the unit will not be generated [1]. [1]: https://github.com/systemd/systemd/blob/c0267a592a2d44c89874249573d53a456ea3756b/src/xdg-autostart-generator/xdg-autostart-service.c#L558 Arg, so "it's a feature" we'll have to workaround somehow. Here's the autostart items on my box with that key (that aren't OnlyShowIn=Gnome) at-spi-dbus-bus.desktop:X-GNOME-Autostart-Phase=Initialization liveinst-setup.desktop:X-GNOME-Autostart-Phase=Initialization spice-vdagent.desktop:X-GNOME-Autostart-Phase=WindowManager xdg-user-dirs.desktop:X-GNOME-Autostart-Phase=Initialization Filed issue against systemd (xdg-autostart-generator), https://github.com/systemd/systemd/issues/18791 xdg-user-dirs workaround commited (kde-settings-plasma): https://src.fedoraproject.org/rpms/kde-settings/c/e62a11ad84c4cfc54b4e75ec52f8bebf287c389a Should be fixed here, https://koji.fedoraproject.org/koji/buildinfo?buildID=1715093 Why do we enable systemd user sessions at all? (As I understand the mailing list thread, the Fedora 34 KDE live image enables it by default.) Was reminded we're frozen for beta, reopening Was reminded we're frozen for beta, reopening FEDORA-MODULAR-2021-2de8bbfa5d has been submitted as an update to Fedora 32 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2021-2de8bbfa5d FEDORA-2021-3519ef4c51 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3519ef4c51 Proposed as a Freeze Exception for 34-beta by Fedora user rdieter using the blocker tracking app because: Due to a quirk of xdg-autostart-generator and plasma now using systemd user sessions, xdg-user-dirs no longer autostart'd as expected, so user directories such as ~/Picutres, ~/Downloads, ~/Documents were no longer being created. This is highly visible, and lots of f34 testers noticed. Only recently discovered the true cause and some workarounds (offered via the bodhi update referenced in the tracker bug). Would be nice papercut to avoid for f34beta if possible to include the workaround. Thanks. FEDORA-2021-3519ef4c51 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3519ef4c51 FEDORA-2021-3519ef4c51 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-3519ef4c51` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3519ef4c51 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. +4 in https://pagure.io/fedora-qa/blocker-review/issue/259 , marking accepted. FEDORA-2021-3519ef4c51 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. I also have the same issue and it does not seem to be related to not generated units. Actually, the units *are* generated (I can see them in "generated.late"), but for some reasons the corresponding applications are not started. This happens specifically with Dropbox and Insync (other applications like Thunderbird work fine). If I set systemdBoot to false, these applications run on startup just fine. Here are their .desktop files as a reference: --- Dropbox --- [Desktop Entry] Name=Dropbox GenericName=File Synchronizer Comment=Sync your files across computers and to the web Exec=dropbox start -i Terminal=false Type=Application Icon=dropbox Categories=Network;FileTransfer; Keywords=file;synchronization;sharing;collaboration;cloud;storage;backup; StartupNotify=false X-GNOME-Autostart-Delay=10 --- Insync --- [Desktop Entry] Categories=Network; Comment=Launch Insync Exec=insync start GenericName=Insync Icon=insync Name=Insync Terminal=false TryExec=insync Type=Application Version=1.0 |