Closed dragonnn closed 10 years ago
Nod, I haven't had time to update the code to work for v206+. Sadly, help will be appreciated.
This could be completed - because in 206 the have changes the uses session management - now when an user login the is automatically starts the user@.service, me temp solutions is edit the user@1000.service and add the Environment options from user-session@.service and and a service with creates screen session for my user - this start automatic the user@.service
I believe this should be closed now that user-session@.service
has been removed in favor of the new launcher.
So now I should use user-session-launch@.service? Just enable this service is enough?
If I understand correctly, yes. The syntax would be user-session-launch@seat0-1000.service
. Any modifications you had previously made to user-session@.service
to set environment variables, etc should now be made directly to user@.service
.
This worked for my thanks ;). So I think this issue can be closed.
The 207 brings some changes to the --user handling, and this brakes user-session-units, the user-session@1000.service start but gives and (code=exited, status=1/FAILED), the user session opens but it is started via user@1000.service.