Bug 623561
| Summary: | prefdm.service should wait for livesys.service | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||||
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 14 | CC: | lpoetter, metherid, mschmidt, notting | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | systemd-7-3.fc14 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-08-19 01:09:27 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers correction: it should wait for livesys-late.service , not just livesys.service . updated patch attached. this does 'the right thing' in my hang test... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 438364 [details]
updated version of the patch
systemd-7-3.fc14 has been submitted as an update for Fedora 14. http://admin.fedoraproject.org/updates/systemd-7-3.fc14 Given when prefdm historically starts, shouldn't it just be after local.service instead? bill: I think it's more correct to think of the relationships as being 'dependencies', since systemd is intended not to be sequential at all. we can't necessarily assume that local.service is being started after livesys-late.service unless they have that relationship expressed between them... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers We sort of can, due to the fact that it sets SysVStartPriority. Of course, it's possibly better defined as a target, since it by definition needs to be After: everything-else. systemd-7-3.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update systemd'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/systemd-7-3.fc14 I generally believe that we should keep the amount of synchronization and dependencies at a minimum. That means that I'd rather not add an ordering dep between local.service in prefdm.service systemd-7-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 438357 [details] patch to add the dependency to prefdm.service When booting a Fedora live service, a livesys service can potentially make some changes to X configuration (it has special case X configs for some OLPC devices, and it should configure X to use a specific driver if you pass the parameter xdriver=foo - this doesn't currently work, but I'm submitting a patch for that to spin-kickstarts). However, in systemd, prefdm.service isn't configured to wait for livesys.service, so these X config changes aren't actually respected (at least in my test systems) because systemd manages to start X before livesys service gets to making the changes. prefdm.service should be patched to have After = livesys.service . Patch attached. (Testing this is a bit tricky because you need a non-Intel, non-Nvidia system to be sure, and it seems like kvm vms currently hang if you try to use the vesa driver. So for now, my 'test' for this is to boot a live image with the fixes to systemd and spin-kickstarts, and pass parameters 'xdriver=vesa nomodeset'. If the live image gets to a graphical desktop using the cirrus driver it's broken, and if the live image completely freezes on X start, it's working!)