Francios, All,

  I wanted to take this discussion out of bug 1902 temporarily to see if we
cannot further the issue on list. According to the freedesktop links for
accommodating clean-systemd (consolekit free) user session/process tracking, one
of the tests to establish if session tracking is active is to check:

$ loginctl show-session $XDG_SESSION_ID
Id=1
Timestamp=jeu. 2014-02-20 21:01:46 CET
TimestampMonotonic=14146902
VTNr=7
Display=:0
Remote=no
Service=tdm-trinity
Scope=session-1.scope
Leader=984
Audit=1
Type=x11
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
Name=francois

for the presence of 'Remote=no' and 'Active=yes'. Francios reports that he is
using a consolekit free environment and has provided the output above which
indicates that session tracking is active on his install -- BUT -- he is
experiencing the exact same problems with tdeio_sftp /file/http/ connection
being left open on his install. I have been making very slow progress
understanding what is going on. I think in Francios case he has established
proper 'user session tracking' showing that session tracking can with in TDE in
this case without code changes. However, I think it is the 'user process
tracking' part that is not working and causing the tdeio process to remain open.

What we need to establish is what config Francios is using that allows proper
user session tracking to be established. In my clean-systemd environment, I get:

22:19 valhalla:~> loginctl show-session $XDG_SESSION_ID
NAutoVTs=6
KillExcludeUsers=root
KillUserProcesses=no
IdleHint=yes
IdleSinceHint=0
IdleSinceHintMonotonic=0
InhibitDelayMaxUSec=5s
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
IdleAction=ignore
IdleActionUSec=30min
PreparingForShutdown=no
PreparingForSleep=no

  From the documentation that shows I do not have it configured properly. I
believe it may have to do with differences in the /etc/pam.d config. Francios,
what are you using?

  I think the users 'process' tracking may have to do with code current wrapped
within consolekit preprocessor checks that is not duplicated outside these
checks but is necessary for process tracking in the absence of consolekit. This
is also where I am focusing effort to learn what additions to the
kdebase/tdm/backend code may be needed to comply with the freedesktop.org
systemd environment.

  Francios, let me know your thoughts on this and Slavek let me know if you have
any other suggestions as well. I am encouraged to see Francios has part of the
correct config working.

-- 
David C. Rankin, J.D.,P.E.