Users cannot login to new install of SuSE 8.1
I have now attempted to install SuSE 8.1 (twice) on to a desktop computer. The install appears to go OK, and afterward I can login as root. The users can not successfully login, either from KDM or from a console. This is a fresh install of SuSE 8.1 (both times). The computer previously had SuSE 8.0 which was working fine. The install did not automatically detect the Viewsonic monitor E773. The E773 is in the database but the install did not detect it. I have manually set the Sax parameter to E773 and also tried just using a VESA setup. Setup was attempted using modest settings 800x600x65k. Root can login graphically from KDM or from console without a problem. As any user from KDM attempting to load KDE will hang after the splash screen shows "window manager"; Alt-Ctrl- <- needed to recover. Attempting to login to gnome will hang with just a grey background; Alt-Ctrl- <- needed to recover. Attempting to login to Windowmaker will show the basic 4 icons, no desktop and mouse buttons have no effect; Alt-Ctrl- <- needed to recover. Any user can login to Enlightenment from KDM !?!? And excepting the KDE menu in Enlightenment, most of the menus are functional. A user attempting from the console to startkde will recieve the following messages (from memory): xsetroot: unable to open display " xset: unable to open display " " xset: unable to open display " " xset: unable to open display " " Ksplash cannot connect to Xserver Kdeinit: aborting $DISPLAY not set The computer is using a Matrox 450 card, Viewsonic E773 monitor, AMD 1100 and mostly SCSI, lots of memory (800+ mb). Any suggestions or solutions to get users to login? Thanks -- Ralph Sanford - If your government does not trust you, rsanford@telusplanet.net - should you trust your government? DH/DSS Key - 0x7A1BEA01
Ralph, make sure /home is mounted/accessible make sure /tmp is allows read/write/entry access for users. Perms are normally rwx,rwx,rwT you can test with user account at console with "touch /tmp/testfile", etc John Scott Ralph Sanford wrote:
I have now attempted to install SuSE 8.1 (twice) on to a desktop computer. The install appears to go OK, and afterward I can login as root. The users can not successfully login, either from KDM or from a console.
Thanks
On Thu, 2003-01-02 at 09:32, John Scott wrote:
Ralph,
make sure /home is mounted/accessible make sure /tmp is allows read/write/entry access for users. Perms are normally rwx,rwx,rwT you can test with user account at console with "touch /tmp/testfile", etc
John Scott
Ralph Sanford wrote:
I have now attempted to install SuSE 8.1 (twice) on to a desktop computer. The install appears to go OK, and afterward I can login as root. The users can not successfully login, either from KDM or from a console.
Thanks
John, The permission were already correct for /home and /tmp. It appears that the problem is KDM will not correctly load KDE, Gnome or WindowMaker. I know this does not make sense, but it appears to be what is happening. By switching from KDM to GDM it is now possible to start KDE, Gnome or WindowMaker from a reboot to init 5. As the computer in question is my wife's computer, this means she still gets to use an entirely GUI system and she gets a new SuSE 8.1 install. She is happy and I can breath easier. I do not understand how KDM on a fresh install can fail to load KDE for just the users. A YOU update did not provide any relief. GDM provides an acceptable workaround. Thanks for your efforts. -- Ralph Sanford - If your government does not trust you, rsanford@telusplanet.net - should you trust your government? DH/DSS Key - 0x7A1BEA01
The 03.01.02 at 23:55, Ralph Sanford wrote:
The permission were already correct for /home and /tmp.
It appears that the problem is KDM will not correctly load KDE, Gnome or WindowMaker. I know this does not make sense, but it appears to be what is happening.
Something similar to this happened to me. It appeared the install failed to set the correct settings for the partitions in the fstab file: /opt was mounted "noexec". Check if this is you case issuing command "mount", some needed partition could be mounted that way. -- Cheers, Carlos Robinson
On Sun, 2003-01-05 at 18:17, Carlos E. R. wrote:
The 03.01.02 at 23:55, Ralph Sanford wrote:
The permission were already correct for /home and /tmp.
It appears that the problem is KDM will not correctly load KDE, Gnome or WindowMaker. I know this does not make sense, but it appears to be what is happening.
Something similar to this happened to me. It appeared the install failed to set the correct settings for the partitions in the fstab file: /opt was mounted "noexec". Check if this is you case issuing command "mount", some needed partition could be mounted that way.
-- Cheers, Carlos Robinson
Just checked. The computer in question does not have a separate partition for /opt (one large / partition and a /home). The permissions listed for /opt, the sub-folders of /opt and the files related to kdm and kdeinit are all owned by root at rwxr-xr-x, so that looks acceptable. In fstab the / partition is set at "defaults 1 1". Is that right? Or actually if there was a problem mounting the /opt partition, then it should not be possible to load KDE and the other desktop environments by using GDM which is the current workaround. Thanks for the suggestion. -- Ralph Sanford - If your government does not trust you, rsanford@telusplanet.net - should you trust your government? DH/DSS Key - 0x7A1BEA01
The 03.01.05 at 23:44, Ralph Sanford wrote:
Something similar to this happened to me. It appeared the install failed to set the correct settings for the partitions in the fstab file: /opt was mounted "noexec". Check if this is you case issuing command "mount", some needed partition could be mounted that way.
Just checked.
The computer in question does not have a separate partition for /opt (one large / partition and a /home). The permissions listed for /opt, the sub-folders of /opt and the files related to kdm and kdeinit are all owned by root at rwxr-xr-x, so that looks acceptable.
Then what I said doesn't apply to you :-)
In fstab the / partition is set at "defaults 1 1". Is that right?
Yes.
Or actually if there was a problem mounting the /opt partition, then it should not be possible to load KDE and the other desktop environments by using GDM which is the current workaround.
Well, in my case Yast had set every partition except "/" as "defaults,noexec", so that as the kde and gnome programs, that reside somewhere under "/opt" could not be executed, even having otherwise the correct permissions. -- Cheers, Carlos Robinson
participants (3)
-
Carlos E. R.
-
John Scott
-
Ralph Sanford