No, just since I haven’t been able to log in as myself have I been doing this.
It does ask me for a password, but then it dumps me to a terminal.
I did notice that the window manager didn’t seem to be assigned to anything, so I assigned it to KDE and its now properly kicking me to a KDE screen (although I have a default user set so there is something going awry there)
Tried a new user and no go.
I went to the home directory and have changed all files to my user, there weren’t very many or any system related files that I could tell
Recap: I now get a proper KDE login screen instead of the one pictured, but even when I log in via that screen I still am getting dumped to a terminal.
All files in my users directory have been set to my user (I selected the directory and had it recursively go through and assign them).
Now it seems the failsafe is being triggered. When I boot up, I eventually end up with a black screen sans 1/9th that is a console window that appears to be frozen.
I can switch to other sessions however and can still “sudo startx” to get into GUI.
There is a minor bug where recursive option doesn’t always work when changing permissions from root+root to user+users.
Not sure if that’s KDE or dolphin specific. I did notice this bug several times.
Steps to reproduce:
Add some root owned files and folders into user home and set recursive permissions of /home/username to username+users.
Open /home/username and the files and other folders inside are sometimes (not always) still owned by root+root.
Enable hidden files display and detailed permission display in dolphin to manually check the permissions.
Then set recursive user permissions on each missed folder if there is any.
Not sure if this solves your problem, just saying I’ve seen it happen before.
When I boot up, I immediately fall into failsafe. Or at least what I think is failsafe. It loads a white console window that I can’t interact or type into.
I hit ctrl-alt-f1 to get to console and log in as my user then run the following commands (the final one is the only one that works the rest output a serverauth not found error).
startx sudo startx
On 2012-11-15 18:26, charlieoliver wrote:
> robin_listas;2503955 Wrote:
>> Have you enabled secure settings, perchance?
> If I’m not sure what those are, could I have enabled them accidentally?
You might, it is one of the settings in YaST.
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))