Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 307
  • Last Modified:

XDM Still kicks me out of X!

in my /etc/inittab, i have xdm in place of mingetty (RHat)
to run X, to login etc. but it doesn't work. even if I run XDM
from a shell it doesn't work. here are the facts:

it gives me the login prompt in xdm, i login, and it boots about half of my window manager (tried several) and then
It kick me out of X and brings me back to logon.

help! i wan' t pure X!

(and no `rc.local' answers please)
Thanks, Bromone4.
0
bromone4
Asked:
bromone4
1 Solution
 
jlmsCommented:
Did you check /var/adm/messages to see if the system reports any problem immediately after loging in?

Know, if you pres <Ctrl><Alt><F1> you go to the console, here you could be getting error messages that could help you to find the problem.
0
 
jlmsCommented:
Sorry, I forgot to mention to press <Ctrl><Alt><F7> to bring you back to the graphic environment..
0
 
bjacobsCommented:
X will not start if you're running the gpm mouse program. Be sure it's not being loaded.
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
bromone4Author Commented:
You people all suck! I have tried all of this over and over and it
still wont work!! It first loads X, then frigs with the screen (looks
oddly-formed) and then redoes X! do you want me to write a book?!
0
 
bjacobsCommented:
We may suck, but at least we can run xdm!
0
 
nicademusCommented:
Oddly formed?  what about your video driver?
0
 
fiverCommented:
Hmmm.
You said, your login prompt works, so it can't be the wrong driver! However, the error seems to occur during the strtup files (.xsession, .profile .kshrc ...). If this is correct, your X session will work when calling "xinit" from the command line.

Maybe you should look in your .profile an .xsession: I've had the same effect on a HP machine when I tried to include my .profile which includes some commands to find out the terminal type or the content of $TERM. So be sure to have nothing in your startup files reated to TERM (e.g. tset). Beware of the .kshrc .bashrc!

fiver
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now