| Summary: | Run Level 5 is not all times the same | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | thomas meiner <tho.mei> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | jgrulich, johannbg, jreznik, lnykryn, mbriza, me, msekleta, muadda, ovasik, rdieter, ssahani, s, systemd-maint, than, tho.mei, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-25 23:16:45 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: | |
|
Description
thomas meiner
2016-09-15 08:21:00 UTC
Sounds like a problem with KDE units (some missing dependencies?). It'd be only a systemd issue if units that were declared in dependencies were not started, but nothing in your description indicates this. I don't think it is a problem of KDE, because KDE works as it should when I just start direct to RL5. The problem is that the systemd setup of Fedora does not produce the same status on boot to RL5 and after the command "init 5". That's really not a KDE problem. 'init 3' is the same as 'systemctl isolate multi-user.target', and 'init 5' is the same as 'systemctl isolate graphical.target'. What gets started in the KDE case depends on various dependencies as specified in KDE units. It's not necesarilly expected that booting directly to graphical.target, and isolating multi-user.target and then graphical.target again, because the latter might stop some units which are not specified as a dependency. But this operation should result in working system. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Yeah, later on we hardcoded runlevel5.target to be an alias for graphical.target and it should work properly now (though probably not in F24). |