-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224

> On Tuesday 12 August 2014 20:25:44 you wrote:
>> >>My home directory is a separte hard drive, it is been reused on
>> >> updates or from backus sinceat least 2004. It  has quite abit of
>> >> old config info, some xsession-errors are related to this.  My
>> >> testing of TDE in vm's do not have any issues
>> >>I will try cleaning up my home dir first, thanks for your reponse.
>> >
>> > As a quick test, you can try creating a new account and make sure
>> > that you have no issue with it. If that is the case, the problem is
>> > almost surely related to some old stuff/config still present in
>> > your home folder.
>> >
>> > Cheers
>> >   Michele
>>
>> And if you do manage to find the offending file I'd like to figure
>> out what happened so that we can prevent it occurring for anyone
>> else!
>>
>> Tim
>
>
> I created a new user, I have enclosed a pristine (new
> user) .xsession-errors file. snipped for all the lockfile entries.
>
> I still get the locked session dialog, lots for the new user...on one
> login attempt I never got an unlocked session to use.
>
>
>
> New issues
> 1. the new user does not have 'opt/trinity/bin' or other TDE
> specific entries in PATH ? I use 'adduser' (cli) to create users on my
> system.
> 2. Dual monitor, no panel on one of the monitors
>
> Xsession: X session started for debian at Wed Aug 13 15:26:23 AKDT 2014
> localuser:debian being added to access control list
> [starttde] Starting starttde.
> [starttde] This script is /usr/bin/x-session-manager
> [starttde] TDE version is R14.0.0 [DEVELOPMENT]
> [starttde] TDE base directory is /opt/trinity
> [starttde] TDEHOME is not set.
> [starttde] Set TDEHOME to /home/debian/.trinity.
> [starttde] Setting TDEROOTHOME to /root/.trinity.
> [starttde] XDG_DATA_DIRS: /opt/trinity/share:/usr/local/share:/usr/share
> [starttde] TDEDIR: /opt/trinity
> [starttde] TDEDIRS:
> [starttde] Starting Trinity...
> [tdebuildsycoca] tdebuildsycoca running...
> [dcopserver] DCOP Cleaning up dead connections.
> [starttde] TDE_FULL_SESSION: true
> [starttde] TDE_SESSION_UID: 1003
> [tdeinit] Shutting down running client.
> ---------------------------------
> [dcopserver] It looks like dcopserver is already running. If you are
> sure
> that it is not already running,
> remove /home/debian/.DCOPserver_tdewheezy__0
> and start dcopserver again.
> ---------------------------------
> [kded] Daemon (kded) is already running.
> [tdebuildsycoca] tdebuildsycoca running...
> [tdebuildsycoca] Reusing existing tdesycoca.
> tdeio (KService*): WARNING: The desktop entry
> file /usr/share/applications/usbview.desktop has
> Type=Applications/System/Hardware instead of "Application" or "Service"
> tdeio (KService*): WARNING: Invalid
> Service : /usr/share/applications/usbview.desktop
> [dcopserver] DCOP Cleaning up dead connections.
> [starttde] tdeinit started successfully.
> [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
> [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
> [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
> [kdesktop] SAK driven secure dialog is not available for use (retcode
> 6).  Check tdmtsak for proper functionality.
> [kdesktop] SAK driven secure dialog is not available for use (retcode
> 6).  Check tdmtsak for proper functionality.
> [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
> [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
> [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
> [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
> tdeio (TDEIOConnection): ERROR: Could not write data (pid 5154
> process "nit] media /tmp/tdesocket-debian/tdelauncher9oiZU")
> [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
>
> <snipped ~ 200 deleting lockfile lines>
>
>
> SAK is not enabled in Contro Center
>
> --
> Peace,
>
> Greg

Very strange; it looks like the kdesktop_lock process is continuously
restarting.  I have never encountered anything remotely like this.

Are you certain kdesktop and kdesktop_lock are the latest R14 versions? 
If there is an old 3.5.13.2 or lower kdesktop_lock executable in your path
it might theoretically be able to do something like this.

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iFYEARELAAYFAlPs+7EACgkQLaxZSoRZrGG5GADgjQf1qQqJ2E9jLHGe3WVdodGO
bQERwZm69mv04QDfXk3Ki3ainplDox8GPYDqhroKSjAXe7ffc+wCdg==
=Vo8j
-----END PGP SIGNATURE-----