X and Fluxbox :: Error: "unable to connect to X Server"



Hi!

I think, I did a very stupid thing. I wanted to customize my fluxbox desktop and so I started to play around. By not knowing what I am doing, I tried to get the version of fluxbox with the command:
Code Sample
fluxbox

But my intention was to type this:
Code Sample
fluxbox --version

So I typed the 2nd command, too.

Both lead to the same messages/warnings (but no real errors), but I am sorry, I cant remember them. At least nothing happened. I got feared and rebooted the computer.

So, now here comes the trouble. On startup, while the computer tries to start the X server, I get this:
Code Sample

xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.


Some "googling" showed me, that this seems to be a common problem, but I found no real match which addresses my problem. The XServer is definitly installed (/usr/X11R6/), the path to "xinit" is in the $PATH too (... :/usr/X11R6/bin: ...)

So a /usr/X11R6/bin/xinit starts the X Server and I get a black-white-GUI (sorry I cant give you a screenshot). From this point I can start things like nedit again. Now, if I enter "fluxbox" I also get the fluxbox desktop with the common elements, but in the same black-white-style. I get a couple of error messages in the xterm-window (Again sorry, I dont know how to include this here):

Code Sample

Failed to read: session.tabs
Setting to default value
.
. [snip]
.
BScreen::BScreen: managing screen 0 using visual 0x21,depth 4
.
. [snip]
.
BScreen::LoadStyle(): couldnt load font '-misc-8x8...'
BScreen::parseMenuFile: [stylesdir/stylesmenu] error, '//.fluxbox/styles' does not exist


I guess that some .foo file is missing or corrupted, right?

Well, it seems I can work awhile though I have this problem, but I want that babytux back again  :D

Oh, and before I forget it: I use DSL 0.49 as an HD-install.

Many thanks for your help in advance!

Cheers
tscha
Hi all people

I'm begginer in Linux, and I'm testint DSL linux.... but  when I try to boot my PC, I HAVE THE SAME PROBLEM: that 2 errors...

I should be much obliged if anybody can explain me how I can repair that.

Thanks

P.D: Sorry about my poor english, I'm spanish :D
I dont know how but the problem is solved...

It seems that after my mistakes with "fluxbox" and "fluxbox --version" several unclean shutdowns caused the problem. Unclean, because the computer halted and didnt finished until the message "Knoppix halted."

I then did a "shutdown -h now", switched off/on, and my babytux is back, yeah  :cool:
Good you got it working.  I couldn't say what the problem was, but here's some info for you in case something similar happens in the future....

If fluxbox is already running and you use the 'fluxbox' command, or use it with an option it doesn't recongnize, it will try to start and fail because fluxbox can't run two instances in the same X display.  to get the version, type 'fluxbox -version'.  It will display the version and then cleanly quit before attempting to connect to your X session.

Quote
Failed to read: session.tabs
Setting to default value

This isn't an error.  Fluxbox is just telling you that it was expecting to find a 'session.tabs' resource in /home/dsl/.fluxbox/init.  It isn't there so it fell back on the default setting.

Quote
BScreen::BScreen: managing screen 0 using visual 0x21,depth 4

This is just information.

Quote
BScreen::LoadStyle(): couldnt load font '-misc-8x8...'

Your current style tries to use a font which doesn't exist on your system.

Quote
BScreen::parseMenuFile: [stylesdir/stylesmenu] error, '//.fluxbox/styles' does not exist

This doesn't look right.  Your /home/dsl/.fluxbox/menu file could be messed up.  The stylesdir paths listed in the menu should be:
[stylesdir] (/usr/share/fluxbox/styles)
[stylesdir] (~/.fluxbox/styles)
It shouldn't be serious, though...Fluxbox should still run.

Quote
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.

This is the only serious thing I could see, although I would have guessed it was a PATH problem (you already mentioned that).  It's possible that there was a file (.Xauthority maybe?) which should have been removed but was not because of the unlclean shutdowns.
I've only burned the ISO image into a CD, and I have boot my PC with it...and then, te fail has appeared :-p.......

Y don't know what's fluxbox.....

..Can anybody help me?
Next Page...
original here.