Ask Your Question

Can't boot through sddm and system settings not working

asked 2018-09-13 19:50:09 -0600

When I try to log through sddm (default on the kde spin) the screen will flash to the the terminal then back to the sddm. When I type a wrong password is seems to work fine i.e. rejecting me but not flashing to any other screen. I have to enter the tty and log in there and startx.

In addition, when I try to use system settings it will appear to load but then do nothing.

The biggest change I made to the system was to set another ssd to be the home partition by adding and deleting a line from the fstab:

dev/mapper/fedora_localhost--live-root /                       ext4    defaults        1 1
UUID=44b329a2-9238-4ffe-a53d-734ac0590ac0 /boot                   ext4    defaults        1 2
/dev/mapper/fedora_localhost--live-swap swap                    swap    defaults        0 0
UUID=bf8efd03-3220-4678-83ab-b2a5228a66c2 /home ext4 defaults 0 2

I don't know where the xorg logs are or how to decipher them. My theory is wierd permissions.

edit retag flag offensive close merge delete


Welcome to ask.fedora. From what you've written, your computer boots just fine, because if it didn't, you'd not get to the login screen. The problem is that sddm, your Display Manager, is failing to start your graphic environment, presumably KDE. I don't know, yet, what's wrong, but I did want to keep you from barking up the wrong tree. Are you comfortable using a command line?

sideburns gravatar imagesideburns ( 2018-09-13 23:16:35 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2018-09-14 18:34:02 -0600

heliosstyx gravatar image

The .Xauthority (not .xAuthority) file can be found in each user home directory and is used to store credentials in cookies used by xauth for authentication of X sessions. Once an X session is started, the cookie is used to authenticate connections to that specific display. You can find more info on X authentication and X authority in the xauth man pages (type man xauth in a terminal).

So, if you are not the owner of this file you can't login since you can't store your credentials there.

What you can do is the following: Change the ownership of .Xauthority which was previously owned by ROOT by executing:


sudo chown username:username .Xauthority (replace username through your system system values).

Start your login screen again.

Please let me know if it's working.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2018-09-13 19:50:09 -0600

Seen: 64 times

Last updated: Sep 14