SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Same happened to me. User access denied! Root was no problem, deleted 'user' including 'user' directory, rebooted, created new user with same name.
Now we have two problems in SUSE10:
1. User access is unstable.
2. Simple broadband connection (DSL) not working "out of the box".
Ok i have a some what similiar problem, but a tad more serious........
Here's the full story....
Recently installed SuSe 10.0 and been loving it.
I noticed 2 of my 3 windows paritions weren't being mounted with the options i stipulated in fstab. Namely, i couldnt execute any scripts on those paritions and had to do, as root:
mount -o remount,exec /windows/E
Now ...... / wont mount in anything except single user mode.
There's nothing in /var/log/messages to explain besides the fact the / partition (/dev/hda7) isnt mentioned at all.
It seems udev isn't making the node device for it during boot, i am suspecting anyway. Also /dev/hdc2 has an error in /var/log/messages from udev saying it doesnt exist when it tried to make the node device for it, yet it does in single user mode and can even be mounted in single user mode.
I am lost. Looks like i might need to take a Windows method in fixing this and re-install /
I had this same problem. For me, it started when I issued a reboot command from a terminal window while in KDE. Other users could still login but my user could not.
I did a google search and found an article that recommended removing the Xauthority file and a couple others from the problem user home directory. I don't remember exactly what the file names were but there were 3 of them.
This worked for me. After that, it happened a couple more times, I removed the same files, restarted run level 5, and all was good.
I'd assume that in some cases the X server is not shut down properly and remains locked. You could try to login to the command-line and remove /tmp/.X0-lock, then try again.
A good hint on what's wrong may come from starting the Xserver from init 3: change to init 3 and type 'startx' this should give some messages. Apart from that, the file ~/.X.err may contain the desired information.
DaveQB:
Did you make any changes in /etc/fstab recently? Maybe you just included a syntax error which makes / unmountable. Check with 'fstab -l' if the partitions in fstab match the actual partition table. I doubt that your mount command has caused any of this trouble.
i have experienced the same problem with both SUSE 9.3 professional and SUSE 10.0 OSS!
i started using SUSE 9.3 pro without any problems and this problem started after my HARDDISK developed some BAD SECTORS. then i switched back to FC4. no problems there. then tried SUSE 9.3 pro again. there was the problem again!
tried SUSE 10.0 OSS on the same HARDDISK (it's dead now ). got the same problem here too! i can login as root, but not as an user. the user is still there in YAST. i tried creating a new user. but after reboot, back to square one! stuck at the login screen!
i like the eyecandy of SUSE very much. but this issue holds me back from installing it on my new harddisk. noone, with whom i discussed this problem, was able to give a solution .
Sounds like this problem occurs preferably to those who change distributions frequently.
In drr_te's post, it seems to be narrowed down to faulty hardware, of which FC4 seems do be more tolerant than SUSE (maybe ext3 vs. reiserfs?).
I never experienced this problem on any of my systems (not a single time, most of them SUSE), so if we try to invesitgate this problem more systematically, we may be able to find a common procedure/hardware/habit of all you people that allows us to find a solution:
- run filesystem checks
- check logfiles
- report non-standard procedures (e.g. manipulation of configs, other than with YaST)
- use of different filesystems
One point I noticed: Do you all use graphical root login? This is something I never do, for example.
yep, all this happened with graphical login screen.
but i never manually edited any config files in this case. the file system thing suggested by abisko00 seems to explain the situation for me, as it happened to me only after there was problem with my harddisk. i was using ext3 in FC4 and reiserfs in SUSE as abisko00 pointed out.
DaveQB:
Did you make any changes in /etc/fstab recently? Maybe you just included a syntax error which makes / unmountable. Check with 'fstab -l' if the partitions in fstab match the actual partition table. I doubt that your mount command has caused any of this trouble. [/B]
I did make a slight change to fstab, but it was minor and there were a few successful reboots before this problem started.
I have double checked my fstab though with fdisk -l to see any discrepancies, but nothing. Also, all mounts automatically in single user mode, no complaints.
My problem seems a little different to the rest, as i can't log in as anyone in runlevel 2-5, but in runlevel 1 i am logged in ok [as root of course].
Seems there is something in all the runlevels accept from runlevel 1 thats causing me trouble. I still suspect udev, but don't anyway to investigate that further, let alone fix it.
i just got the same problem and here are the stuff i did in my last session:
1. install ymessenger (yahoo messenger) using RH9 package available on their site
2. changed my bootsplash using a software called kbootsplash
3. used a USB key for the first time since installation.
just a question i want to ask here:
did any of you did something similar specially the ymessenger or the USB key??
hey everyone
i got it to work and i may know what the problem is:
when i played around i finally got a pop up message that said DCOPserver can not be linked or has a problem.( i dunno know what it is, it may have came b/c i played around with some stuff).
so in continue i removed all hidden file( the dot files) in my home directory (and i mean all of them except the folder ones) then i removed the .kde as well. when i tried to login it worked like a charm for my user.
and one other thing. on my last session before the problem, i was angry so unplugged the computer from the power while being in KDE!!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.