-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
When reading the thread "Lockups after
unlocking screensaver", it
reminds me an unanswered question I had months ago.
I use Trinity 3.13.2 on Ubuntu 12.04 LTS. As far as I can recall
(years), my TDE session started on vt7 (Ctrl-Alt-F7).
After a power outage, I restarted my box and ever since TDE starts on
vt8 (Ctrl-Alt-F8).
Everything works well but I would like to understand the reason of this
vt switch.
I searched the web for an answer with no success.
Does someone on this list has an answer?
Nothing harmful, no bug, but curiosity... is on mars now :-)
midi-pascal
I'd look for stale Xorg lockfiles in /tmp; if Xorg
"thinks" there's a
session already active on VT7 it will start the next one on VT8. This
isn't an issue on boxes where /tmp is mapped to tmpfs, but I know there
are people who like to map /tmp to persistent storage so I thought I'd
mention it.
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlSB6z0ACgkQLaxZSoRZrGGXqQDfXoMa8jDHKghnXuI611mGuHNG
gmgCfcU5d6A2WADeK+6oFdNhI0uIbfWQRdQJeuJ2RBBr9wvK47+qNQ==
=Pc3H
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting Thanks for this quick
and interesting reply Tim.
Actually my /tmp is mapped to tmpfs so I assume it is cleared on each
reboot.
There should not be any lock surviving a reboot in this configuration.
This is why I am so curious on what caused the vt switch - and how to
revert it -.
The X server shows:
$ ps -ef | grep X
root 1301 858 2 12:47 tty8 00:02:58 /usr/bin/X -br -nolisten
tcp :0 vt8 -auth /var/run/xauth/A:0-uTXGia
So X is clearly started with the "vt8" param but I do not know enough
about X management to find out which process provides the param.
I think I found a hint on what is happening while booting:
If I do a [Ctrl]-[Alt]-F7 after a fresh boot while [Ctrl]-[Alt]-F8 shows
the login screen, the vt7 shows the Ubuntu Splash screen with the
message "Waiting for network for another 60 seconds..." (I do not
remember the entire message though) so it looks like TDE tries vt7 first
and switches to vt8 because there is something wrong in vt7 (my guess).
I have no clue on what could be wrong for vt7 and right for vt8 on the
same box!
Still searching...
midi-pascal