Quote:
Originally Posted by jschiwal
I don't understand what you mean by having a lot of user id's. If you create a new user, on the other hand. And this user doesn't have the same problems, then it sounds like your configurations are mucked up somehow.
Simply changing your UID could cause problems because your own files will have permissions for another user. If you've been doing this, changing your UID without using chown on all your personal ooo configuration files could be the reason that ooo is locking up for you.
|
...
OK. Step by step:
- ex. I've UID=1000, I can't start any progs from OOo
- I change UID to 1001, chown -R on my /home/user dirs and files, OOs starts normaly...
- after some days (sometime weeks, months...) on UID=1001 , my OOo crashes again, no chance to start any apps from OOo
- I change to UID=1003, no problems, OOs starts again
- But , when I can change UIDs to previously used (1000, 1001) to check, that is OK or NOT, my system remembers the blockage of OOo

- root can starts every apps from OOo without problem, but I use root's account not sporadic, (I use sudo su on normal accounts). But when my system will do this on UID=0 (it's possible), what will be next UID for root

?
- I haven't any messages when I start apps from OOo under X
- No infos in logs...
It isn't the problem with permissions on folders, because I chowned OOo dirs to ex. user.users, all libs into usr, kde too.
Anywhere, my system holds information what are relations between OOo and UIDs..., the question is: where...