On Sat, 2008-04-19 at 13:16 -0700, John Oliver wrote: > On Sat, Apr 19, 2008 at 11:09:52AM -0700, Phil Mullane wrote: > > Here is some more feedback when I try to get things running. > > > > When I am at [EMAIL PROTECTED] and input konqueror, I get: > > > > konqueror: cannot connect to X server > > > > when I input mozilla-firefox, I get: > > > > (firefox-bin:4969); Gtk-WARNING **: cannot open display: > > > > when I input evolution, I get: > > > > cannot open display: > > Try "init 5" > > Also, try logging in as root, not you, and runing "startx". A user > wouldn't be able to do that. > > If you have an /etc/inittab you can look in it for a line like: > > id:3:initdefault: > > If something changed the 5 to a 3, that would explain why your X doesn't > start any more. Maybe an update "fixed" it for you? > > I don't know if your Linux uses dmesg, but try "dmesg | more" at the > command line. Scroll through and look for anything that looks ominous > :-) > > As far as the ISDN thing... Red Hat, for example, has an "isdn" service > that starts as default. Why, when very few people use ISDN today? > Dunno. Some legacy thing. Your distro may be similar... an ISDN > related service is attempting to start and failing. No biggie. > > -- > *********************************************************************** > * John Oliver http://www.john-oliver.net/ * > * * > ***********************************************************************
Hi John As I just wrote, I got lucky and found the answer. However, I did learn some things from your email. I went to /etc/inittab, which is new to me, and found what you mentioned. It does say id:5, but who knows what it said before. Also, I have come across "dmesg | more" before, but had forgotten about it. It seems to be pretty similar to what Carl mentioned earlier, /var/log/messages, but showing only the latest boot. Since I am up and running I don't want to try init 5. However, I did try that earlier when things weren't working and it didn't work. Again, I think I caused the problem last night and fixed it by "resetting" x Thanks for your help, Phil > -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
