Sometime since 2023-11-10, when it was created, an email thread with this title disappeared from my email client. Fortunately I had the presence of mind to copy to a text file the contents of that thread; so the content was not lost.
Three people also contributed to this thread, Mike Bird, Thierry de Coulon and Peter. I hope that they at least still have that that thread so they will know what it am talking about in this posting, as it is a continuation of that thread and would not have been possible without their collective help.
I was able to download from the desktop computer a copy of file ‘.xsession-errors’. It is attached to this posting, all 924 linesof it, with the title ‘TDE-xsession-errors.odt’, no more dot and everybody has permission to read it. Interestingly enough, the ‘.xsession-errors’ file for the laptop contains only 894 lines.
After examining the desktop .xsession-errors of all the possibility for errors which could cause TDE not to open, I was able to identify only one, the UID. The .xsession-errors used 1001 as the UID. At some point I changed my default UID from 1001 to 1000. (The UID on the .xsession-errors for the laptop is and always was 1000.)
In view of the foregoing I think the best thing for me to do now is to reinstall Bookworm and TDE completely. For Thierry’s information both computers have four partitions, boot/efi, root (/), /var and /home which is encrypted. I no longer have a swap; I had them since 2008 in several computers – but never were they ever used. ‘Partition’ /tmp is now part of tmpfs and set up as so by a line in the /etc/fstab file.
In retrospect, the original message – Call to lnusertemp failed (temporary directories full ?). Check your installation. – was misleading. If my analysis herein is correct a full temporary directory is not the issue. The command lnusertemp, if it is a command, could refer to a UID number; which it could not do for the desktop but could for the laptop.
One final comment. I will not be able to do the reinstalments before 26 November. I will report results when done.
Regards, Ken Heard
Hi Ken Heard via tde-users,
Am 12.Nov.2023 um 20:11 schrieben Sie:
After examining the desktop .xsession-errors of all the possibility for errors which could cause TDE not to open, I was able to identify only one, the UID. The .xsession-errors used 1001 as the UID. At some point I changed my default UID from 1001 to 1000. (The UID on the .xsession-errors for the laptop is and always was 1000.)
Just a quick question. Have you changed all relevant files thereafter also from 1001 to 1000? [chown -R --from=1001 1000.....], see man chown for exact details.
Regards Peter.
On 2023-11-12 21:13, phiebie--- via tde-users wrote:
Hi Ken Heard via tde-users,
Am 12.Nov.2023 um 20:11 schrieben Sie:
After examining the desktop .xsession-errors of all the possibility for errors which could cause TDE not to open, I was able to identify only one, the UID. The .xsession-errors used 1001 as the UID. At some point I changed my default UID from 1001 to 1000. (The UID on the .xsession-errors for the laptop is and always was 1000.)
Just a quick question. Have you changed all relevant files thereafter also from 1001 to 1000? [chown -R --from=1001 1000.....], see man chown for exact details.
I hope so. In any event, I think that reinstalling everything will do so for me.
Regards Peter. ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On Sunday 12 November 2023 14.11:28 Ken Heard via tde-users wrote:
In retrospect, the original message – Call to lnusertemp failed (temporary directories full ?). Check your installation. – was misleading. If my analysis herein is correct a full temporary directory is not the issue. The command lnusertemp, if it is a command, could refer to a UID number; which it could not do for the desktop but could for the laptop.
So you changed you user UID, but you don't say how.
I think that for the system a directory that can't be written to can be considered full, as it has the same result.
There are directories for the users in /var/tmp. If your /var/tmp/tdecache-<user> had UID 1001 but <user> has UID 1000 it is not writable and TDE will fail.
Thierry
Actually, here are the disrectories that might be affected:
tmp/tdesocket-<user> tmp/tde-<user> var/tmp/tdecache-<users>
Hi Ken,
some thoughts on the log you provided.
line 24: [starttde] TDE_SESSION_UID: 1001
TDE's start script 'starttde' starts the session as USER with UID 1001.
But it errors with:
line 921: [mcoputils] Error: Can not find password entry for uid 1001.
You get the effective USER ID by running the command (see man id for details):
id -u
On Linux systems the ID of the USER on a single user machine usually is 1000. I suspect that you are running as USER with id 1000 and TDE somehow gets 1001 and then cannot access certain directories or files to complete its startup process.
But that's only guess work from my side. As it is not clear to me, how you installed your desktop system (on which linux system) I have no idea how you got into that situation.
The USER ID (and group ID) are defined in a file /etc/passwd, for example:
user:x:1000:1000:,,,:/home/user:/bin/bash
You could check that on your system.
I'm not shure why TDE on your system starts with USER ID 1001 but a possible explanation is that your /etc/passwd says:
user:x:1001:1001:,,,:/home/user:/bin/bash
In that case all files owned by user should be owned by the user with these UID/GID's.
Hopefully that helps to investigate further and avoid a reinstallation.
Cheers, Stefan
-
Ken Heard -
phiebie＠drei.at -
Stefan Krusche -
Thierry de Coulon