Have openSUSE 12 in a Vbox which has been working good untill today. I get a login box that says:
Welcome to linux-ouvc.site
When I introduce my password, the screen goes dark and returns to same screen, asking for login password again.
If I try another password, I get a “Login Failed” message.
To recap, I am unable to login. Before today, no login was necesary. Only change was to turn on Network Services and run Update Manager last time I boot up to openSUSE.
Thanks for any help
Then login is actually working, but your desktop is crashing.
Which desktop?
You should be able to login to a failsafe session (if you are using KDM), and perhaps to an icewm session. Or, at the login screen, CTRL-ALT-F2 should give you a virtual terminal where you can login at the command line.
On Tue, 21 May 2013 23:56:02 +0000, Mayagrafix wrote:
> Have openSUSE 12
Please specify which version precisely - 12.1, 12.2, 12.3? There was no
“12”. 
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Latest and greatest, 12.3 “Dartmouth” kernel 3.7 - 64bit with KDE desktop - 
I tried alternative sessions to log in, all acted the same, except for failsafe, which works with terminal, i.e. accepts my password and user-name and logs me in.
The CTRL-ALT-F2 virtual terminal, on the other hand, will not recognize my user-name and password and rejects with login incorrect message.
Thanks in advance for ur help.
On Thu, 23 May 2013 15:16:01 +0000, Mayagrafix wrote:
> Latest and greatest, 12.3 “Dartmouth” kernel 3.7 - 64bit with KDE
> desktop -
>
> I tried alternative sessions to log in, all acted the same, except for
> failsafe, which works with terminal, i.e. accepts my password and
> user-name and logs me in.
>
> The CTRL-ALT-F2 virtual terminal, on the other hand, will not recognize
> my user-name and password and rejects with login incorrect message.
Sounds like either the pam configuration is whacked, or your user doesn’t
exist in the /etc/passwd file.
Can you login (at the terminal) as root? If you can, look at /etc/passwd
and see if the user is defined there. (Note - it is not recommended that
you log in to the GUI as root, as that can cause issues)
You can try resetting your normal user’s password with:
passwd [username]
Where [username] is the name of the user you normally login as. Do this
as root, then logout and switch to the graphical login and try logging in
there (or from the terminal, either will be fine to test with).
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Heres what I get in response to a new password request:
BAD PASSWORD: it is based on a dictionary word
passwd: Authentication token manipulation error
passwd: password unchanged
Tried different combinations of words and numbers, plain letters and numbers but only a numbers password successfully completes the change request. However, when used to login via GUI into KDE Plasma Workstation (or any other option from list other than failsafe), the screen blinks, and again brings me right back to login box as before. The failsafe option and console login still works.
From console tried startx, sax2, but no joy.
Thanks for ur help.
Startx and sax2 no longer work like they did in the past. sax2 is no longer supported at all and Startx needs permission changes to be used as a user. (Should work as root)
But try init 6 as root to start the GUI Note that you may already be in lev 6 so you may need to do init 3 then init 6
On 05/24/2013 02:46 PM, gogalthorp pecked at the keyboard and wrote:
> Startx and sax2 no longer work like they did in the past. sax2 is no
> longer supported at all and Startx needs permission changes to be used
> as a user. (Should work as root)
>
> But try init 6 as root to start the GUI Note that you may already be
> in lev 6 so you may need to do init 3 then init 6
>
>
init 6 will cause the machine to reboot, use init 5 instead.
OOPSIE
have no idea why I typed a 6 da
What is “init 3”?
I tried
su -c startx
from the console and the Plasma Workspace is functioning again. Tried to login as normal user, but no joy. Back to graphical login screen and if login as root, everything is fine. I created new user, tried to login as new user and same thing happens. Suse OS only works when I log in as root.
PS:
How do I add signature to post?
Suse 12.3 “Dartmouth” kernel 3.7 - KDE 4.10
init 3 is multiuse terminal mode. init 5 is multiuser graphics mode init 1 is single user terminal
if for some reason the GUI fails you are usually still in run level 5
ok so is ther a chance you have been loading stuff from the non standard repos??? This can cause a odd problems if you have mixed versions. show
zypper lr
Did you check ownership in of the .Xauthority and .ICEauthority files in your home they should be owned as the user not by root.
NEVER LOG IN AS ROOT to any GUI!!!
Have not loaded any software from other repos other than OpenSuse. - .Xauthority + .ICEauthority are nowhere to be found. Ran init 3 + init 5, after GUI reset login screen came back and still no joy. Here is result from zypper lr:
http://i16.photobucket.com/albums/b1/mayagrafix/binaryes/zypperlr2_zps54e88e9d.jpeg](http://s16.photobucket.com/user/mayagrafix/media/binaryes/zypperlr2_zps54e88e9d.jpeg.html)
Do you know that a period make a file onvisable to some commands?
in CL (Command Line) you us ls -a
in GUI be sure you show hidden files
You have tried just about everything that is known to cause your problem.
You never said type of video card. Is it a NVIDIA if so is your user in the video group??
I’m running out of ideas
On 2013-05-24 04:46, Mayagrafix wrote:
>
> Heres what I get in response to a new password request:
>
> BAD PASSWORD: it is based on a dictionary word
> passwd: Authentication token manipulation error
> passwd: password unchanged
Have you perhaps played with security settings in YaST?
Maybe you have set permissions to “secure” instead of the typical “easy”.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Thanks for help, me thinks maybe this might be a VirtualBox problem instead of OpenSUSE bug. I will go to their forum and ask (recently changed size of virtual HDD from 8 to 15 Gb because running out of space on Home).
Do you know that a period make a file invisable to some commands?
Used mc (midnight commander) to seek files.
Have you perhaps played with security settings in YaST?
Probably, because in VB one can screw up bad and not worry about it :>)
Again thanks for help. If VB forum says no problem with virtual disk size change, then I’ll be back… >:)
You never said you were running in a VM. That does change things. LOL
On 2013-05-26 05:46, gogalthorp wrote:
>
> You never said you were running in a VM. That does change things. LOL
He did, on the first post.
I don’t think it is related, except if the resizing operation damaged
some files.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Could be but it could be video drivers for the VM.
On 2013-05-26 20:26, gogalthorp wrote:
>
> Could be but it could be video drivers for the VM.
Yes, it could, but the vbox video driver should be a basic one, highly
compatible. I don’t use vbox myself, can’t check.
A full disk can also do that, a failed login. He changed the size of the
virtual disk, because it was full, I gess; but was the procedure the
correct one? I assume that first you resize the partition, then you
expand the filesystem to occupy it. 1st step is external, the 2nd one is
done by Linux, I assume, and manually.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
also could be expanding the partition and not expanding the files system.
