[SOLVED] Slackware 13 - Problems with "su" as superuser(root)
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
What exactly happens when you use `su` in an X terminal? Is the password rejected? Or do some strange errors happen, such as maybe "command not found" or something like that? Please elaborate about the exact symptoms of "cannot access my root account".
Also, I notice you are from Brazil? If the case is of the password being rejected, I ask this: have you got the same keyboard layout & locale/language settings while in your desktop, running X, as you do when you are outside of X, at the Virtual Terminal? Does your root password contain any strange, foreign, accented, etcetera characters, which may not be getting entered correctly from your desktop?
Finally -- Did you change anything with the system recently? Did you have no problem one day, then "something happened", and now it does not work? If so, what did you change? Maybe upgraded some packages, or removed some, or whatever?
Yes, I'm from Brazil. No, I don't have problem with my Layout.
My Keyboard It's OK and my password too. My problem is 'su' in
an X Terminal (Like konsole, gnome-terminal, xTerm, etc) and
Console(without X11), but I don't have problem with 'Logon'.
When I will restart my computer, I can access my root account
normally, less with 'su' in Console and X11.
I'm sorry I got distracted by how cool your screenshot looked you should put a screenshot in the giant thread called "This is my slackware desktop", it's very nice.
I'm not sure what to suggest, but it *appears* that you're simply entering the wrong password, due to character/locale problem.
As Didier suggested above, perhaps running `xorgsetup` will help, provided that you set the keyboard to be the same as you did when you installed the OS and selected a keyboard. For example, if when you installed the OS, you chose "en_US" as the keyboard setting during installation, then run xorgsetup and set the keyboard language to that setting again, and see if this helps.
I assume you are absolutely certain that you know what the root password IS, so another suggestion (I tested this earlier) is to type your root password in plain text, either on a text-editor or on a terminal window (type it at the prompt and just hit enter to get to the next line), so that you can copy & paste it later. Now, you can see the password in plain text on the screen-- make sure it is exactly correct;
Now, type su, and where it asks for the password, highlight the password you put in plain text, using your mouse, and press SHIFT+MiddleClick to paste the password (you will not see anything, but trust me, it did paste). Now hit ENTER.
If neither of these ideas helps, I apologize; I have no other suggestion at this time, so I really hope that someone else has another approach to try.
I upgraded my Slackware and I found a lot of problems here.
Now I need to reinstall everything again. I can access normally
with `su` now, after upgraded. When I access as root or another
account, I see that message:
configuration error - unknown item 'DIALUPS_CHECK_ENAB' (notify administrator)
configuration error - unknown item 'NOLOGIN_STR' (notify administrator)
Last login: Fri Mar 19 03:48:50 -0300 2010 on /dev/tty1.
Never have children, only grandchildren.
-- Gore Vidal
Mar 18 14:32:29 MOBJRLinux login: ROOT LOGIN on `tty2'
Mar 18 23:38:46 MOBJRLinux su: Authentication failed for root
Mar 18 23:38:46 MOBJRLinux su: - pts/0 miltonjr-root
Mar 19 03:48:30 MOBJRLinux login: ROOT LOGIN on '/dev/tty1'
Mar 19 03:49:03 MOBJRLinux su: unknown configuration item `DIALUPS_CHECK_ENAB'
Mar 19 03:49:03 MOBJRLinux su: unknown configuration item `NOLOGIN_STR'
Mar 19 03:49:05 MOBJRLinux su: Successful su for root by miltonjr
Mar 19 03:49:05 MOBJRLinux su: + /dev/tty1 miltonjr:root
Mar 19 03:49:15 MOBJRLinux su: unknown configuration item `DIALUPS_CHECK_ENAB'
Mar 19 03:49:15 MOBJRLinux su: unknown configuration item `NOLOGIN_STR'
Mar 19 03:49:18 MOBJRLinux su: Successful su for root by miltonjr
Mar 19 03:49:18 MOBJRLinux su: + /dev/tty1 miltonjr:root
Mar 19 13:41:56 MOBJRLinux login: ROOT LOGIN on '/dev/tty1'
Mar 19 15:48:20 MOBJRLinux login: invalid password for 'miltonjr' on '/dev/tty1'
Mar 19 15:48:25 MOBJRLinux login: invalid password for 'UNKNOWN' on '/dev/tty1'
Mar 19 17:00:43 MOBJRLinux login: ROOT LOGIN on '/dev/tty1'
I had that stuff too, after I first upgraded to -current. Those messages are, if I recall correctly, caused by deprecated items in the /etc/login.defs file. Once you have replaced the old version of the file, with the new one (usually with the .new suffix), the problem will go away.
You might want to look around the system for other .new files and examine them for changes in the new version over the old version; then, make sure you either merge the old and the new, or manually edit/copy/rename whichever version you want to keep. Doing this sort of cleanup would save you having to re-install.
Also, if you have Slackpkg installed, it has an option for dealing with .new files.
P.S. - why did you attach that dmesg or kernel.txt file? It looks OK in there.
About my screenshot, thanks.
slkrover, I use `su --login`.
I use slapt-get (slapt-get) and I have slackpkg.
I have `Gnome` and `KDE`. My KDE I can`t start more and my Gnome
I can`t see my Wallpaper and my Keyboard layout is different now.
I will rename one by one and make a backup for each file(security).
I rename `login.defs.new` to `login.defs`, I don`t have problem now.
I usually overwrite the ones i haven't changed and diff the ones i know i changed so i know what i should do.
slackpkg is real good for keeping your Slackware up to date.
But it only handles official packages.
I think you should start checking .new files when you update or upgrade your Slackware.
You can't always trust a tool to do everything for you so always read the changelog before an update or upgrade.
Last edited by Nille_kungen; 03-19-2010 at 07:14 PM.