Bug 1929697
| Summary: | Application startup delay after re-login | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | nucleo <alekcejk> |
| 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: | jgrulich, kde-sig, me, rdieter, than |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | plasma-workspace-5.21.2-1.fc34 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-12 01:35:17 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: | |||
|
Description
nucleo
2021-02-17 13:21:39 UTC
If I kill all left user processes after logout and login after that then no delay in applications startup. There are user processes left after logout user 13330 0.3 0.0 19812 11216 ? Ss 15:37 0:00 /usr/lib/systemd/systemd --user user 13334 0.0 0.0 171648 3400 ? S 15:37 0:00 \_ (sd-pam) user 13369 0.0 0.0 9488 4024 ? Ss 15:37 0:00 \_ /usr/bin/dbus-broker-launch --scope user user 13370 0.2 0.0 6028 3400 ? S 15:37 0:00 | \_ dbus-broker --log 4 --controller 10 --machine-id 3e41e674aa6d4bb69cb0fb473436db8a --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000 user 13451 0.0 0.0 155840 5584 ? Ssl 15:37 0:00 \_ /usr/libexec/dconf-service user 13796 0.0 0.0 308292 6556 ? Ssl 15:38 0:00 \_ /usr/libexec/at-spi-bus-launcher But all of them terminated after some time. Sometimes processes are not terminated user 672 0.0 0.2 19704 11372 ? Ss 16:06 0:00 /usr/lib/systemd/systemd --user user 676 0.0 0.0 242476 3120 ? S 16:06 0:00 \_ (sd-pam) user 700 0.0 0.1 9620 4324 ? Ss 16:06 0:00 \_ /usr/bin/dbus-broker-launch --scope user user 701 0.0 0.0 6384 3592 ? S 16:06 0:00 | \_ dbus-broker --log 4 --controller 10 --machine-id ded605307ba2424e8284f527ca35e8f4 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000 user 1790 0.0 0.3 376856 12740 ? S<sl 16:08 0:00 \_ /usr/bin/pulseaudio --daemonize=no --log-target=journal This happens in x11 session, I am not sure about wayland. Variable SESSION_MANAGER is not defined at first login. After re-login this variable is defined and points to non existing file that was created at previous session and deleted after re-login local/unix:@/tmp/.ICE-unix/1948,unix/unix:/tmp/.ICE-unix/1948 After clearing SESSION_MANAGER in konsole with export -n SESSION_MANAGER kwrite starts without delay and error message Looks like this was fixed after update to 5.21.1, SESSION_MANAGER points to existing file. Enforce SESSION_MANAGER is exported before plasmashell is started. https://kde.org/announcements/changelogs/plasma/5/5.21.0-5.21.1/ FEDORA-2021-4cb70a50e5 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4cb70a50e5 FEDORA-2021-4cb70a50e5 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-4cb70a50e5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4cb70a50e5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-4cb70a50e5 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4cb70a50e5 FEDORA-2021-4cb70a50e5 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-4cb70a50e5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4cb70a50e5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-4cb70a50e5 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4cb70a50e5 FEDORA-2021-4cb70a50e5 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-4cb70a50e5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4cb70a50e5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-4cb70a50e5 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |