DU Today Can't Login to KDE Desktop as user

Started by bad_aptitude, 2017/03/03, 17:16:54

Previous topic - Next topic

bad_aptitude

After a DU last night  I can't login to KDE as user. The login screen just goes blank and then cycles back to the login screen.
I am able to login as root.
I performed another DU this morning but this did not help.
I've been upgrading from the same installation for about 3 years.
Has anyone else had this problem?

towo

Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

bad_aptitude

@towo
should I post he entire output of du -h?
running "ls -ld /tmp" after "du -h" just gave me

root@kent_siduction:~# ls -ld /tmp drwxrwxrwt 12 root root 4096 Mar  3 10:32 /tmp

finotti

No sure, but maybe he meant "df -h"?  To check if some partition (like /tmp or /home) is full...

bad_aptitude

here is the result of df -h

root@kent_siduction:~# df -h Filesystem      Size  Used Avail Use% Mounted on
udev            1.9G     0  1.9G   0% /dev
tmpfs           385M  1.3M  384M   1% /run
/dev/sda4        32G   21G   11G  67% /
tmpfs           1.9G   15M  1.9G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/sda1        96M   43M   54M  44% /boot/efi
/dev/sda3        79G   39G   41G  49% /disks/disk1part3
/dev/sda5        25G   12G   14G  48% /disks/disk1part5
/dev/sda6       320G  236G   83G  75% /home
tmpfs           385M  8.0K  385M   1% /run/user/0
tmpfs           385M  4.0K  385M   1% /run/user/105

[/size]My home directory is a btrfs partition. I can still access it from the console as either root or as user.

dibl

#5
Check the permissions on all the files in your /home folder -- make sure none of them, eg. .Xauthority, are owned by root.


Also I have noticed a new error from systemd journal since it was updated yesterday, "Cannot set file attribute for '/var/log/journal', blah blah blah" -- but it doesn't prevent login. It appears to be a reversion
https://bbs.archlinux.org/viewtopic.php?id=199940
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

bad_aptitude



Where would I find ".Xauthority"?
Here is the list of files owned by root in my user's home directory
I found these by running [ ls -alR | grep "root" ]



-rw-r--r-- 1 root root      149 May 23  2016 vpn.sh
drwxr-xr-x 1 root root       54 Oct 17  2015 flashplugin-nonfree
-rw-r--r-- 1 root root     1691 Jun 22  2014 pubkey.asc
-rw-rw-r-- 1 root root      1395 Dec  8  2014 ca.crt
-rw-rw-r-- 1 root root       577 Dec  8  2014 crl.pem
[/size]I don't think any of these would be important for my user login.

dibl


Depending on your desktop environment (mine is KDE), you might see this in your user's home directory:


don@Hibiscus:~$ ls -la | grep authority
-rw-------   1 don  don         53 Mar  4 06:43 .Xauthority



If you forget and run a GUI package as root, that file's ownership gets changed and you're finished logging in until you change it back to the user.
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

bad_aptitude

Hi dibl
I am using KDE.
When I run  ls -la | grep authority I get

kwd@kent_siduction:~$ ls -la | grep authority
ls: cannot access 'tor': Input/output error
ls: cannot access 'Dropbox': Input/output error
ls: cannot access 'logs': Input/output error
ls: cannot access '.dbus': Input/output error
ls: cannot access '.kde': Input/output error
ls: cannot access '.local': Input/output error
ls: cannot access '.Xauthority': Input/output error
ls: cannot access '.mplayer': Input/output error
ls: cannot access '.pki': Input/output error
ls: cannot access '.dropbox': Input/output error
ls: cannot access '.sabnzbd': Input/output error
ls: cannot access '.packagesearch': Input/output error
ls: cannot access '.recently-used': Input/output error
ls: cannot access '.thumbnails': Input/output error
-????????? ? ?    ?           ?            ? .Xauthority



[/size]I get the same whether I run it as root or as user.
[/size]This seems pretty ominous.

bad_aptitude

When I'm in the root shell I am getting  6 error messages of the form:
[/size]

[ 449783999] BTRFS critical (device sda6): corrupt node, bad key order: block=762344752, root=1, slot=120

[/size]
[/size] I took a photo screen shot to get this. The "block" "root" and "slot" are the same for all of the message lines.
[/size]
[/size] I also get the following message with ls
[/size]
ls cannot access 'logs': Input/output error

[/size]
[/size] Is there a way to recover my BTRFS on sda6?

dibl

#10
As root


umount /dev/sda6
btrfsck --repair /dev/sda6


Then mount /dev/sda6 and


btrfs scrub start /home


That will take some time to complete, depending on how large the partition is.


More
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

bad_aptitude


l ran the repair and scrub on my btrfs partition.
It seems to have worked but there is now no ".Xauthority" file in my home directory. So I guess it was unrecoverable.
I tried copying the file in from a backup either as root or user but I get the following in either case.
[/size]
root@kent_siduction:/tmp# cp .Xauthority /home/kwd
cp: cannot stat '/home/kwd/.Xauthority': Input/output error


Is there some other way to get an Xauthority file into my home directory? I would like to avoid doing a reinstallation.

dibl

That file is created automatically at the user's first login to X.  I would advise to make another user, and then delete your original user and his home folder (after copying off any needed data), and then remake the original user and when he logs in, the hidden files in his home directory will be rebuilt.  There might be a simpler way to fix it but I'm sure this will work if the problem is only with software.
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

bad_aptitude

Thanks dibl.
So I have moved my user directory over to a new user.
It seems my problem was bad sectors on my disk drive. It is odd that btrfs didn't manage this better.
It is also strange that the problem with a corrupted file system was only manifest after a dist upgrade.
I wonder if  .Xauthoriity was more vulnerable to this corruption because it changes frequently so the btrfs journaled version got corrupted as well.