Been using 11.2 for a couple of months now, mostly I’ve solved my own problems or read from some preexisting already solved problems on threads like these. But, I’m not even sure where to start with this one. I cannot login under my main username, the account is set to autologin, and I get the login screen instead. When I attempt to login I get a black screen for about a second then it bumps me back to the login screen, no error messages. I’m able to login under runlevel 3, but as soon as I try to “init 5” it bumps me out and back to the login screen.
Root account works fine, and I used it to create a secondary account from which I am posting from right now. The behavior started after the system put the display to sleep while I was watching a movie in VLC, I woke it up just as it turned completely black, it hung there and I was forced to hard reboot. Had the problem ever since (for several hours now, lol).
I use Gnome but I installed KDE to see if it would resolve my problem, but no dice. Any suggestions?
When you boot
Try selecting the Failsafe boot, see if you can get to a desktop that way.
This sounds like a graphics issue to me.
If you have drivers (ati, nvidia) try re-installing them.
Hard reboot – hmm, that can be tricky. If the graphics works fine at runlevel 5 for root user and for the secondary account user, it looks like the graphics drivers are OK.
It might be expedient to copy all your data from /home/oldusername/* to a safe place, then delete and re-make the user “oldusername”, then selectively copy the data back from the safe place.
I’d say it’s not in the KDE4 configs, nor in the Gnome ones. Please do this and post results:
Login as the secondary user (the one that can login). From the Exit options in the kicker menu, pick ‘Change User’ and start a new session for the first user (the one that cannot login). I know it will throw you back to the second user’s session. Unlock that with the user’s password. Now open a terminal window and do:
tail -30 /var/log/Xorg.0.log
and post the output here. Let’s hope it contains the info needed to see what crashes X.
Side Question…
Is literally everything you do in opensuse, or even linux as a whole documented and logged???
-cheers
(II) Saitek GM3200 Laser mouse: initialized for relative axes.
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event4"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-D378AD8F86E560F712A83EE36E4E5E92C595B9BD.xkm
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event3"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-D378AD8F86E560F712A83EE36E4E5E92C595B9BD.xkm
(II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-09685A99DE19CBFB2C6505181AE64F7C6D530329.xkm
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Apr 26 12:52:06 NVIDIA(0): Setting mode
(II) Apr 26 12:52:06 NVIDIA(0): "CRT-0:1280x1024+1280+0,CRT-1:nvidia-auto-select+0+0"
(II) Microsoft Microsoft® Digital Media Pro Keyboard: Device reopened after 1 attempts.
(II) Microsoft Microsoft® Digital Media Pro Keyboard: Device reopened after 1 attempts.
(II) Saitek GM3200 Laser mouse: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
It’s just a bunch of **** (seriously it censors cr@p? lol) about my keyboard and mouse … which is weird, because I thought X dealt only with display …
@subcook - Was I being too through? The answer is no, in any case, everything I put down was from (my human) memory.
@swerna - I was thinking about doing that, but I’d prefer to do that only if I can’t get an answer out of this thread, as I’d like to know what to do if this happens again or at least, what I did wrong so I can avoid doing it again. Plus, I think it will probably be annoying to deal with changing all the permissions on my files.
Oh yeah, and I did try to boot in fail safe mode, didn’t work.
I found the source of the problem and fixed it. It was because of this line I had put in my .bashrc earlier in the day.
export XAUTHORITY=/home/name/.Xauthority
which was intended to keep me from having to type in
xhost local:root
every time I wanted to use Altera Quartus which would otherwise give me this message when I tried to run it.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
quartus: cannot connect to X server :0.0
I didn’t consider it earlier because I had already restarted the system at least once after I made the change without any problems.
This is no longer an Install/Boot/Login problem, but perhaps someone has a suggestion on how I can put this annoyance to rest?
Oh, and thanks for everyone’s help so far. It would have taken me much longer to figure out that it wasn’t a problem caused by VLC/DisplaySleep without you.