Bug 57887

Summary:	After running su, user/session looses active state
Product:	systemd	Reporter:	Arne Stäcker <arne.staecker>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium	CC:	thilo.wiesner
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Arne Stäcker 2012-12-04 17:42:42 UTC

I'm running Gentoo and systemd 196.

When I run 'su' in a terminal under KDE and switch to root, my normal user and user's session looses the "active" state and switches to "online". And so my normal user looses all device file permissions. After exit the su mode, the state is still "online".

Last know working version was 193. Could't test intermediate versions because of bug #55656.

Before 'su':
$ loginctl show-session 1
Id=1
Timestamp=So, 2012-12-02 23:27:45 CET
TimestampMonotonic=4397266
DefaultControlGroup=name=systemd:/user/arne/1
VTNr=7
Display=:0
Remote=no
Service=kde-np
Leader=301
Audit=1
Type=x11
Class=user
Active=yes
State=active
KillProcesses=no
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
Name=arne

$ loginctl show-user 1000
UID=1000
GID=1000
Name=arne
Timestamp=So, 2012-12-02 23:27:45 CET
TimestampMonotonic=4390137
RuntimePath=/run/user/1000
DefaultControlGroup=name=systemd:/user/arne
Display=1
State=active
Sessions=1
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0

After 'su':
$ loginctl show-session 1
Id=1
Timestamp=So, 2012-12-02 21:28:24 CET
TimestampMonotonic=4368073
DefaultControlGroup=name=systemd:/user/arne/1
VTNr=7
Display=:0
Remote=no
Service=kde-np
Leader=298
Audit=1
Type=x11
Class=user
Active=no
State=online
KillProcesses=no
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
Name=arne

$ loginctl show-user 1000
UID=1000
GID=1000
Name=arne
Timestamp=So, 2012-12-02 21:28:24 CET
TimestampMonotonic=4360683
RuntimePath=/run/user/1000
DefaultControlGroup=name=systemd:/user/arne
Display=1
State=online
Sessions=1
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0

Comment 1 Pavel Procopiuc 2013-01-10 14:40:20 UTC

The same bug affects me too. I've done investigations and found out that the bug was introduced in systemd-196 by the commit 978cf3c75fbd94fd0e046206ada6169b35edd919

You can view it online: http://cgit.freedesktop.org/systemd/systemd/commit?id=978cf3c75fbd94fd0e046206ada6169b35edd919

Reverting this commit in systemd-196 sources fixes the problem.

Comment 2 Arne Stäcker 2013-01-11 11:02:44 UTC

Just tried the same, but then I run again into bug #55656 as the commit fixes the bug.

Comment 3 Arne Stäcker 2013-01-19 13:19:41 UTC

No change with 197. When I have time, I will do a git-bisect.

Comment 4 Arne Stäcker 2013-04-15 07:59:09 UTC

Works again with systemd 199 and above. Thanks to all developers.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.