Hi,
How is it possible to configure TDM / TDE so that it does allow any user
to have more than one session? TDM/Trinity after update to R14, will
actually start a second session but the first goes looked.
Example:
On server logged as supervisor, then on thinstation too, on server goes
the session locked.
on .xsession-errors
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0xcff130
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x92ccc0
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x176a220
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x25b0130
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x1317e30
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x22511b0
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x1e2e000
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x155a100
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x806130
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x25d0080
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x1771300
Thanks,
Show replies by date
More info about the enviroment.
I'm using R14 from rpm repo for Centos7.
I have updated from R3.5.13.x.
I start X from the command line with startx or in graphical mode with TDM.