Fix session startup with new systemd, using user@.service mechanism #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[packaging] Fix rpm file list [packaging] Add set-boot-state binary [packaging] Fix start-user-session permission to be executable by user
…now start-user-session.service
…arate it from Jolla contributions
…ontaining only xorg.target) altogether.
|
LGTM! :) Thanks a lot!!! :D |
|
Thanks :) |
locusf
added a commit
that referenced
this pull request
Oct 26, 2014
Fix session startup with new systemd, using user@.service mechanism
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With these patches, we use the new systemd's user@.service to start user services. To this end, start-user-session service becomes a service which logs into 'nemo' user, and user@.service is automatically started by systemd. Boot state setup has become a separate service since start-user-session is now started as nemo user rather than root.
Finally, nemo user is added to users group because battery status information in statefs in only accessible to root and members of users group.