Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
11-06-2002, 08:08 PM
|
#1
|
Senior Member
Registered: Nov 2002
Location: British Columbia, Canada
Distribution: Gentoo x86_64; FreeBSD; OS X
Posts: 3,764
Rep:
|
INIT problem, won't start x
OK, this is a new one for me. . .
I rebooted my system and it started up ok, but when I got to the /etc/issue message, where it usually fires up x for the GUI login I got this message:
INIT Id "x" respawning too fast: disabled for 5 minutes
after 5 minutes it says the same thing again. I can switch consoles and use the system as normal from a text prompt, but x won't fire up.
I have not configured anything for x or INIT or anything since the last time it worked normally. The only thing I did was change one of the labels in grub.conf from "DOS" to "Windows 95" (my roommates don't know DOS from donuts!), but I don't see how this could possibly affect X.
I'm using RedHat 8.0, on a i586
Anybody know what's up?
TIA
|
|
|
11-06-2002, 08:09 PM
|
#2
|
Senior Member
Registered: Apr 2001
Location: Plymouth, England.
Distribution: Mostly Debian based systems
Posts: 4,368
Rep:
|
Is there anthing ominous in the logs?
|
|
|
11-06-2002, 08:14 PM
|
#3
|
Senior Member
Registered: Nov 2002
Location: British Columbia, Canada
Distribution: Gentoo x86_64; FreeBSD; OS X
Posts: 3,764
Original Poster
Rep:
|
Not sure, I had to post this from windows, as Lynx doesn't appear to be working either!?! I'll go check. . .
|
|
|
11-06-2002, 08:47 PM
|
#4
|
Senior Member
Registered: Nov 2002
Location: British Columbia, Canada
Distribution: Gentoo x86_64; FreeBSD; OS X
Posts: 3,764
Original Poster
Rep:
|
OK. ..
boot.log is fine
dmesg is fine
messages has the same thing as above
XFree86.log is fine, but I assume this is because it only logged the last time X was successfully started
any other logs I should check?
|
|
|
11-06-2002, 09:51 PM
|
#5
|
Member
Registered: Jul 2002
Distribution: Redhat, Gentoo, Solaris, HP-UX, etc...
Posts: 391
Rep:
|
Quote:
XFree86.log is fine, but I assume this is because it only logged the last time X was successfully started
|
No, the XFree86.log file should update everytime X attempts to start. Do a "cat /dev/null > XFree86.log" and then try to "startx" just to be sure.
|
|
|
11-06-2002, 11:44 PM
|
#6
|
Senior Member
Registered: Nov 2002
Location: British Columbia, Canada
Distribution: Gentoo x86_64; FreeBSD; OS X
Posts: 3,764
Original Poster
Rep:
|
I know you're all following this post with bated breath to see if I can figure it out,  well I did:
I followed jdc2048's advice, but got nothing from /dev/null. startx crapped out with a more useful error message: I upgraded my openssl package, without realizing that X was dependent on some of the shared-object libraries. So, uninstall the new one, reinstall the old one and I'm good to go.
So now my question is this: What does ssl have to do with X, other than secure http in a browser? Am I missing the point of what ssl does?
Thanks for the help.
|
|
|
11-07-2002, 12:23 AM
|
#7
|
Member
Registered: Jul 2002
Distribution: Redhat, Gentoo, Solaris, HP-UX, etc...
Posts: 391
Rep:
|
I had installed a series of updates recently on RH7.3 using the Red Carpet updater (Ximian's version of the RHN). Afterwards my X wouldn't work any more. It turns out that one of the updates (glibc I think) was overwriting my "/etc/ld.so.conf" file which was causing problems with a library that was stashed away in an odd place.
Did your openssl update include dependencies? Could you list the RPM's you were installing (including version).
----------------------------------
Jeremiah
|
|
|
11-07-2002, 12:42 AM
|
#8
|
Senior Member
Registered: Nov 2002
Location: British Columbia, Canada
Distribution: Gentoo x86_64; FreeBSD; OS X
Posts: 3,764
Original Poster
Rep:
|
Redhat 8 comes with openssl-0.9.6b-29
I was trying to install openssl-0.9.6g
I don't know why I did, it was a foolish attempt to have https support for konqueror, which does not appear to have it "out of the box". I made the new version from source, because I could not find an RPM for it, so it did not warn for dependencies.
|
|
|
All times are GMT -5. The time now is 06:36 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|