Yes, that already has been mentioned.
And I guess his /tmp or /var/tmp directories have wrong permissions as well…
Thanks for all the suggestions while I was asleep.
My partition setup is partly habit, but I don’t think it’s totally insane.
- I use /data as my sole non-system partition, as I like keeping some stuff outside of user homes. I also sometimes access files in /data dual-booting, and it means I don’t need to let windows transverse my home.
- My only *real *
home is in /data/home, and rather than using a symlink or loop mount in fstab I take the insane route of assigning the user home using the option provided in YAST. - When I fresh install I usually put the first user in /home so everything on the / partition is happy as a system, then add my real user to /data/home.
So apart from the setup being unconventional, I channel your collective wisdom as follows:
- The partition setup may be unconventional, but working fine and this on other machines from 8.something through to 12.3 until yesterday.
- Ignore that I even have a /data partition, and ask ‘why can’t a user newly created by YAST (u3), log in’
… and yes, now that I think about it 700 on / doesn’t look so good.
No idea how that happened, but now all fixed:
GERTY:~ # chmod 755 /
GERTY:~ # ls -la /home
total 20
drwxr-xr-x 5 root root 4096 May 31 23:38 .
drwxr-xr-x 28 root root 4096 Jun 1 08:28 ..
drwxr-xr-x 26 u1 users 4096 Mar 1 19:10 u1
drwxr-xr-x 23 u2 users 4096 Apr 17 15:44 u2
drwxr-xr-x 7 u3 users 4096 May 31 20:58 u3
GERTY:~ #
History has shown
- root partition full (usually /tmp ful)
- ownership of ~/.ICE authority and ~/.Xauthority files taken over by root.
- something broken in the desktop config files (which desktop??)
- problem with graphics driver (which)
9 time out of 10 it is one of those
with you description it sounds like you /data/home is FAT or NTFS.
Is that really acting as a home or just a place to keep stuff? Windows file systems don’t have the same permission bits as Linux so ownership is somewhat fuzzy. If you have things pointing to a FAT/NTSF partition as a real home location then there is bound to be problems.
Thanks gogalthorp - turns out this is the 1 out of 10 it was something different!
Turns out that an app install (the 0.10 release candidate for the Insync Google Drive client -which is looking pretty good) reset the permissions on / to 700 -everything you cover was actually fine.
Sorry if my descriptions were vague but the /data partition that m*y **real *home is definitely ext4 not ntfs.
All back to normal now - and I’ve fired a note to Insync…
On 06/01/2013 08:46 AM, agt499 wrote:
> Turns out that an app install (the 0.10 release candidate for the
> Insync Google Drive client -which is looking pretty good) reset the
> permissions on / to 700 -everything you cover was actually fine.
well, if Google has released an app candidate which changes
permissions so rudely, i would suggest you write Google and remind them:
Do no Evil!
–
dd
On 05/31/2013 05:36 AM, agt499 pecked at the keyboard and wrote:
> Hi all.
>
> After a reboot today (kernel update, but had started OK the first time
> after this), my user account is not longer able to login.
> Things I’ve tried/established so far:
> -I’ve fscked the partition
> -the home directory and its permissions look fine, and I did a chown -R
> just in case.
And just what did you change the ownership to? /home needs to owned by
root with the home folders under /home owned by the respective user.
Ken
I’m having similar problem - my home is mounted - but in home - there is only : lost+found, linux~ ( which is the root’s “home”) - and it seems user robert ( which is only one userI’ve created) is in that linux~ dir ( /home/linux~) instead of /home/robert. I’ve no problem with full disk I’ve lot of free space everywhere
No, it’s not.
/root is the root’s “home”.
/home/linux~ is a backup of the LiveCD user’s home.
- and it seems user robert ( which is only one userI’ve created) is in that linux~ dir ( /home/linux~) instead of /home/robert.
Not really, see above.
But I’d say just rename that directory to “robert” and change the owner if necessary.
And please don’t double-post. This is the same issue as http://forums.opensuse.org/showthread.php/500197-boot-problems-check-cable-connection-PXE-more-active-partition?p=2658791#post2658791 , right?
You should have mentioned that your /home is encrypted here as well though. This might be crucial information.
Is your correct /home mounted at all?
solved - so I log in as root did this : mkdir
/home/robert
cd /home/linux~
cp -R * /home/robert
chown -R robert.users /home/robert
then log out and log in as robert
And why didn’t you just rename it? 
mv /home/linux~ /home/robert
As I said, this is just a backup of the LiveCD user’s home (“linux”). You don’t need it anyway.
And as I wrote in the other thread, your actual /home/robert might be in /home on the / partition.
Probably /home was not properly mounted when the user was created.
So have a look there and delete it if you don’t need it.
yeah I could rename it too but that was laso some toher strange thing bout it - user was 999 and not robert ? but anyway it’s working
So what?
You had to run chown anyway…
And there’s nothing strange with the ownership really. As I wrote it was supposed to be the LiveCD user’s home directory (“linux”), not robert’s.
but anyway it’s working
Right.